Related
I'm not sure how this will be taken by the people here. Everyone seems really helpful when other people ask questions or need help so I may be surprised, but after rooting my Incredible last night and then trying to look into boot animations, removing bloatware and other things I was left with some feelings that took the joy out of being rooted and I wanted to share them.
Laugh if you will, insult if you feel it's necessary. I'm old enough to be able to handle it but beyond all of that I just wanted to say that the "rooting community" are a brilliant bunch of people. The things that you guys do boggles my mind. Since I only just registered I'm forbidden to post links, but if you're so inclined to go read it here it is.
ishootpixels.tumblr.com/
EDIT: I'd also like to add that my wife's netbook is running XP and not Vista. I forgot that we downgraded it (or upgraded however you want to look at it). I've gone back and changed my blog post.
If you would like some help getting where you want to be, PM me and I would be glad to help. I am far from an expert, but after scouring these forums endlessly, I am quite familiar with the process.
@mtag1029 Thanks. I guess my first problem is that whenever I type in "adb" anything, I get that "adb is not recognized as an internal or external command, operable program or batch file."
I've used this method to connect the phone to the netbook...
1. Boot into Clockworkmod recovery by powering off the phone and pressing and holding the volume down and power button until the screen lights up.
2. At the menu press volume down to select Recovery, then press power.
3. At the Clockworkmod main menu select partitions menu, then select mount /system
4. On the computer click Start > Run, and type CMD to open a command prompt.
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
and I get as far as step 6 before I can't go any further which is where I get that message. Right now I'm trying to install a boot animation and sound but I'll also need to be able to get beyond this in order to remove the bloatware. What am I doing wrong?
And THANK YOU again for the help. I'm almost to the point of returning it to stock so I'll at least be able to get Froyo whenever it's released OTA, but I've come so far at this point I'd hate to throw it all away and go back to stock.
IShootPixels said:
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
Click to expand...
Click to collapse
Assuming your sdk folder is in the root of the C drive (i.e. C:\sdk\), the command in step 5 is wrong -- it's supposed to be:
Code:
cd \sdk\tools
with a space. That should get you into the C:\sdk\tools directory, where adb is.
Not sure if the lack of spacing was just a typo, but if not, there ya go Let me know how it works
edit: Just tried cd\sdk\tools, actually works, I thought there had to be a space, but maybe not. I guess the next step would be to make sure there's an adb.exe in your tools folder?
I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Beyond that, when I get into running command lines I have gotten to where it looks like this...
C:\sdk\tools>
No spaces. I'm taking a pic and trying to attach it if my noob status on the forums will allow me.
I don't have the exe file. I didn't need it to root the phone. I don't know where to even get it.
IShootPixels said:
I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Click to expand...
Click to collapse
If you just made the folders, there's nothing in them -- if you go to the tools directory and type "dir", there probably won't be any files unless you extracted some in there.
From the how 2 adb thread by dreamersipaq:
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Click to expand...
Click to collapse
edit: the rest of that thread is located http://forum.xda-developers.com/showthread.php?t=709220 there, if you're interested
gmonox is absolutely correct. You cannot just create the folders. They have to come from the sdk.
Another thing. You mentioned in your blog post that you would like to have froyo. Froyo should be flashed before removing any apps becauseeverything that you have removed will be put back in with froyo.
Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.
IShootPixels said:
Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.
Click to expand...
Click to collapse
Either way works. I renamed mine sdk because I'm too lazy to type android-sdk-windows every time I want to go into adb shell. But it's up to you
Ok, I'm guessing that my question will be answered after I run the setup. I didn't see the link at first to the thread. Apparently my wife's netbook doesn't even have the right java ver. to run the setup.
This is making my brain hurt.
I should have asked this earlier, have you made a nandroid backup?
LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
EDIT: This is going to take awhile I'm guessing. Installing SDK Platform Android 2.2, API 8, revision 2
Okay. The nandroid is the most important. It will save your butt if something goes wrong.
IShootPixels said:
LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
Click to expand...
Click to collapse
Both types of backups are easy to restore, for nandroid you just go into recovery, same place as you backed it up but click Restore and just wait for it. For titanium, go into backup/restore, batch, and there's an option to restore apps, apps+data, and apps+system data I think. If you have the paid version, the apps will all install on their own, but if not I don't think they will.
Are you still on a netbook or can you use a pc? Might be easier if your java's out of date and whatnot to just use a pc, I'm no expert on netbooks but I'd imagine they're stripped down a lot
gmonox said:
Both types of backups are easy to restore
Click to expand...
Click to collapse
Just keep in mind that you need a functioning phone in order to use Titanium. If you mess something up while in adb and the phone will not boot, Titanium is useless. A nandroid however will restore you back exactly how you were before messing around in adb even if the os will not boot.
Well then I'm glad I did the Nandroid BU! Bsically then I guess that because I backed up with Ti first and then with Nandroid, the Nandroid created a back up of my Ti backup. If so I think I just set a record for redundancy.
As for using a netbook, I don't have a choice. I run everything off of my Macbook, or did until now. The only Windows based item in the house aside from my Xboxes is my wife's netbook. I've updated the Java and begun the setup process. I had to do as the thread said and force the http and then go into the available packages and I'm DLing and installing them all because I was afriad that if I didn't I'd find that I needed one I hadn't installed. I'm guessing that since I'm already rooted (and I'm hoping) that once I'm done installing all of these packages that that should be it except for step #4 and #5.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.
I'd also like to add that this is the YouTube video that started this mess. I followed his tutorial on rooting the phone and although the sound was low it was pretty spot on minus one or two things he failed to mention.
However, after watching this video I thought it would be just as easy to install the boot animation as it was to root the phone. Seems the bigger task would be rooting rather than a boot animation. In the hours that you guys have helped me I've learn that this boot video lacks a TRUCK LOAD of information and assumes that the person watching it isn't a noob. Dont' most people that watch tutorial videos watch them because they have no idea what they're doing? I realize now that there's a ton o' stuff missing from it. I still want the animation and sound though.
http://www.youtube.com/watch?v=-Ju9lpH7_4g&feature=channel
Titanium stores backups on your SD card. Nandroid does not backup your SD card, but you are in good shape. Keep us posted.
I'm not sure if step 4 is required, I'm on win7 64bit and I don't recall doing it, but I guess it couldn't hurt. Also, I don't think nandroid backs up your titanium backup -- Ti backup is stored on your SD card
Hey guys.
I've been searching this damn problems all day and cant find a straight forward solution i can use so i resort to asking you guys for help. Im sorry if the solution is easy but i just cant seem to get it.
I was trying to unlock the bootloader today. So i downloaded the SDK and got an unlock code. But then the problems begin. First i missed AdbWinApi.dll. I relocated the file so Fastboot.exe would work. But now it does something and closes up in an instant.
How the hell do i make the screen stay open to enter commands?
Thanks in advance guys.
fastboot has to be done via CMD sounds to me like your double clicking on it.
Cant give you more info than that really out of not wanting you to brick your device, if your struggling to use fastboot to unlock you should think twice about doing it.
also just to add there is NO advantage right now in unlocking the device.
Aightu said:
Hey guys.
I've been searching this damn problems all day and cant find a straight forward solution i can use so i resort to asking you guys for help. Im sorry if the solution is easy but i just cant seem to get it.
I was trying to unlock the bootloader today. So i downloaded the SDK and got an unlock code. But then the problems begin. First i missed AdbWinApi.dll. I relocated the file so Fastboot.exe would work. But now it does something and closes up in an instant.
How the hell do i make the screen stay open to enter commands?
Thanks in advance guys.
Click to expand...
Click to collapse
Yep i've noticed the same thing, there seems to be a .dll missing in the sdk, now worries though, download this fastboot package, i used it to unlock my bootloader
http://www.multiupload.com/BMJ24IL6XY
waz000000 said:
fastboot has to be done via CMD sounds to me like your double clicking on it.
Cant give you more info than that really out of not wanting you to brick your device, if your struggling to use fastboot to unlock you should think twice about doing it.
also just to add there is NO advantage right now in unlocking the device.
Click to expand...
Click to collapse
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Aightu said:
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Click to expand...
Click to collapse
No not at all!
Simple download gingerbreak and root it with that go to market download root uninstaller and off you go.
You change DIR like this:
hold shift and right click on the folder containing the tools select open command prompt here. but please dont do it! not until youve read a lot more.
There is no need right now to unlock the bootloader. Wait for custom roms possibly the weekend i may have a go at a kernel overclock but that's if i get the time wolves are playing sunderland.
Aightu said:
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Click to expand...
Click to collapse
to change directory in a command prompt, use the cd "directory location" command or cd .. to go back a folder
AndroHero said:
to change directory in a command prompt, use the cd "directory location" command or cd .. to go back a folder
Click to expand...
Click to collapse
Ok i finally got the CMD thing running. It just keeps saying: Waiting for device. Ive re-installed the drivers but it still cant really connect. Phone does go into fastboot mode. Anyone got any idea? Because else im just gonne try another laptop.
Fixed, used wrong driver.
Note that the android_winusb.inf file provided by SE is a quick hack (do a diff of both versions to appreciate the workmanship..)
In particular, it will not work as it is on Vista or Windows 7 with AMD x64 CPUs.
To fix it, you'll have to open the .inf file in a text editor, and copy the "; SonyEricsson" line and the 3 lines that follow under the "[Google.NTamd64]" section.
Save it, replug your phone with the search key pressed, and windows should finally be able to accept the driver.
This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
skipster99 said:
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory
Click to expand...
Click to collapse
Or you could add PLATFORM-TOOLS to your PATH environment variable like most people do.
Also, try Droid Explorer.
skipster99 said:
This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
Click to expand...
Click to collapse
All well and good but my simple method after a wipe is to flash a stock rom then CWM root and copy file over .No need to bother with all that Linux stuff and probably easier for noobs and nearnoobs .
jje
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
skipster99 said:
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
Click to expand...
Click to collapse
So now they have two methods pity they will never look or search .
jje
+1 for all that linux stuff -- I love it! Droid Explorer is nice too but I feel like a wuss when I use that program because all its doing is executin linuxy stuff.
Hey, WHY are you nuking your sdcard? Thats overkill!!! but whatever floats your boat!
Hey everyone! I am back with a new question / challenge for everyone. I apologize if this sounds too N00B! I searched in the forum and cannot find a solution.
I am trying to make my Galaxy S4 TOTALLY R/W permanently. Rooting only makes the system directory r/w but there are other directories and locations that also need to be accessible as well. When I was back on the MDL firmware I used a linux command to make the entire drive and phone (everything) R/W using the Terminal ... and for the life of me I cannot remember how I did it.
Can anyone help me out with this? I sure would appreciate it. I am tired of copying files and pasting and tricking it to do what I want when I assign permissions or modify a file. If I remember correctly I ran some linux command that made the ENTIRE phone read / write accessible permanently.
Thanks to anyone who can help!
TheDogman said:
Hey everyone! I am back with a new question / challenge for everyone. I apologize if this sounds too N00B! I searched in the forum and cannot find a solution.
I am trying to make my Galaxy S4 TOTALLY R/W permanently. Rooting only makes the system directory r/w but there are other directories and locations that also need to be accessible as well. When I was back on the MDL firmware I used a linux command to make the entire drive and phone (everything) R/W using the Terminal ... and for the life of me I cannot remember how I did it.
Can anyone help me out with this? I sure would appreciate it. I am tired of copying files and pasting and tricking it to do what I want when I assign permissions or modify a file. If I remember correctly I ran some linux command that made the ENTIRE phone read / write accessible permanently.
Thanks to anyone who can help!
Click to expand...
Click to collapse
Still no replies. Holy smokes. Looks like this one stumped everybody. -smiles-
I have the same issue. I have also been searching around for this.
TheDogman said:
Still no replies. Holy smokes. Looks like this one stumped everybody. -smiles-
Click to expand...
Click to collapse
u talking about a simple chmod 666 ?
What would the reason be in doing so ? I only ask to see the reason behind why you would need to do so
hednik said:
What would the reason be in doing so ? I only ask to see the reason behind why you would need to do so
Click to expand...
Click to collapse
+1. Sounds like a disaster waiting to happen.
jd1639 said:
+1. Sounds like a disaster waiting to happen.
Click to expand...
Click to collapse
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
TheDogman said:
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
Click to expand...
Click to collapse
I still wonder what it is you are trying to do. Honestly I can't see much of a reason because most things I do are done in Root Explorer (hands down the best file explorer and worth the price) and it's merely clicking the button to make R/W and then altering what it is I need to do. What firmware are you on by the way ? You stated you were on MDL but not now. I might only assume you are on one of the more locked down firmwares like MK2 or MF3 and maybe it is not possible.
The chmod comment was not a dig at anyone and he was asking if that is what you are trying to do as in linux cdmod 666 makes the file system R/W.
What other directories are you trying to make R/W ?
TheDogman said:
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
Click to expand...
Click to collapse
Wasnt trying to be cute. Open terminal, type su chmod 666 /path/to/folder. As others have said, be very careful what you're setting to rw. Chmod is command to change user perms and 666 is rw.
Sent from my SGH-I337M
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
StonerSteve420 said:
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
Click to expand...
Click to collapse
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
jinkerz9430 said:
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
Click to expand...
Click to collapse
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
StonerSteve420 said:
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
Click to expand...
Click to collapse
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
jinkerz9430 said:
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
Click to expand...
Click to collapse
Can you link me to the adb you used. It just keeps opening and closing.
StonerSteve420 said:
Can you link me to the adb you used. It just keeps opening and closing.
Click to expand...
Click to collapse
Let me see if i can find it. If not i will zip it and send it to you
jinkerz9430 said:
Let me see if i can find it. If not i will zip it and send it to you
Click to expand...
Click to collapse
Thank you
StonerSteve420 said:
Thank you
Click to expand...
Click to collapse
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
jinkerz9430 said:
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
Click to expand...
Click to collapse
Still doing it. I must be the one person who's screwed lol
StonerSteve420 said:
Still doing it. I must be the one person who's screwed lol
Click to expand...
Click to collapse
Have you tried to run it in administrative mode?
jinkerz9430 said:
Have you tried to run it in administrative mode?
Click to expand...
Click to collapse
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Here, use this.
https://forum.xda-developers.com/showthread.php?t=2588979
Best for noobs.
It it asks about system wide say yes.
Then hit Windows key and R and type cmd. Then run your commands. The installer should also work.
StonerSteve420 said:
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Click to expand...
Click to collapse
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
jinkerz9430 said:
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
Click to expand...
Click to collapse
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
StonerSteve420 said:
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
Click to expand...
Click to collapse
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
jinkerz9430 said:
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
Click to expand...
Click to collapse
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
StonerSteve420 said:
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
Click to expand...
Click to collapse
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Thank you. I'll try that when I get home.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
StonerSteve420 said:
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
Click to expand...
Click to collapse
but are you in fastboot mode now? because after you have done the OEM unlock and then after that use usb debbugging then accept the prompt it shows about giving authorization to your computer, then after that you must go to fastboot mode to start the process of root