Database Users

[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

Rooting the SCH i400 - Step by Step Instructions for Newbies

I just managed to root my SCH i400 (first ever rooting of any Android device for me).
I am very surprised by how smoothly it went, despite reports & warnings everywhere about complications (like this one - which should be totally ignored if you're using SuperOneClick v2.1.1 or higher).
For the benefit of n00bs like me who may be confused by multiple sources, resources, versions and problem reports, I am posting a step by step procedure that is confirmed (by me, on Windows XP SP3) to be working smoothly, without a single hitch of complications:
Phone: Make sure setting > applications > unknown sources is checked.
Phone: Make sure phone is in debugging mode.
Phone: Make sure SD card is unmounted!
PC: Make sure Windows USB driver for this phone installed and works
PC: Make sure .NET 3.51 SP1 is installed.
PC: Unzip SuperOneClickv2.1.1-ShortFuse.zip ==> C:\Program Files\SuperOneClickv2.1.1-ShortFuse
PC: Double-click SuperOneClick.exe
PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
PC (in SuperOneClick): Now click the root button and wait for the process to complete.
PC (in SuperOneClick): "BusyBox not found. Would you like to install it?" Yes!
PC (in SuperOneClick): "Root install has completed! Would you like to run a test?" Yes!
PC (in SuperOneClick): "Your device has been rooted! Would you like to donate now?"
Exit SuperOneClick, unplug phone from USB, power down phone, power on phone. -- this step might not be mandatory, I just did it to be on the safe side.
Enjoy!

Great job on this tut.
Sent from my SCH-I400 using xda premium

Nice...
I may have to sneak my wife away from her for a bit....
Sent from my DROID using XDA App

Froyo is so nice... Here's how...
Hey guys... new poster here.
Just got a (Gently used) Samsung Continuum for free from Verizon after the power button on my G Droid 1 broke.
Anyways, after rcving it and realizing that it would only support Android 2.1 - I was slightly upset.
My D1 was rooted and modded to the max many times over with just about every ROM you can get.
So after reading up about IMNUTS leaking the Froyo download for the Continuum, my hopes were raised.
It is now debinged, debloated, lightening quick and amazing!
There may not be ROMS out there yet - but I truly hope some of you geniuses decide to make a few.
Just wanted to say thanks and encourage you to do some research before rooting it.
Here's what worked for me.
Odin 1.3
Continuum PIT.pit file
froyo_modem.tar.md5
cwm_recovery_test4_adryn.tar
cyan Clockwork Mod Recovery (BLUE, not yellow) (update.zip file, which is placed on the root of your SD card - renamed to update.zip)
stock_deodexed_ec03.zip (ROM)
(Place all of these files on your Desktop for easy access)
How to do it...
1. Connect your phone to your computer and Mount it.
2. Place the cyan CWM Recovery zip file to your SD card. (rename it to update.zip & do not put it in any folders. Just drag the file to your SD card - whatever drive it is listed as. Mine is my Removeable F
3. Make a new folder on your SD card. Name it whatever you want. (Mine is named "Froyo") Place the stock_deodexed_ec03.zip file in the folder on your SD card.
4. Open Odin 1.3 on your PC.
5. While your phone is off... hold the down volume button and connect it to your computer via USB. The yellow triangle will appear and it will say "Downloading". (Some people say to take the battery out, but my Odin program would not recognize my phone without the battery. Whichever works for you is fine.)
6. In Odin - Click the PIT file button. Load the Continuum.Pit.pit file into the file field. (Just double click it once you find the file from your Desktop.)
7. In Odin - Click the PDA button. Load the froyo_modem.tar.md5 file into the file field. (same as #6. Just double click it once you find the file from your Desktop.)
8. Click Start in Odin.
It should think for a minute, then say resetting, then say PASS
Then your phone will probably turn back on - turn it off again and reconnect it to your PC in download mode as stated in #5 above.
9. In Odin - Click the PDA button again. Load the cwm_recovery_test4_adryn.tar file as you did in #'s 6 and 7 above.
10. Click Start again in Odin... same as before. (thinking, resetting and PASS)
Your phone will turn on again.
11. Disconnect your phone from the computer & turn it off.
12. Hold both Volume buttons and turn it on. It will boot into the Samsung Recovery mode.
13. Use your Volume buttons to go down to highlight "apply update.zip" Then find the place where your normal Menu softkey would be and push it. The phone should then reboot into Clockwork Mod Recovery. It will be orangish.
14. In CWM, use the Volume buttons to highlight Backup/ Restore. Use the Power Button to choose it. Then at the next field, highlight Backup and make a backup.
15. After is makes the backup, press where the softkey Back button should be to go back to the original screen. From there, do a Wipe Data/ Factory reset. Do not forget to do this part.
16. Once it does the Data Wipe - go back to the main menu and and highlight & select the "zip from SD card" choice. Find your "Froyo" folder (of whatever you named it) and apply the stock_deodexed_ec03.zip file.
17. After that, go back to the main menu again and reboot your phone.
It may take a while, but your phone should restart in Froyo.
Of course, you have to re-sign in to your Google network...
Thanks so much guys for all the posts. Without them, is nowhere near as cool.

Hanging at Step #5, Now what?
Thank you for sharing. Wish I could say it went as smoothly for me with my SCH-I400 Continuum... I'm still working on it! I followed recommendations of several different developers/rooters. I've installed .Net Framework 4.0 and the SDK developers kit (who knows, maybe I'll start a new hobby...), and now when I run Superoneclick it hangs at step #5 with this message:
link_image[1728]: 3252 could not load needed library 'libdiskconfig.so' for './zergRush' (load_library[1058]: Library 'libdiskconfig.so' not found)CANNOT LINK EXECUTABLE
I have rebooted the computer and the phone, unmounted the SD card, settings to allow unknown sources, and turned on USB debugging. I'm not sure why the config file can't be found, and I don't know where to get it...
Do I need to reinstall the SDK? Or install the additional Java developers software? Or am I over-complicating this whole thing?
Any ideas will be greatly appreciated...
-James

Perhaps the easiest way is to flash a rooted ROM through Odin (or Heimdall)... Especially if you don't use Windows. This is how I did it:
http://forum.xda-developers.com/showthread.php?t=1203597

Two topics in one thread?
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James

bighigmt said:
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
Click to expand...
Click to collapse
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX

Txwolf1980 said:
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Click to expand...
Click to collapse
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...

bighigmt said:
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
Click to expand...
Click to collapse
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium

Come on now...
ciscogee said:
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
I spent 6 hours last night troubleshooting, researching, digging deep, and "using that little search box." Seems to me You guys need to "just read the thread." It's about rooting your phone, period. If a forum is out there, I've probably read it. I'm using superoneclick to do it. SDK is installed. Net framework is installed. My error message frome SOC is above. When I am finally rooted, THEN I will install several programs - starting with a wifi tether.
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.

bighigmt said:
...Seems to me You guys need to "just read the thread."...
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
Click to expand...
Click to collapse
well i did read the thread...
ive been out of town for a week and finally back on my pc... i would love to help you yet more info is needed.
you are running dl17 stock 2.1 correct?
what OS is your pc running?
and yes i have same phone as you. i have used superone click on ec03 build once.
just for root. but then flashed a deodexed rom to use custom mods and apps.
and since have been flashing rooted kernels, imnuts and adrynalynne have released most all of them.
there are a few ways to root the device, best bet is, as always is go to IRC.
clarity and patience are key, we all got to practice both

I rooted EC09 with soc no problem. If I send someone the EC09 could they extract the apks and send them to me? I deleted some sys apps for the ticker and rss feeds and need them back now to use it.
Sent from my SCH-I400 using xda premium

Unzip factory.rfs of ec09 to grab missing apks and put them on sdcard and install from there.
Sent from my SPH-M580BST using Tapatalk 2

verizonless said:
[*]PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
Click to expand...
Click to collapse
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?

verizonless said:
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
Click to expand...
Click to collapse
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.

trailblazer101 said:
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
Click to expand...
Click to collapse
Im assuming by now everyone is on EG04 Gingerbread?

[Q] Using fastboot.

So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2

a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....

dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2

CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951

So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.

Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......

Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device

CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit

OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"

CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording

Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL

CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs

Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.

Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8

[Q] Phone has a wierd rom can't get the drivers working on the computer

Hi this is my first thread and i really dont know how this works but heres the problem
i bought a nexus 4 16gb from a guy on craigslist and it has a wierd rom in it, it is still 4.2 and i am unable to get updates on it. i browsed around and landed on a forum that said about it being some kind of debugger/developers rom that google uses. i dont have a lot of feature i can't connect it to computer to root it and neither can i transfer file from computer for exaple music or pictures.
The build number is:
full_mako-userdebug 4.2 lgep19
eng.seungju24.choi.20121114.105751 test-keys

If you want your phone back to stock and unroot you'll need to access a PC and follow this guide.
http://forum.xda-developers.com/showthread.php?t=2010312
This will put the phone how it comes out of the box. Otherwise if rooted and has custom recovery why not stay rooted and flash different 4.2.1 roms?
Sent from my Nexus 4 using xda premium
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
Also this video will help too. He has a folder for download with everything you need.
All you need is to type in commands.
https://www.youtube.com/watch?v=2Se0N86qsJE&feature=youtube_gdata_player
Sent from my Nexus 4 using xda premium

What os do you have on your computer?
Sent from my Nexus 4 using xda app-developers app

1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.

Not working
rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this:
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.

irfan9490 said:
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this: http://dl.google.com/android/installer_r21.0.1-windows.exe

It still isn't working
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse

irfan9490 said:
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
Click to expand...
Click to collapse
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat

ANother Error
rr5678 said:
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat
Click to expand...
Click to collapse
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money

irfan9490 said:
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money
Click to expand...
Click to collapse
Okay, try adding these to the same directory.

Still not working.
rr5678 said:
Okay, try adding these to the same directory.
Click to expand...
Click to collapse
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.

irfan9490 said:
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.
Click to expand...
Click to collapse
open a command prompt in that directory and type fastboot oem unlock. then try again

Thanks you very much it works a lot better
now.
Sent from my Nexus 4 using xda app-developers app

rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
I am VERY thankful for this thread. It helped me rid a company phone of that garbage Debug ROM. Thank you very much!

Root, Backup TA and Unlock Xperia Z1 running 4.3 on Mac OS X

Rooting, Backing Up TA and unlocking bootloader on a Mac can be a pain in the backside especially if you're a nube. Since there isn't an obvious guide out there for us (the most hated computer users by developers) Mac users i decided to create one.
Before we start make sure you're running the latest Mac OS X Mavericks (which is free thanks to apple generosity ) this is to make things easier for me when it comes to helping you.
PLZZZZ PLZZZZZ Read Instruction first (making sure you have a general under standing of them) THEN FIND A POSSIBLE ESCAPE PLAN (just incase things go south) and obtain the correct files before proceeding to follow them!!!!
WARNING!!!!From this point onwards I AM NOT RESPONSIBLE for any damages to your phone, whether they are as small as a 1/1000 mm scratch or as big as a worldwide Nuclear Holocast caused by Aliens! You decided to follow these instruction so it's YOUR FAULT!
Here's the order of what we'll be covering first to last:
1) Backing Up TA
2) Unlocking Bootloader
3) Installing a custom kernel
4) Rooting
BACKING UP TA
You may have heard rumours saying that "YOU CANNOT BACKUP TA ON MAC OS X, ONE MUST HAVE WINDOWS!".
Well I'm here to tell you that's TRUE, sadly. But FEAR NOT! Because the GODS have given us a work around (which is probably longer), and here it is:
First Downgrade to .534 using latest flashtool for Mac OS X
DOWNLOAD HERE http://www.flashtool.net/download.php (make sure you dave the app in applications folder)
Downgrade instruction here: http://forum.xda-developers.com/showpost.php?p=45464122&postcount=3
You can find firmware folder by right clicking ( if thats enables, surf the interwebs on how to do it if you don't know) then "show package contents" => Contents ==> MacOS ===> firmwares. This is ware you'll place your .ftf fiiles.
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Then download,buy or any other means that are LEGAL "wink wink" (I bought BTW cause I love these guys!), Parallels Desktop 9 or later. Or use Bootcamp if you know what that is and are willing reboot you Mac lots of times just to change something on your phone. To me personally it completely defeat the purpose of having a Mac in the first place although its a nice option.
You can get Parallels Desktop 9 or later legal and get a 14 day trial of it here at their official website here: http://www.parallels.com/downloads/desktop/
Then get yourself a copy of Windows OS (windows 8 recommend cause it comes with inbuilt anti-virus) or try this 90 day free trail of Windows 8/8.1 from Microsoft:
Here is link http://www.microsoft.com/en-gb/business/products/downloads-and-free-trials#/
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Make sure you save the TA file some where safe like google drive, skydrive, drop box, box or all 4 of them
then use flashtool to flash .290 back (root might disappear depending on what you do.)
You can practically use Windows from PD with other guides on xda z1 forum to do the rest of the step. But step 3 is going to be a Nightmare especially on window because you're dealing with drivers and command prompt. If you're not in good terms with these youre going to suffer with these, trust me I know .
Unlocking Bootloader "THE EASY PART!"
Turn off Parallels Desktop open browser and head to: http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
Scroll down to how to unlock bootloader and follow the instruction using Mac OS X.
then check if bootloader is unlocked by dialling *#*#7378423#*#* and go to service info / configuration
If the last line says
bootloader unlocked: Yes
Then its unlocked
If it says
bootloader unlocked allowed: Yes
then it is locked but you can unlock it
If it says
bootloader unlock allowed: No
then you cannot unlock it
Installing a Custom Kernal"THE HARD PART!"
For this you need to First set up ADB and Fastboot on MAC. I will post a link to a very very easy to follow guide on how to do that. This guide is pretty easy to follow but I do advise that you follow it carefully down the way words are spelt other wise you're going to run into problems.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=1917237
Take note on of this step "press CTRL+X to exit, then Y to confirm the save then press ENTER" because people forget to press ENTER and the start complaining.
Now download and unzip DoomKernel from: http://forum.xda-developers.com/showthread.php?t=2448613
Save it some where convenient like the "android" folder you created.
Then open terminal and type the Command while your device in in fastboot mode (turn off phone and connect usb while holding volume up Button, a blue light should be shown on Z1):
"adb fastboot flash boot directory of where you placed the kernel/Z1-DooMKernel-v04.img"
here's an example of my code:
"adb fastboot flash boot /Users/RealibleCandy4/Desktop/android/Z1-DooMKernel-v04.img"
Now you have custom kernel on phone after reboot.
Rooting
Download SuperSU (do not unzip) and place on sdcard from: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Flash SuperSU.zip on one of the recoveries which you can access by either holding Volume down/up key after you see the DooMkernel splash screen and phone vibrates.
Well done You are now rooted!

Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Click to expand...
Click to collapse
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
then use flashtool to flash .290 back (root might disappear depending on what you do.)
Click to expand...
Click to collapse
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.

RealiableCandy4 said:
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Click to expand...
Click to collapse
Or... you know... you could just do it from OS X. Check out my guide, much simpler.
http://forum.xda-developers.com/showthread.php?t=2449244

Seriously?! Backing up TA on Mac or Linux is just a few commands in terminal. Very simple.
Sent from my C6903 using Tapatalk

I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app

RealiableCandy4 said:
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Depends on how you define "safe", I much prefer doing it myself, then I know it is done properly. And what do you mean by mock restoring? You can easily verify authenticity by MD5:ing the TA partition, and subsequently the image taken of it.

Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app

TagEHeuer said:
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
Click to expand...
Click to collapse
Yes flash .290 will fix it make sure you use the latest Flashtool NOT 0.9.11.0.
for firmware I'm using the 14.2.A.0.290 Generic NCB (Unbranded/Nordic) found at http://forum.xda-developers.com/showthread.php?t=2572195
you can find the .290 files on xda z1 general forum
As for root it will disappear when using Flashtool but on you can get it back once you unlock bootloader, flash custom kernel and flash superSU.zip file. Im not sure if you can root 4.3 with a locked bootloader i havent found anything all ask in Q&A section. This guide is for root with unlocked bootloader.

Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............

Not everyone will read the billion guides you've read. The more the helpful. He's not doing any harm to anyone. Yes, quoting OP was a mistake, thank you for pointing it out.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse

RealiableCandy4 said:
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Be my guest, I made it specifically because I wanted people to learn more about their devices and as a result hopefully help increase the average knowledge level on these boards! Let me know if you need any help following it.

meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
I understand what you mean I did mention that in the post. But i also mentioned that the problem with that method is adb and drivers (mainly drivers) I tried doing that myself and I found that dealing with drivers is a pain, but luckly for use mac users we don't have to deal with that which is a good thing. It makes the installation of custom kernels via fastboot easy and you dont have to wake up the next morning wondering why drivers don't work anymore (which i went though) and causing you to look through 100s of forums for a solution. Somestimes the long why is the best way.