Database Info

[Q] rooting inspire questions

Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!

Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!

He said the adb drivers won't connect

Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software

We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?

trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol

did u ever find out y adb wont connect im having d same problem

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer

Need help with samsung skyrocket root!!

So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.

is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.

shansmi said:
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
Click to expand...
Click to collapse
I have not changed anything since the first success of my Skyrocket root. It's weird that it would root the first Skyrocket but not the second one.

I used this one.
http://androidadvices.com/root-samsung-galaxy-s2-sky-rocket-4g-sgh-i727-tutorial/

Solution for "Files not found" and "permission" when trying to run ZergRush
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!

trying to root
ashque01 said:
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
Click to expand...
Click to collapse
I still get errors "system cannot find the path specified" and it doesn't work.
ashque01 you put "D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat"
I didn't get that to work until I switch the > to a \ the arrow instead of a backslash makes a difference, beg pardon but I don't know dos very well and I did use the arrow with no success, lol...
Once in the command prompt (you get there by typing exactly that "command prompt" in search bar, after clicking the start button in windows 7) Right click on command prompt to run as administrator.
I put D:\DooMLoRD_v3_ROOT-zergRush-busybox-su\runme.bat because that's where I used 7zip to extract it to, in the root of hard drive partition. It ran but with errors and announced done! press any key to continue.
I tried it again by creating a subfolder on the D: partition named android like you did, tried it again, same thing,
Still hoping to get a superuser icon so I can download my root explorer app from the market.

YAY!
I got root.
I told all of about it in that thread I started titled s#%rocket. I did admire what Entrophy remarked about it's hardware being disagreeable, but that was in the i777 thread. I had no business there (mod moved my thread, thank you) as my handset is i727.
I coulda swore that's what about phone said before I started but sure enough when you pull the battery it says i727 right there, can't argue with that, I was just being "elevator up, but door not open"
Beg pardon

androiduser1 said:
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
Click to expand...
Click to collapse
use 2.3 not 2.2
Sent from my SAMSUNG-SGH-I727 using xda premium

Can't Root TF700 32gb

I can't root my TF700 32gb
when i try to use the Rootdebugfs, the screen pops up and says
"you did not select an option. exiting...
press any key to continue"
i followed previous steps, (unknown sources and USB debugging)
and tried to do this several times, still no go..
what am i doing wrong then?

Here
See if this YT vid helps... http://www.youtube.com/watch?v=xUCBHPyvYDI
Good luck!

did that same error.

I had some issues with rooting as well. You can just open the bat file, and once you see the section with the commands, run each line separately from the prompt. Look for a thread titled roots, bloody roots, sorry but I am on my phone and at work, but that thread explains what I am saying about manually running the commands. Worked like a charm for me. NOTE: Ignore when it says files not found and a few other errors, just run SU after, then check with root checker. Getting superuser installed and working is key, as far as my experience. Rooted 3 Infinitys this way. Good luck
Sent from my SAMSUNG-SGH-I727 using xda premium

psyclon9 said:
did that same error.
Click to expand...
Click to collapse
Sorry bout the no help...looks like you or someone else commented there also.
I wonder if you got a bummed out debugfs.bat file.
Which pc OS\version are you trying to install from?

Thats OK said:
Sorry bout the no help...looks like you or someone else commented there also.
I wonder if you got a bummed out debugfs.bat file.
Which pc OS\version are you trying to install from?
Click to expand...
Click to collapse
Im using windows 7 64bit ultimate/pro version.

Still dont know whats wrong with this.

I read somewhere that having ADB already installed on your PC causes the defrags method to have problems. If you have ADB install, uninstall.
I've done it on two TF700T--C7 and C8--both on .26 update, and it worked like a charm. I did run defrags on a Windows 7 64bit machine, 32 bit should run fine as well.

I had some problems trying to root too and had to use an older version of Rootdebugfs

I have ADB installed on my comp. I ran the Rootdebugfs method just fine? Maybe you have driver issues connecting?

I never have installed ADB and rooted with no problumz.

[Q] HELP - Atrix 2 Rooting?

I have been trying to root for months now, but I can't seem to do it. My friend, who is very knowledgeable about technology, couldn't even figure it out.
I followed all the steps that are listed. I connected as a camera (PTP) with USB debugging enabled using the cable that came with the phone, disabled my antivirus, ran adb.exe, ran ROOT.bat, and not much is happening. adb.exe appears to be working, because a command prompt window opens up and a bunch of text scrolls through, which I assume is supposed to happen. Then I run ROOT.bat, and a command prompt window opens and says * daemon not running. starting it now * * daemon started successfully *. That's it, nothing else happens. The phone is supposed to reboot a few times, but it doesn't, even when I wait 30 minutes.
My phone is running ICS, and I know I downloaded the ICS root program.
I'm not technologically illiterate, but I'm far from an expert.
Any suggestions would be highly appreciated.
EDIT: Just remembered some information that might be useful. Someone suggested to me that I use ADB driver installer (can't link to it because new user - just google it), but my phone doesn't even show up on the list when I run the program. That might mean that my computer doesn't recognize my phone as a phone? I'm not sure. Anyway, I thought that would be helpful.
Thanks.

Do a backup and try a factory reset. I had this same problem while rooting my friends phone... And do not run the adb.exe ...just double click the ROOT.BAT file... That's it.. His phone was full of apps and very slow...I did a factory reset...and it worked...oh and make sure USB debugging and unknown sources is ticked (unknown sources is under settings> security)..
Sent from my MB865 using XDA Premium 4 mobile app

nikhJ said:
Do a backup and try a factory reset. I had this same problem while rooting my friends phone... And do not run the adb.exe ...just double click the ROOT.BAT file... That's it.. His phone was full of apps and very slow...I did a factory reset...and it worked...oh and make sure USB debugging and unknown sources is ticked (unknown sources is under settings> security)..
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to try that, but I've run into an issue. All of my contacts are saved in AT&T's address book, but I want to make a backup of them. However, I can't, because I can't seem to transfer the contacts to Google. How did you get around this?

is there a main thread on rooting? Im not finding it if so.
Just need instructions and the files. Thanks
Edit: The phone was given to me because he dropped it in water, its sitting in a bag of rice right now, I dont know what version of the OS he's running. My question is does the root work for all versions? or is it specific?

ebcrew said:
is there a main thread on rooting? Im not finding it if so.
Just need instructions and the files. Thanks
Edit: The phone was given to me because he dropped it in water, its sitting in a bag of rice right now, I dont know what version of the OS he's running. My question is does the root work for all versions? or is it specific?
Click to expand...
Click to collapse
here is the general thread for rooting
http://forum.xda-developers.com/showthread.php?t=1742879
to know your mobile android version just go to "settings" and slide down to "about phone" check in android version if it 2.3.4 or 4.0.4 then choose the right method for rooting from the rooting thread.

[Q] Problems updating to Lollipop

Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!

iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend

Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?

You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start

Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly

Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.

Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.

Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?

iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.

this is what I pasted:
;c:\adb_fastboot
?

iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.

Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...

Oy vey
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse

OK so my path is broken so I won't be able to run adb commands?

Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands

Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?