Related
HTC Thunderbolt Windows One Click Root
This is a simple batch file that will guide you in rooting your device.
It is pretty easy to follow along but please take your time and read everything. It has only been tested a few times so please report any errors or issues you find.
Huge thanks to NetForce-TX on IRC for testing along with helping, I owe you!
Also thanks to Jcase for guidance
TeamAndIRC and Captainkrtek (Me) are NOT responsible for any bricks, fires, or damaged/broken hardware due to this process
If you wish to read the batch files contents either open it with notepad or check the pastebin
Instructions are included in the file when running it along with where to get the necessary files.
Prerequisites:
Drivers Installed & Working
SDK Installed with ADB
Exploits.zip with contents extracted to your ADB dir
PG05IMG.zip
Downgrade RUU
A Thunderbolt running 605.6 or 605.9 Firmware
You can download the OneClickRoot here
I will update this from time to time if needed, If you have issues with the batch file please PM me on XDA or find me on irc.andirc.net #Thunderbolt.
I will not reply to your PM if you want me to help you root your phone!
UPDATE: If SU acts up (IE: Force closes) flash this via CWM
Reserved for Linux version
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
pinhead875 said:
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
Click to expand...
Click to collapse
Thanks! It is pretty simple, only a few things you have to do manually (no possible workaround) such as flashing from the bootloader.
Anyone try this yet?
sent using Tapatalk on the TB.
egeorgia said:
Anyone try this yet?
sent using Tapatalk on the TB.
Click to expand...
Click to collapse
Already a few people have tested it, all successes
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the other root ;set up my ADB earlier but chickened out... i already have the files downloaded
Cg006 said:
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the ot her root and set up my abd earlier but chickened out... i already have the files downloaded
Click to expand...
Click to collapse
Yeah exactly, just debug and charging, until you have to copy over the roms then you will set the USB mode to mount SD
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
alphatectz said:
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
Click to expand...
Click to collapse
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Captainkrtek said:
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Ok, I'll unroot and use the one click method. Thx
can we get a poll maybe to see success rate
Can we get a Step by Step Instruction Guide? it would be nice for us beginners
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
b33zy682 said:
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
Click to expand...
Click to collapse
You need to put the contents of exploits.zip in the same directory ADB is in
ok what in that zip needs to go where?
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
b33zy682 said:
ok what in that zip needs to go where?
Click to expand...
Click to collapse
take everything that is in exploits.zip and move it to your android sdk directory specifically the location of adb.exe (will either be in platform-tools or tools) as for the two RUUs, they can be anywhere but you will have to move them at one point to your SD card. That is about it
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
Yes you should
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
damn right! lol
Here's the NANO text editor for the Android. This is not completely my work, I just compiled the threads I found on the net and made the flashable zip only.
I tested a little bit with Terminal Emulator and seems like it's working fine.
Enjoy.
Installation: Just flash with recovery. Requires aprrox. 1.5mb space in System partition.
Hi
Thanks, i didn't try it ('cause I already have nano) but i think this flashable solution is the easier for installing nano! :good:
Great!!
Thanks
What is that
Sent from my HTC Desire using xda app-developers app
SeeZaar said:
What is that
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
An editor like vi/vim for *nix based machines. I would say more friendlier than vi/vim.
And what is vi/vim? XD
Sent from my HTC Desire using xda app-developers app
Moving to Desire Themes and Apps as this shouldn't have been in dev to begin with.
theGanymedes said:
Here's the NANO text editor for the Android. This is not completely my work, I just compiled the threads I found on the net and made the flashable zip only.
I tested a little bit with Terminal Emulator and seems like it's working fine.
Enjoy.
Installation: Just flash with recovery. Requires aprrox. 1.5mb space in System partition.
Click to expand...
Click to collapse
Thank you but I can't save file after editing, because I can't press "^" and "0" at a time ......
Any workaround ?
Thanks again in advance for salutation
monitorstudioworker said:
Thank you but I can't save file after editing, because I can't press "^" and "0" at a time ......
Any workaround ?
Thanks again in advance for salutation
Click to expand...
Click to collapse
Maybe you can look at the "settings" section of your terminal emulator. Some emulators make Volume Up key as Control character etc.
theGanymedes said:
Maybe you can look at the "settings" section of your terminal emulator. Some emulators make Volume Up key as Control character etc.
Click to expand...
Click to collapse
Thanks for replying, but I mostly used it in recovery via aroma file manager, and there's no setting so far ...
I want to edit updater-script without rebooting and computer I have zip and unzip binary yet, but no text editor (echo "" >> is not a good way to do my work)
Much thanks, it works!
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.
I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.
atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?
lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.
New version won't install on Kit Kat
PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.
atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt
Are extracted files accessible in file system? I can't find them
levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM
PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...
It seems that the image you want to unpack it is not an android image.
atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
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
Hi so I updated to Windows 10 Creator's update and now when I go to my platform tools and shift right click it only gives me option for powershell I can't click on cmd. I can search computer and open cmd but it's not in the right directory and can't run adb commands.
check the image
AndrewM3 said:
Hi so I updated to Windows 10 Creator's update and now when I go to my platform tools and shift right click it only gives me option for powershell I can't click on cmd. I can search computer and open cmd but it's not in the right directory and can't run adb commands.
Click to expand...
Click to collapse
Hello,
Follow this link, it's a simple change: https://insidewindows.net/2016/12/1...-window-here-option-in-build-14986-and-newer/
Good luck...
Puck24 said:
check the image
Click to expand...
Click to collapse
Hello,
This won't help in case you want to open a command prompt in a specific folder. Check the link above...
Cheers...
EDIT: updated link. Tested it myself and the previous one didn't work. This one does :good:
Also, just in case you would like to go back to previous state, instead of deleting the cmd DWRD as stated on part 10 of the tutorial
10. Delete the DWORD with the name HideBasedOnVelocityId.
I suggest you right click on the name, select "rename" and just add an underscore _ like this _HideBasedOnVelocityId
Do the same if you follow the second part of the guide and want to hide the "Open PowerShell window here"
Cheers
5.1 said:
Hello,
Follow this link, it's a simple change: https://insidewindows.net/2016/12/1...-window-here-option-in-build-14986-and-newer/
Good luck...
Hello,
This won't help in case you want to open a command prompt in a specific folder. Check the link above...
Cheers...
EDIT: updated link. Tested it myself and the previous one didn't work. This one does :good:
Also, just in case you would like to go back to previous state, instead of deleting the cmd DWRD as stated on part 10 of the tutorial
10. Delete the DWORD with the name HideBasedOnVelocityId.
I suggest you right click on the name, select "rename" and just add an underscore _ like this _HideBasedOnVelocityId
Do the same if you follow the second part of the guide and want to hide the "Open PowerShell window here"
Cheers
Click to expand...
Click to collapse
This didn't work for me. I tried renaming first and then deleting the entry. None worked. I went back and tried again and all the settings are already correct as per the guide. I did it again anyways and still nothing even after a reboot. Not a huge deal since I can still just open CMD and cd to the correct location. I have mine at c:/SDK/platform-tools so it isn't a huge pain. Any ideas? I took the latest Creator update.
5.1 said:
Hello,
Follow this link, it's a simple change: https://insidewindows.net/2016/12/1...-window-here-option-in-build-14986-and-newer/
Good luck...
Hello,
This won't help in case you want to open a command prompt in a specific folder. Check the link above...
Cheers...
EDIT: updated link. Tested it myself and the previous one didn't work. This one does :good:
Also, just in case you would like to go back to previous state, instead of deleting the cmd DWRD as stated on part 10 of the tutorial
10. Delete the DWORD with the name HideBasedOnVelocityId.
I suggest you right click on the name, select "rename" and just add an underscore _ like this _HideBasedOnVelocityId
Do the same if you follow the second part of the guide and want to hide the "Open PowerShell window here"
Cheers
Click to expand...
Click to collapse
Thank you so much it worked for me followed the instructions to the line and it worked really thankful.
AndrewM3 said:
Thank you so much it worked for me followed the instructions to the line and it worked really thankful.
Click to expand...
Click to collapse
What the heck, I wonder why it isn't working for me. Is your username (for step 6) a single word or two? Mine is my first and last name. I don't think that should be an issue since when I type it in and hit check names it shows up as PC NAME\FIRST LAST so it doesn't seem to have any problems with that. Checked the box under it, deleted registry key. Changed admin to full control & nothing. Tried giving USER full control as well and nothing.
I've followed the steps 100% about 8 times now, I know I'm not missing anything, but it just won't work for me. :crying:
RoyJ said:
What the heck, I wonder why it isn't working for me. Is your username (for step 6) a single word or two? Mine is my first and last name. I don't think that should be an issue since when I type it in and hit check names it shows up as PC NAME\FIRST LAST so it doesn't seem to have any problems with that. Checked the box under it, deleted registry key. Changed admin to full control & nothing. Tried giving USER full control as well and nothing.
I've followed the steps 100% about 8 times now, I know I'm not missing anything, but it just won't work for me. :crying:
Click to expand...
Click to collapse
For user name I just put my email and hit ok then it automatically put my first and last name. Also make sure to allow full control for administrators. Then delete the dwords
AndrewM3 said:
For user name I just put my email and hit ok then it automatically put my first and last name. Also make sure to allow full control for administrators. Then delete the dwords
Click to expand...
Click to collapse
Yep yep, did those both and still no dice. Just powershell. IDK what's going on.
AndrewM3 said:
Thank you so much it worked for me followed the instructions to the line and it worked really thankful.
Click to expand...
Click to collapse
Hello,
Google FTW! I just typed a few keywords and the tutorial showed up. Glad it helped you...
Cheers...
RoyJ said:
Yep yep, did those both and still no dice. Just powershell. IDK what's going on.
Click to expand...
Click to collapse
Hey,
Not sure what's the problem. I tried it before posting, because i didn't want to post it just assuming it would work. Check the attached screenshot. Just followed the tutorial and i got "Open command window here" back...
Yeah it's not working for me. Oh well.
RoyJ said:
Yeah it's not working for me. Oh well.
Click to expand...
Click to collapse
I don't give up so easily :good:
Try adding this *.reg file: Enable Command Prompt.reg
Just double click and accept... Open it if you wish, basically, it's just the "HideBasedOnVelocityId" renamed to "_HideBasedOnVelocityId"
I didn't find infos if it also needs proper permissions.
Let me know if it works...
Also adding a "disable command prompt" in case you want to revert the change. I just found the *.reg somewhere and edited it a bit...
Cheers...
5.1 said:
I don't give up so easily :good:
Try adding this *.reg file: Enable Command Prompt.reg
Just double click and accept... Open it if you wish, basically, it's just the "HideBasedOnVelocityId" renamed to "_HideBasedOnVelocityId"
I didn't find infos if it also needs proper permissions.
Let me know if it works...
Also adding a "disable command prompt" in case you want to revert the change. I just found the *.reg somewhere and edited it a bit...
Cheers...
Click to expand...
Click to collapse
Hey thanks, I'll be out for a couple hours but I'll try it when I get back!
RoyJ said:
Hey thanks, I'll be out for a couple hours but I'll try it when I get back!
Click to expand...
Click to collapse
I tried the *.reg file just for fun and it seems it still needs proper permission though...
By the way, did you properly set the full control at step 9?
Strange, but after a reboot it disappeared for me until i set "full control" for my username (Seb desktop as you can see on the attached screenshot) and not administrator as per the tutorial... This thing is really weird. Doesn't work for you, disappear after reboot for me, lol...
Good luck...
Option in settings for powershell or CMD... I think
dontbeweakvato said:
Option in settings for powershell or CMD... I think
Click to expand...
Click to collapse
Hello,
Where?
Thanks...
5.1 said:
Hello,
Where?
Thanks...
Click to expand...
Click to collapse
I remember someone complaining that powershell was default and told me how to change it. Right click taskbar then navigation or properties. I'll look tomorrow if that isn't correct. My mind is so foggy sometimes
dontbeweakvato said:
I remember someone complaining that powershell was default and told me how to change it. Right click taskbar then navigation or properties. I'll look tomorrow if that isn't correct. My mind is so foggy sometimes
Click to expand...
Click to collapse
Hey,
Check the OP and the second post of this thread. This doesn't have anything to do with what we are trying to achieve...
Thanks though...
5.1 said:
Hey,
Check the OP and the second post of this thread. This doesn't have anything to do with what we are trying to achieve...
Thanks though...
Click to expand...
Click to collapse
yea thats wrong, I was half a sleep. I remember someone telling me about switching from ps couple of days ago but as usual i wasnt listening.
Just put "./" before your commands in power shell.
(Without the quotes if that isn't obvious)
ajgftw said:
Just put "./" before your commands in power shell.
(Without the quotes if that isn't obvious)
Click to expand...
Click to collapse
Hey,
I set adb + fastboot path in environment variable and forget about it...
Still your post doesn't help to replace powershell by Command prompt using contextual menu which is the matter of this thread... :good:
Chers...