Ive tried the black prince video, the unlockr method and the original xda perm root guide and my G2 will not perm root. Seriously need some help.
do you have adb and sdk installed?
>
no such thing!
its just smarter than you (;
lol
it is funny that you mention the black prince video, because that is what i used. im not sure, but i followed that video exactly and got it my first try. just watch the video very carefully, and follow EVERYTHING that he does and it should work. if not, then i am really not sure. obviously, you just need "S-off"
Are you using Visionary ? I would suggest the rage method, IMHO it's a lot more reliable and you can see if anything goes wrong because you're using individual commands.
i know its possible because I rooted my friends G2 just days before I got mine. I don't have adb, to be honest as soon as i see that it takes more than just installing a program on my pc, i flee, and its not because im new to android or rooting or anything like that, i just don't have a whole lot of spare time. And i DO have S-OFF. Like ill do everything in the blackprince video, then after I'm done I'll got and test the root by typing SU in terminal, and it says permission denied. Or for any of the other methods, same thing.
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
adamtheindien said:
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
Click to expand...
Click to collapse
Download HTC Sync from the HTC website (look in the downloads section), and install that on your PC. That'll give you all the USB drivers you need.
Download the Android SDK from http://developer.android.com/sdk/index.html and install it on your PC. Be sure to read the guide on installing it at http://developer.android.com/sdk/installing.html
Plug your phone in to your PC using the original HTC cable (do not use a third-party cable for this) and type "adb devices" at your PC's command prompt, and tell us if it can see your phone. It should show up your phone's serial number (don't tell us exactly what that is, this is a public forum), but if there's an error then we need to sort that first.
Edit - partially prompted by this request, I've started an "adb for Noobs" guide (very much a work-in-progress) at http://forum.xda-developers.com/showthread.php?t=865685
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
http://www.youtube.com/watch?v=A1SOSXwkc_8
adamtheindien said:
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
Click to expand...
Click to collapse
when you type adb devices does it recognize your device?
Super easy way.... http://forum.xda-developers.com/showthread.php?t=834228 just copy paste the codes.
Your phone might be s-off, but not allowing you to do any su commands. Mine was, but I just installed rom manager and it flashed clockwork recover no problem, then I flashed cyanogen and everything was good. Go into hboot and just make sure it says s-off, then do the rom manager bit. Try it and see if it works.
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
yeah, but i cant use rom manager since i dont have super user permissions. do i just temp root then try to install a rom? that seems sketchy. haha.
Earlier you said that you have S-OFF. If this is the case, then just open up Market and download Superuser by ChainsDD. Then you should be good to go.
adamtheindien said:
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
Click to expand...
Click to collapse
When you type "adb" on your PC, Windows needs to know where to find the "adb" program to run it. So you either need to specifically add the directory containing adb to your Windows PATH variable (which you can do in the environmental variables section, which will be in different places on different operating systems - on XP you need to right-click on My Computer, then select Properties, then Advanced, then the "Environmental Variables" button) - or you need to cd to where adb is stored under where you installed the Android SDK, and run it from that folder.
pretend youre explaining this to a five year old...
ok, which operating system do you have on your PC ?
Where did you install the Android SDK, i.e. which folder on the PC did you put it in ?
never mind guys, did what that dude said and just installed a rom with temp root and im all good now. thanks for everyones help though, sorry for my lack of knowledge in adb and what not.
guys dont flame me I looked through the threads. I wiped my computer so far i have the hercules drivers, odin, toolkit lol on here already
but I never used ADB terminal commands before and I been wanted to learn so Im going to give it a shot.
been looking around the threads but I cant find any downloaded file for adb, well I found one and it have fastboot files in it and I understand the htc phones uses fastboot, is it going to be the same as ours? and please I need to know where to put the adb files, for commands.
can you provide me with a link of the actuall adb the I need? when to moved the folder and etc etc.
some threads did not just tell you much about adb just tells you that you need them.
android sdk. Also check out developer.android.com
Sent from my SGH-T989 using xda premium
Hi developers and non-developers
I have like a proyect idea but I don't know it its possible. You have seen that we can use adb on our terminal to root other devices like root transmissor app
But fastboot commads are not enabled on terminal so I think I could be very useful if we can flash recoverys,kernels,complete systems
Only whit our phone like HOX in my case.
I know adb is located on system/bin/adb.....and is really realliy similar to one on computer(.exe)
But mi question is...can we convert the fastboot.exe on a runnable block on our terminal??
If you have ideas or more knoledge on this subjet than me, please help me..I think making this will help all of us
I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.
jerzykid said:
I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.
Click to expand...
Click to collapse
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.
sleekmason said:
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.
Click to expand...
Click to collapse
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.
jerzykid said:
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.
Click to expand...
Click to collapse
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.
SOLVED
sleekmason said:
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.
Click to expand...
Click to collapse
so changing the path to the folder containing adb.exe was correct but I had to put the recovery.img directly like many have said. In Windows the command prompt doesn't always default to C:\(or whatever your main drive is called) and you have to manually change this.Most people are fairly fluent with command promt but for those who aren't you must use " cd.. " (without quotes)to change the path to your base directory. i hope this helps anyone else.I've seen others explain it but not detailed enough
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Edit: for some reason sudo -s finalize_device device/nextbit/ether worked but have some other issues with building efi droid.
AnierinB said:
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Click to expand...
Click to collapse
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
VenomMOD said:
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
Click to expand...
Click to collapse
Darn it.. it's been getting to me for a few days now and I even got lk.img to boot and configured so alls that needs to be done is the finalize_device and then off to compiling uefi. Oh well, at least I got that close :crying:
Windows it works without it but cant compile jack on that xD
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
bback78901 said:
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
Click to expand...
Click to collapse
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
AnierinB said:
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
Click to expand...
Click to collapse
Forgot to add, I only use it on Windows 10.
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
valhallen.282 said:
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
Click to expand...
Click to collapse
Got it to bypass needing -i 0x2c3f just by typing sudo -s before my fastboot cmd.
Try it