Related
Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3
Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release
If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble
Droid Support!!!!
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market
Donate version now just to support me, added support for all devices to free version.
Please donate!
1.3 version uploaded
See changelog.
Any updates on newer phones?
KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.
Warning! I don't recommend this to users who are new to Android since there is a possibility of bricking your device. I will not be responsible if this happens.
It will downgrade everything even the HBoot using a HTC signed ROM. I've downgraded RUU_Saga_Telstra_WWE_1.36.841.3 with HBoot 0.98.0002 to Hboot 0.98.0000 of RUU_Saga_HTC_Thailand_1.35.1113.2.
First you need below tools and applications. I will not explain everything since I'm assuming you already know how to use it and make it.
1. ADB tool to access you device thru shell.
2. ADB driver - you may install HTC Sync since it has ADB driver in it.
3. HEX Editor - I used HxD.
4. Spare micro SD with Goldcard.
5. Card reader to make your life easier.
6. Update.zip ROM you will use to downgrade(rename it to PG88IMG.zip).
6. GingerBreak-v1.20.apk to temp root our device.
Step 1: Copy GingerBreak-v1.20.apk to your spare micro SD and insert it into your phone.
Step 2: Enable USB debugging in your device and connect it to your PC(Charge only). Make sure the drivers are installed properly. If not, install HTC Sync.
Step 3: Install and run GingerBreak-v1.20.apk. It will force close other apps(this is normal just close it). The gingerbreak application will promp that something goes wrong with the rooting(can't remember the actual spiel) but actually we already have our temp root.
Step 4: Run you ADB tool and issue command su to have root access. You can now see in your device that Superuser app is prompting you to allow the ADB root access. Accept it.
Step 5: On the # prompt, issue command dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard/mmcblk0p17.img (to copy mmcblk0p17 to your SDcard). Power off your device and copy mmcblk0p17.img to your PC.(You can also use the command shell to copy it into your PC if you know how to do it).
Step 6: Open mmcblk0p17.img using your Hex editor. On the 11th line(I think), modify the current version to 1.28.401.1(since this is the lowest version I know). Save it and copy back to SDcard. Insert the sdcard and turn your phone on.
Step 7: Run GingerBreak-v1.20.apk again and follow step 3 to 4.
Step 8: On the # prompt, issue command dd if=/mnt/sdcard/mmcblk0p17.img of=/dev/block/mmcblk0p17 (to copy back mmcblk0p17.img to your phone). Do this as quickly as possible since the temp root access sometimes loose its effect.
Step 9: Power off your device and remove your SDcard. Using your card reader, delete everything(not format) in your microSD(with Goldcard) and paste your PG88IMG.zip.
Step 10: Hold volume down + power to boot to recovery and the phone will do the installation itself. Wait until you have your downgraded ROM.
This is how I do it. Hope you won't encounter any problem with this procedure. Good luck!
I want to give thanks to all the XDA members for the knowledge I acquired for this procedure and to the developer of Gingerbreak.
You may also check sonikz procedure on post #4. I think his procedure is faster. You may use which one is easier for you to follow.
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
Good question i think, if i remember well, on the desire (or HD?) sometimes downgrading was a way of getting to a version of software where you then could get root again !From that point on you could get a recovery installed and install some nice roms. I dont know if thats whats going on here, i wouldn't dare to hope that ...?
Me n00b me downgrade
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This copies the files to the phone and changes the permissions so they will function
adb shell
Click to expand...
Click to collapse
This will enter the terminal for the phone
./data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
cd /data/local/tmp
./misc_version -s 1.27.405.6
Click to expand...
Click to collapse
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.
This can be used with paulobriens test signed RUU HTC update to get root/boot/recovery installed on s-on .
If it just were public
Sent from my HTC Desire S using XDA Premium App
panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
This is why I recommend this only to advance users.
Our Desire S with S-On was released with Gingerbread ROM and Hboot that still not possible(as of now) to have custom boot recovery. Since we are on S-On, it is still not possible to be rooted and use custom ROM.
As far as I know, we don't have any official ROM except for Gingerbread. Correct me if I'm wrong. The list can be seen in this post. http://forum.xda-developers.com/showthread.php?t=1002506
I'm just sharing this to people who wants to change their ROM if they want to change to a different one. Like me who installed the latest ROM from TELSTRA and find the bloatware annoying. I've done this to get back to the ROM I'm more comfortable using.
Yeah I'm pretty much with you mate, no way to do anything more practical than flash a clean European Rom currently..... Not really a vast amount of progress either. Anything we should be doing to help get permanent root? Anyone?
Sent from my HTC Desire S using XDA App
Thankkssssss
It works on my s-on DS
Thanks a lot
i really like it how sonikz is doing now like it was his idea how to downgrade it using adb gingerbreak and misc_version lol
i'm gonna stop my rooting tries + supporting here for the desire s, hating such people like him
I never said it was my idea and I have in a posted my thanks to the relevant people in other threads, I didn't mean to rub anyone the wrong way... I hadn't seen a adb version of gingerbreak until Friday and I'm sure you know the apk is very unpredictable or at least it is on my phone so I couldn't use misc_version, it just kept kicking errors.... Hey I just threw it out there, my bad
okay
no it isnt the apks fault, maybe u forgot to use "su" in adb shell after using the apk, which u dont need for the command line version
anyway, maybe there is a way to get past the s-offf
in titanium backup there's a recovery exploit to remove files from s-on phones
we just need to know how the exploit is working and if it still working with 2.3
2nd option is i am getting a 2nd desire s soon.. it's a bugged on, radio destroyed and he don't get it repalced so he gives it me
maybe i can get the desire hd bootloader running somehow.. even if i am sure it will be a lot of work to get in
Plz guys... Get a grip.. we share.. whocares about credit.. come on..
Keep sharing.
Sent from my HTC Desire S using XDA Premium App
Worked
Sent from my HTC Desire S using XDA Premium App
@Rexton270: what worked?
@brokenworm: what you meant by the paulobriens test RUU?
@brokenworm:
it's not paul's ruu, the files he published been released 1 day before at 911snipers blog
sadly without ruu too
what ROM to get root
after doing that, what ROM is it better to download in order to become root ?
thanks
pdaGeek13 said:
after doing that, what ROM is it better to download in order to become root ?
thanks
Click to expand...
Click to collapse
If you are on S-ON, none as of now.
Sent from my HTC Desire S using XDA Premium App
> 2 hours
running for more than 2 hours now, normal ?
sonikz said:
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
This copies the files to the phone and changes the permissions so they will function
This will enter the terminal for the phone
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.
Click to expand...
Click to collapse
no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart
Blezz said:
no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart
Click to expand...
Click to collapse
same thing with this log:
$ ./GingerBreak
./GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 s
[**] (C) 2010-2011 The Android Exploid Crew. All rig
[**] Kudos to jenzi, the #brownpants-party, the Open
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 25104 GOT start: 0x00014360 GOT end: 0x000
[*] vold: 25104 idx: -1024 fault addr: 0xfffb2284
[*] vold: 25162 idx: -2048 fault addr: 0xfff4e284
[*] vold: 25212 idx: -3072 fault addr: 0xffeea284
[*] vold: 25262 idx: -4096 fault addr: 0xffe86284
[*] vold: 25312 idx: -5120 fault addr: 0xffe22284
[*] vold: 25363 idx: -6144 fault addr: 0xffdbe284
[*] vold: 25414 idx: -7168 fault addr: 0xffd5a284
[*] vold: 25466 idx: -8192 fault addr: 0xffcf6284
etc ....
and sometimes:
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
:-(
::::::::::::::::::::::::EDIT:::::::::::::::::::::::::::::::::::::::::::::
Bin4ry has come up with a way to root many android phones
http://forum.xda-developers.com/showthread.php?p=31545627
UltimateSeo at Android Forums has made a version that will work on the Hydro
http://androidforums.com/hydro-all-things-root/619232-kyocera-hydro-confirmed-working-root.html
I will leave the info in this thread intact, someone may find some use for it
::::::::::::::::::::::::EDIT:::::::::::::::::::::::::::::::::::::::::::::
Hi all
I am new here, I hope it is OK that I posted this in this forum, if not please delete.
I could not find the ADB USB drivers for the Kyocera Hydro, on the Kyocera web site, so I decided to modify the Kyocera Milano driver to work with this phone
View attachment kyocera_hydro_adb_usb_driver.zip
This driver is for Windows 32/64 systems, and does not have an install utility, you have to manually install from the device manager.
I did this so that I could start trying to find a root exploit on this phone, so far I have had no luck, but I have never tried to find an exploit before, so I am a noob at it.
Maybe if we get more people looking at it, we can find something.
In my opinion the security seems pretty tight, the kernel is patched to other ICS kernel exploits, the file permission are very strict, there is no way to access the boot loader/fastboot that I know of with button combos, or doing an “adb reboot bootloader” command, the stock recovery has less options than most stock recoveries.
I do not think I have the skills needed to find an exploit, I am hoping some mad genius will come along and be able to find one, of course they will be given full credit for doing such. I am going to post some information and files that may help us find an exploit, please see post number three.
For those who may know me, I am not really starting to do any dev work again just yet, I just want my new phone to be rooted, so that I can do dev work on it at some later time
If we are able to get root, this will probably be the thread I release any stuff I make for this phone, so I made a few "reserved posts" hope that is OK
.,
reserved
I am going to put information and some files in this post that may help someone find a vulnerability, of course there are a lot of things I cannot get because the phone is locked down
General Info
This phone has an MSM8655 processor and the ROM and Kernel seem to be made from CAF (Code Aurora) source code using the msm7630_surf platform , of course it would have been modified a lot by Kyocera
Android Version 4.0.4 - Build IML77 - Kernel Version 3.0.8-perf
Dump of /system, "adb pull / c:\dump"
It is not a complete ROM, it is only the files I was able read and pull from ADB, it cannot be used for anything, but maybe someone who looks at it may find a hole somewhere.
www.mediafire.com/?cuppd1dj29nvbl1
De-Compiled .apk and .jar These are all the .apk and .jar files in the app and framework folders de-compiled with apktool
https://github.com/hroark13/hydro_decompiled
De-Odexed "/system/app" Files All the /system/app files de-odexed
http://www.mediafire.com/?rs77g1tiwvk2hbv
De-Odexed "/system/framework" Files All /system/framework files de-odexed
http://www.mediafire.com/?g12wcmpdpojj1yz
Kernel configuration “adb pull /proc/config.gz”
View attachment hydro_config.txt
Mounts "adb shell mount > hydro_mounts.txt"
View attachment hydro_mounts.txt
Folder Permissions “adb shell ls –l –R / > hydro_permissions.txt”
The /data folder is locked down tight so there really is no info about it there, this was a big text file, so I had to zip it
View attachment hydro_permissions.zip
logcat "adb shell logcat > hydro_logcat.txt"
View attachment hydro_logcat.txt
dmesg "adb shell dmesg > hydro_dmesg.txt"
View attachment hydro_dmesg.txt
Props"adb shell getprop > hydro_props.txt"
View attachment hydro_props.txt
Well, if anyone finds anything, has any good ideas, or needs me to upload something else, please post a reply
.
Here are some dial codes I found that work
##22767# or ##BCSMS#
##25327# or ##CLEAR# ACCESS CODE
##3282# or ##DATA# MSL TO EDIT
##33284# or ##DEBUG# ACCESS CODE
##3424# or ##DIAG# MSL
##4772579# or ##GPSCLRX# MSL
##564#
##72786# or ##SCRTN# MSL
##786# or ##RTN# MSL TO RESET
##8378# or ##TEST# MSL
##9526# or ##WLAN#
ACCESS CODE = SPRINT (777468)
One thing that I found interesting "at least it was interesting to me, hey I am new at this"
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh
there also seems to be a copy of busybox at /system/etc/firmware/wlan/volans/KCJ/busybox
If I do an "adb shell /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh"
I get
Code:
/system/bin/sh: /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh: cannot exe
cute - Permission denied
If I do a "adb shell mksh /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh"
I get
Code:
mount: Operation not permitted
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/busybox: Read-only file sys
tem
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/fer_measure_step1.sh: Read-
only file system
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/fer_measure_step2.sh: Read-
only file system
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/iwpriv: Read-only file syst
em
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/kcj_wifi_on.sh: Read-only f
ile system
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh[45]: /system/etc/firmware/w
lan/volans/KCJ/busybox: cannot execute - Permission denied
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh[69]: /system/etc/firmware/w
lan/volans/KCJ/busybox: cannot execute - Permission denied
MACADDR NOT CHANGE
Unable to chmod /system/etc/firmware/wlan/volans/WCN1314_qcom_cfg.ini: Read-only
file system
rm failed for /data/fcc/fcc.zip, No such file or directory
rm failed for /data/fcc/, No such file or directory
rm failed for /system/etc/firmware/wlan/volans/FCC/fcc_daemon, No such file or d
irectory
mount: Operation not permitted
I do not know why I can execute that script with mksh
.
Another thing that may be a potential vulnerability is
/system/xbin/updateue
This seems to be the Kyocera System Updater
I really would not know how to exploit this, but I figured I would just point it out, and I am trying to get past my 10 post thingy
.
I have tried using the debugfs exploit from miloj, but /data/local is owned by root so I can not "mv /data/local/tmp /data/local/tmp.bak"
I have tried the mempodroid / mempodipper exploit from saurik but that vulnerability seems to be patched in this kernel
I have also tried some of the older GB exploits methods with no luck
.
your link
www.mediafire.com/?cuppd1dj29nvbl1
I hope someone does help with this. I can vouch for Hroark and his work (His kernel work on the ZTE Warp was most helpful). Good luck big guy! Your work is still appreciated!
Sent from my N860 using xda premium
atlharp said:
I hope someone does help with this. I can vouch for Hroark and his work (His kernel work on the ZTE Warp was most helpful). Good luck big guy! Your work is still appreciated!
Sent from my N860 using xda premium
Click to expand...
Click to collapse
yeah, I am trying to provide a lot of information, just so anyone who wants to help, does not have to waste time on doing some of the things I am able to do myself, this way they will be more encouraged to help out
do you have a Hydro
I just got mine a few days ago, I like it, it is a pretty good phone
.
OK so I only need two more posts to get to my 10 post thing, so here is a nice picture of my girl friend
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shabbypenguin said:
your link
www.mediafire.com/?cuppd1dj29nvbl1
Click to expand...
Click to collapse
thank you Shabster, I think I can post external links now since this is my 10th post
hroark13 said:
yeah, I am trying to provide a lot of information, just so anyone who wants to help, does not have to waste time on doing some of the things I am able to do myself, this way they will be more encouraged to help out
do you have a Hydro
I just got mine a few days ago, I like it, it is a pretty good phone
.
Click to expand...
Click to collapse
No, but I am trying to steer a friend to it. It looks promising though.
yes finally
ive had this phone since day one and cant even get a case or screen protector i had to cut one to fit it seems this phone didnt get much air on lauch but i love the wate thing cause i am a auto mechanic and iam always geting my phone wet ,i wish i could help with the root issue but i have no experience and no one to how me the ropes iam sure i could catch on with all help any one game to help a noob who wants needs a master to whom i can ask questions
fordefied said:
ive had this phone since day one and cant even get a case or screen protector i had to cut one to fit it seems this phone didnt get much air on lauch but i love the wate thing cause i am a auto mechanic and iam always geting my phone wet ,i wish i could help with the root issue but i have no experience and no one to how me the ropes iam sure i could catch on with all help any one game to help a noob who wants needs a master to whom i can ask questions
Click to expand...
Click to collapse
this phone is great for the price, I paid $115.00 plus tax at a Boost store,
even if we do not get root, the phone is worth having, so far I am happy with mine
I have not tried getting it wet yet
I even dropped it a couple of times, and it held up pretty good
atlharp said:
No, but I am trying to steer a friend to it. It looks promising though.
Click to expand...
Click to collapse
it is worth it, in my opinion
I have had no problems so far, but it has been less than a week, so who knows
hroark13 said:
this phone is great for the price, i paid $115.00 plus tax at a boost store,
even if we do not get root, the phone is worth having, so far i am happy with mine
i have not tried getting it wet yet
i even dropped it a couple of times, and it held up pretty good
Click to expand...
Click to collapse
yea iagree it is a durable phone
why is it freezein
Ive had this phone from its release, it was good at first ,but now it keeps freezing and its so slow i don't know what happened i had a evo flashed to boost before this phone and it has same snapdragon process er,why is this phone not as smooth ,has any one else experience d this
fordefied said:
Ive had this phone from its release, it was good at first ,but now it keeps freezing and its so slow i don't know what happened i had a evo flashed to boost before this phone and it has same snapdragon process er,why is this phone not as smooth ,has any one else experience d this
Click to expand...
Click to collapse
I was having slow data issues, so I switched to Metro PCS and got the new LG Motion, so far I am very happy with it.
I will probably sell my Hydro, because I can not return it, since I have more than one hour of talk time on it.
Hroark
Good to see you back at it Hroark.
Please help me about how to root in 2.20
Ummm . . . did you read the threads in Development on how to root?
Did you attempt it, and having a specific problem?
redpoint73 said:
Ummm . . . did you read the threads in Development on how to root?
Did you attempt it, and having a specific problem?
Click to expand...
Click to collapse
yep..
Please help me about how to root in 2.20
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
2100 KB/s (64526 bytes in 0.030s)
[-] Failed.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
please help me with this problem
thank you so mmmmmmuch
lizhongzhi000 said:
yep..
Please help me about how to root in 2.20
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
2100 KB/s (64526 bytes in 0.030s)
[-] Failed.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
please help me with this problem
thank you so mmmmmmuch
Click to expand...
Click to collapse
Sent from my HTC One XL using xda premium
abhipati said:
At which step your failing? Let us that, you just posted the instructions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
the CID didn't change after the process..
please help me with this problem
lizhongzhi000 said:
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
the CID didn't change after the process..
please help me with this problem
Click to expand...
Click to collapse
Which phone do you have? This tool is only for the One XL (evita). Are you using a PC, Mac, or Linux?
Sometimes these things don't take the first time. Have you tried it again, perhaps after rebooting your phone?
iElvis said:
Which phone do you have? This tool is only for the One XL (evita). Are you using a PC, Mac, or Linux?
Sometimes these things don't take the first time. Have you tried it again, perhaps after rebooting your phone?
Click to expand...
Click to collapse
i am using a PC. and the phone is HTC ONE X ATT edition.
I have tired seveal times but failed.
thank you.
iElvis said:
Which phone do you have? This tool is only for the One XL (evita).
Click to expand...
Click to collapse
CWS__001 is the CID for AT&T.
lizhongzhi000 said:
yep..
Please help me about how to root in 2.20
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
2100 KB/s (64526 bytes in 0.030s)
[-] Failed.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
please help me with this problem
thank you so mmmmmmuch
Click to expand...
Click to collapse
if I am not wrong.. you are getting error for below command.. correct??
adb shell "/data/local/tmp/pwn"
---------- Post added at 12:18 AM ---------- Previous post was at 12:17 AM ----------
Try rebooting your phone.. and in one of thread i read that doing factory reset and trying again resolved the issue.. you may try that
lizhongzhi000 said:
i am using a PC. and the phone is HTC ONE X ATT edition.
I have tired seveal times but failed.
thank you.
Click to expand...
Click to collapse
It looks like u downloaded old version of tool which had bug in it. Download new version and try again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kancherlapraneeth said:
if I am not wrong.. you are getting error for below command.. correct??
adb shell "/data/local/tmp/pwn"
---------- Post added at 12:18 AM ---------- Previous post was at 12:17 AM ----------
Try rebooting your phone.. and in one of thread i read that doing factory reset and trying again resolved the issue.. you may try that
Click to expand...
Click to collapse
this is the whole process that it showed.
[*]
[*] X-Factor: HTC One X Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Greets/thanks to Michael Coppola
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest HTC drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: this will overwrite your CID, and potentially void
[*] your warranty. I am not responsible for the repurcussions
[*] of this or any other damage this exploit may cause.
[*]
[*] Press enter to exploit your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
2100 KB/s (64526 bytes in 0.030s)
[-] Failed.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Press any key to continue . . .
so, is something wrong with it..?
thank you
as abhipati said,, download the root exploit again and try again.. let us know the result
kancherlapraneeth said:
as abhipati said,, download the root exploit again and try again.. let us know the result
Click to expand...
Click to collapse
it is still like that..didn't work,..
lizhongzhi000 said:
it is still like that..didn't work,..
Click to expand...
Click to collapse
do factory reset and try again. someone reported it worked..
kancherlapraneeth said:
do factory reset and try again. someone reported it worked..
Click to expand...
Click to collapse
but i don't want lose all the data i have install in the phone....how can i handle that if possible without wipe the phone..
thank you so muchhhhhhhhhhhh
lizhongzhi000 said:
but i don't want lose all the data i have install in the phone....how can i handle that if possible without wipe the phone..
thank you so muchhhhhhhhhhhh
Click to expand...
Click to collapse
try each step listed in bat file one by one and find at what step exactly you are getting error. I think it is at adb shell "/data/local/tmp/pwn"
also do adb shell "ls -lrt /data/local/tmp/pwn" to see if that file exists and check permissions of 775
kancherlapraneeth said:
try each step listed in bat file one by one and find at what step exactly you are getting error. I think it is at adb shell "/data/local/tmp/pwn"
also do adb shell "ls -lrt /data/local/tmp/pwn" to see if that file exists and check permissions of 775
Click to expand...
Click to collapse
/data/local/tmp
adb shell "chmod 755 /data/local/tmp/pwn"
adb shell "/data/local/tmp/pwn"
echo
i think there is the problem,,so how can i do with that thank you
paste the output of below three steps
adb push pwn /data/local/tmp
adb shell "chmod 755 /data/local/tmp/pwn"
adb shell "/data/local/tmp/pwn"
also this adb shell "ls -lrt /data/local/tmp/pwn"
kancherlapraneeth said:
paste the output of below three steps
adb push pwn /data/local/tmp
adb shell "chmod 755 /data/local/tmp/pwn"
adb shell "/data/local/tmp/pwn"
also this adb shell "ls -lrt /data/local/tmp/pwn"
Click to expand...
Click to collapse
C:\Users\zli\Desktop\X_Factor_Windows>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\zli\Desktop\X_Factor_Windows>adb push pwn /data/local/tmp
1432 KB/s (64526 bytes in 0.044s)
C:\Users\zli\Desktop\X_Factor_Windows>adb shell "chmod 755 /data/local/tmp/pwn"
C:\Users\zli\Desktop\X_Factor_Windows>adb shell "/data/local/tmp/pwn"
[-] Failed.
C:\Users\zli\Desktop\X_Factor_Windows>adb shell "ls -lrt /data/local/tmp/pwn"
ls: Unknown option '-r'. Aborting.
C:\Users\zli\Desktop\X_Factor_Windows>pause
Press any key to continue . . .
this is the reply
thank you
do adb shell "ls -lt /data/local/tmp/pwn" -- removed r - Looks it failed while running /data/local/tmp/pwn
Hello, well today i was going through the second hand market on my town for a phone and i saw this mb865, impecable but as is.. with no charger cables or anything whatsoever.. the price was cheap enough so i got it..
After getting to my home i noticed that on the back under the cover and on the display at the right side of the screen it has some engravings saying this phrase.
"Confidential Motorola property not for sale"
so whats the deal with this phone? is it a prototype? or what?
Im from Mexico and the phone has a Iusacell rom.
What do you guys think?
If i were you, i would go to that store again, and return it. Perhaps you'll have some bad experiences with that phone, because maybe it's not the final release and may had some changes than ours phone.
And on the other hand, it may be an engineering device with an unlocked bootloader....
snowplow said:
And on the other hand, it may be an engineering device with an unlocked bootloader....
Click to expand...
Click to collapse
im now officially praying for this.. as of right now.. i have asked for an unlock code from cellunlocker.net..
any of yoou know them? they seem reliable enough...
No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?
snowplow said:
No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?
Click to expand...
Click to collapse
Well i have tried my sim ( which is from another carrier) and it asks me for asubsidiary code.. so im hoping ill be able to unlock it the same way i did with my xt610 some time ago..
So far i dont see anything special in this phone, other than those words... mm well see.. tomorrow ill try to flash some roms, recoveries.. etc..
and ill be expecting my unlock code..
Sent from my iPad using Tapatalk
enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.
Ravikirancg said:
enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.
Click to expand...
Click to collapse
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Eetu, you need to follow above instructions and advise what output you get on screen. Your phone may be one of a kind most special and our developers need all help to unlock bootloader & they may get in touch with you based on your reply that is sought & until then preferably do not alter stock settings by flashing custom ROM's, Mod's etc. We need all help we can get. Thanks!
RAD7 said:
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Click to expand...
Click to collapse
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos
serch_mx said:
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos
Click to expand...
Click to collapse
Noted & I guess eetu must have given reply in PM to developers!
RAD7 said:
Noted & I guess eetu must have given reply in PM to developers!
Click to expand...
Click to collapse
doubtful about that.. dosent look like he returned to this.
Ravikirancg said:
doubtful about that.. dosent look like he returned to this.
Click to expand...
Click to collapse
Gee, sucks, Eeetu, Man do revert.
When Jim said he is looking at stuff from user Amritin's phone, I was thinking prolly something more like Eetu's phone can surely add to the database.
IM HERE
Sorry guys i have had some in house problems.. but im here now..
Well blast i have probably ****ed this up now.. you see i was trying to root the phone in order to see things under the hood, but the usual superonelick, methond didnt work ( i tried other 2 thati cant remember they were mostly sripts with a runme.bat file on them)...
So with no avail.. i decided to flash the rom to a LATAM stock GB rom.. after i did.. i tried superoneclick and voila...
I havent been able to tinker with it past then.. but now im afraid of what i did.. ****..
So tell me do i try to reflash the iusacell rom( it is avaliable).. do i leave it like this.. or what?
on the meantime i have uploaded some pics of the phones messages of confidential property.. for you to see.. and im checking the ADB stuff.. getting the terminal emulator from the playstore as im typing this..
Let me know how to proceed..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the quality.. i couldnt take better ones at the moment.. and the words on the front (on the side of the screen) are just impossible to take.. but believe me they are there..
well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..
eetu1923 said:
well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..
Click to expand...
Click to collapse
Try:
adb shell
Then, su...
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
Edit: Ahh.. You're using an app, not by usb.. Forget the first part of what I said - or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Sent from my MB865 using xda app-developers app
alteredlikeness said:
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Click to expand...
Click to collapse
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??
eetu1923 said:
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??
Click to expand...
Click to collapse
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Sent from my MB865 running PAC-man using Tapatalk 2
Ravikirancg said:
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Click to expand...
Click to collapse
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.
eetu1923 said:
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.
Click to expand...
Click to collapse
If you have no su binary file in xbin or bin, then it's going to be difficult for things to recognize root.
You opened Superuser and tapped to check for binary updates in settings?
You could also try to install SuperSU instead..
Another thing to try: get busybox installer from Play Store and update busybox.
And about adb debugging - go to settings>developer options (or maybe security on GB?) - and enable USB debugging.
Plug in your phone to your computer by USB. Switch to each USB connection type on your phone (mass storage, mtp, camera..) and wait to let the drivers install if they haven't already.
Open a command prompt on that folder that contains adb.exe - do this by holding shift and right-click on the folder and choose open command prompt from the list (or just open the command prompt and type cd C:\Users\Desktop\1-click_exploit or whatever your path is to adb).
Type adb devices
If you get a serial number and the word "device" as output, then you should be OK to use adb
Sent from my MB865 using xda app-developers app