Tried running the program provided in this thread:
http://forum.xda-developers.com/showthread.php?t=1644167
I followed all the steps (there hard to mess up, haha) but when running the .bat it says root then this happens...
{
"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"
}
I'm so confused what am I doing wrong? I've tried in charge mode only and mounting the sd card nothing changes..
I've reinstalled the drivers, download the .zip again, reset my phone to factory. What else can I do?
EDIT: USB Debugging is enabled, I enabled it before plugging it in.
UPDATE: It's still not giving root access, I updated my sdk tools after this error still nothing
Enable USB debugging.
Sent from my HTC One X using Tapatalk 2
Make sure you have debugging enabled on your phone.
Sorry I forgot to add the fact usb debugging is enabled.
EDIT: nevermind... re-read your post again.
For some reason sometimes you need to enable debugging before you plug it in.
How long does the rooting process take from where it says "PUSH FILES"? It just seems to sit there for a few mins on my end.
For me it took like 5 min I wan say maybe les, just make sure u guys read everything and don't skip any steps.
So does this work for the at&t? Has anyone tried it?
Sent from my HTC One X using XDA
Your drivers aren't talking to adb. I had an issue yesterday, couldn't install the drivers to save my life. Installed SDK tools, still no go. Everytime I tried to root I got the same error as you.
Try this: Do all of the steps again.
This time, Kill the ADB process tree.
Now, hit the root file again. That may work. Some users are saying that adb won't work for them until they do this.
I've had similar problems on my atrix before. If I remember correctly, it seemed to help when I extracted root files to my desktop.
Sent from my HTC One X using Tapatalk 2
htcvarona said:
So does this work for the at&t? Has anyone tried it?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Yes, the title of the One Click root says AT&T in it.
XNine said:
Your drivers aren't talking to adb. I had an issue yesterday, couldn't install the drivers to save my life. Installed SDK tools, still no go. Everytime I tried to root I got the same error as you.
Try this: Do all of the steps again.
This time, Kill the ADB process tree.
Now, hit the root file again. That may work. Some users are saying that adb won't work for them until they do this.
Click to expand...
Click to collapse
No cigar, was there 2 adb.exe processes running for you? At first one took me to htc sync so I uninstall sync. When I tried again killing one the other would just keep the CP open.
BBock9 said:
I've had similar problems on my atrix before. If I remember correctly, it seemed to help when I extracted root files to my desktop.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That didn't seem to help either
Thank you to everyone that's trying to help, its still not working but I appreciate the community's help!
make sure HTC Sync service is not running
Pirateghost said:
make sure HTC Sync service is not running
Click to expand...
Click to collapse
I actually uninstalled it, Sync just didn't seem necessarily if its not supported by the HOX. Then again I could be having a driver issue and it just wasn't seeing the device in Sync. Would anyone recommend the first root method? I'm just running out of ideas...
droidnamedjakke said:
I actually uninstalled it, Sync just didn't seem necessarily if its not supported by the HOX. Then again I could be having a driver issue and it just wasn't seeing the device in Sync. Would anyone recommend the first root method? I'm just running out of ideas...
Click to expand...
Click to collapse
At this point, try it on a different computer if you have one available. That will quickly eliminate any problems that could be causing this on the computers end.
Sent from my HTC One X using Tapatalk 2
Have you tried copying all the files required for root to the c: drive on your computer and then running it from there via command prompt? also, i didnt see it mentioned, but what about running as admin?
BBock9 said:
At this point, try it on a different computer if you have one available. That will quickly eliminate any problems that could be causing this on the computers end.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Bazinga! I have no clue why my gaming rig wouldn't accept the drivers but my little brothers scrappy hp ran everything without a hitch! Many thanks!
droidnamedjakke said:
Bazinga! I have no clue why my gaming rig wouldn't accept the drivers but my little brothers scrappy hp ran everything without a hitch! Many thanks!
Click to expand...
Click to collapse
LOL. My 3K watercooled rig wouldn't install the HTC drivers, my GF's 600 dollar rig did it without a hitch. Glad to see you got it sorted!
I hate Windows.
Related
What to change the Sprint banner to something else?
Well here is how.
This is a rough guide, maybe I'll get ambitious and spruce it up when I have some more time...
Install HTC Sync if you haven't already..
Get it here.
http://www.htc.com/www/SupportViewNews.aspx?dl_id=933&news_id=631
Gonna need the HTC Diag drivers, least I did... these work fine:
http://rapidshare.com/files/293529424/HTC_Hero_DIAG_Drivers.zip x86 32bit
Here are the /64 bit drivers thanks to techwerkz
http://www.techwerkz.com/evo/HTCDiagDrivers.zip
[highlight]Mod edit: No linking to warez site or suggesting users to get warez is allowed[/highlight]
Enter DIAG mode, dial ##diag#, let windows install the drivers...most likely it won't find the HTC DIAG drivers, but they are in the link above... get it installed.
Now in CDMA workshop, you really don't want to be effin' with stuff you aren't sure what it is... but we are here to change the banner right? riight so don't be changing anything else and you'll be a-ok.
Select your port, hit connect, hit read... goto the NAM tab...hit Read ...change the Banner from "Sprint" to whatever..hit "Write".... then you can reboot the phone and its done.
To find your port...
{
"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"
}
Select your port, hit connect then hit read. ( picture shows "Disconnect" only because I already pushed connect... )
Goto the NAM tab, hit read, change the banner, hit write. Reboot your phone
Enjoy!
Mods if there is a problem with me posting the link to isohunt, I'll gladly remove it.
Thank you so much love these tips
I keep on getting phone does not answer. Is there something else I need to do?
violent23 said:
I keep on getting phone does not answer. Is there something else I need to do?
Click to expand...
Click to collapse
Did all the drivers install? Are you using the correct port? are you in diag mode?
violent23 said:
I keep on getting phone does not answer. Is there something else I need to do?
Click to expand...
Click to collapse
The com port you are using is not the one the phone is using. Go into Device manager and see what port it is running on. The demo version will not allow above port 6 so you may have to change the port.
slayer69 said:
The com port you are using is not the one the phone is using. Go into Device manager and see what port it is running on. The demo version will not allow above port 6 so you may have to change the port.
Click to expand...
Click to collapse
I am an idiot, thanks that solved it.
cool thanks for the guide!
If anyone has the HTC diag drivers for x64 can ya post em... please try them prior to posting.
Finally got it! Thank's OP....
apristel said:
What to change the Sprint banner to something else?
Click to expand...
Click to collapse
Thx for the info.. great job, added to my thread in first post for easy find
Looks good. My 64bit w7 gave me a hard time, it wouldn't install the drivers correctly so I wasn't able to do it last night. I was however, successful when I used my work's xp this morning so it works now.
Thanks!
w7 x64 here also, and it keeps installing the Diag driver as a network driver....
re2gie01 said:
w7 x64 here also, and it keeps installing the Diag driver as a network driver....
Click to expand...
Click to collapse
I have the same issue as well on my Windows 7 x64. Looks like a bug in the installer from HTC. We should let them know its Jacked!. lol
Got it!! For all those with win7 64bit, I have attached the appropriate driver to get the HTC Diag working. Verified this on my machine and installed no problems.
re2gie01 said:
Got it!! For all those with win7 64bit, I have attached the appropriate driver to get the HTC Diag working. Verified this on my machine and installed no problems.
Click to expand...
Click to collapse
Thanks and I will update my OP.
Good work!
just glad to be able to help out
re2gie01 said:
Got it!! For all those with win7 64bit, I have attached the appropriate driver to get the HTC Diag working. Verified this on my machine and installed no problems.
Click to expand...
Click to collapse
Didn't work for me. Windows 7 64 bit.
Edit: It does work on Windows 7 x64. The 64 bit drivers will not be recognized or installed by the Windows 7 automatically. You must force the installation of the drivers by choosing the "Browse" option then "Let Me Pick" option then the "Have Disk" option.
Thanks, that's awesome. I got it working no problem, just followed your instructions
I was sad though, it only lets you put up 12 characters I was going to put up Mistersquirrle but I had to truncate it to Mistrsquirrl. Still great though, thanks
good stuff guys
I did NOT have to install HTC Sync... maybe because I already have the driver installed for adb to work.
But yeah, just had to install the DIAG driver and it worked (Win7 x32)
Having trouble rooting your phone? This might be just for you!
Credits
z4ziggy
Sebastian Krahmer's rageagainstthecage
What this does
It is an app you install (currently you must side load it, but it will be on the market once it's had some testing here on XDA), that has a single button that will root your device. Should work on ALL Android devices -- please leave a note if it works or doesn't work on your device.
How safe is this?
Should be 100% safe - nothing on disk is changed besides the root binaries, so if something goes wrong, simply rebooting the device should fix up any and all issues. Let me know if you find any bugs!
{
"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"
}
Changelog
V1.0.0 : Initial Release
V1.1.0 : Will now open the application settings page if USB debugging is not enabled.
New version 1.1.0 uploaded with detection for USB debugging not being enabled.
This looks really cool! But, is it just a shell root? Not a nand unlock?
RyanZA said:
New version 1.1.0 uploaded with detection for USB debugging not being enabled.
Click to expand...
Click to collapse
It does not seem to work on my Archos 101 Internet tablet, it just reboots the device.
Edit: Busybox says it isn't rooted.
Will this do a Full root on X10 Mini Pro? just as this tool is suppose to do? Unfortunately that tool keeps looping even if I tap usb debugging for hours...
So Root and Shell Root and Superuser and allow non-market apps (thought that was just a normal setting in Android..)?
awesome app, I just did this on Sony x10, although I can't confirm that it installed busybox. I loaded it from the market and it didn't detect it.
Install on busybox 1.17.1 worked good
Thanks.
It started the process and rebooted, but hadn't installed Busybox, so downloaded it from the Market and it confirms the phone is actually rooted. Good start but far from perfect.
Does this work on the HTC Evo?
Any1 tried on the dinc???
Just use in unrevoked HTC devices are harder to root
CoryKalis said:
Any1 tried on the dinc???
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
Worked great on my EVO.
Working on GSM HTC Hero 2.1 with original spanish Orange rom, AFAIK. The screen says "wait for root to complete and reboot your phone", stays there forever and after 1 hour I decided to go back. Rebooted manually and there it was, just downloaded Busybox from Market and working fine.
Its been the only working method for me, so saying thanks is actually less than needed.
partyman1971 said:
Worked great on my EVO.
Click to expand...
Click to collapse
Worked great on my Droid 2
Thanks so much for this.
Indigon said:
Worked great on my Droid 2
Click to expand...
Click to collapse
i have a droid 2 also and really wanting to root was this root way painless and is everything working ok?
reyrey2435 said:
i have a droid 2 also and really wanting to root was this root way painless and is everything working ok?
Click to expand...
Click to collapse
Everything works perfect on my Droid 2, fast and easy one click root like it says.
Been waiting for something like this, so glad I did it.
Opens a whole new world of great rooted apps and
getting rid of that unnecessary bloatware.
Remember to first enable (turn on) usb debugging: Menu> Settings> Applications> Development> USB Debugging
Kudos! Thanks again to the Dev!
I tried Superoeclick yesterday only my X10 Mini (2.1 firmware), which tells me the phone is rooted, but still won't allow me to delete apps
just tried this and it ran, rebooted the phone as it should but when I try to remove some apps it still won't let me
forgot too add, it didn't install Busybox either
It worked flawlessly on galaxy s jm1,
great app !
Sent from my GT-I9000 using Tapatalk
Works on DX! (Mine froze and required a reboot after the first try, but worked like a charm the 2nd go round)
petter11 said:
It does not seem to work on my Archos 101 Internet tablet, it just reboots the device.
Click to expand...
Click to collapse
Install busybox and see if it rooted it; where did you get a 101, I thought they weren't released yet...
worked on an og droid running frg22d
thanks
Hey everyone, basically just what the title says. I plug it into the computer via USB, and ADB will not see the device when it's booted into Android. However when I boot it into recovery, it sees it fine.
I'm running Cyanogen 9 for a rom and TWRP for recovery.
Booted into android:
C:\Users\Michael>adb devices
List of devices attached
Booted into recovery:
C:\Users\Michael>adb devices
List of devices attached
b3fe68e1 recovery
I've tried installing drivers, deleting drivers, reinstalling drivers, rebooting, countless times now. Samsung's own software Kies won't even recognize the phone.
I am able to use ADB over wifi with ADB Wireless.
C:\Users\Michael>adb devices
List of devices attached
10.0.0.99:5555 device
Oh, and I can turn on USB Storage and access the filesystem with no problems.. so that works fine.
Am I going crazy or has someone else had this same problem? Thanks everyone.
Sorry for the silly question but have you enabled it in settings? That may or may not help you:thumbup:
{
"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"
}
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I should have posted that in my original thread.. but yes I have it enabled. I tried having ADB over network enabled just to see if it would help.. but it did't.
Is "USB Debugging" in the phone (inside Android) checked ? check this option and see..
PS:sorry if it is enabled ... ROM problem ? did adb work on stock ROM ?
Yep it is enabled. It did not work with the stock rom either and the only reason I know that is because my wife just got the same phone yesterday and I noticed it wasn't working while trying to root it.
Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)
mahanddeem said:
Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)
Click to expand...
Click to collapse
+1
try on another comp and c what happens, 2 phones cant be both screwed up so it must b comp
Yeah I agree it must be something to do with Windows. I will try installing the drivers and such on a computer at work on Monday and see what gives.
In the mean time I uninstalled everything and rebooted. Then I downloaded the drivers from Samsung's website, from here:
http://downloadcenter.samsung.com/c...27_GS_II_Skyrocket_USB_Driver_v1_3_2200_0.exe
I also read this post:
http://forum.xda-developers.com/showthread.php?t=1415051
and the #2 article points to: ATT_i777_GS2_USB_Drivers.zip
So I tried installing that too. Still nothing.
I took a couple screenshots during the process, maybe it will raise a red flag to one of you guys because I certainly can't figure this out.
When I plug in my phone, the "Android" device is what comes and goes. I've tried updating the drivers for that and pointing them to the Samsung drivers directory, just says it can't find them.
I admit to still being new around the whole android development thing, but with Windows I'm pretty proficient, I just can't figure out what I'm missing.
Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery
yoft1 said:
Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery
Click to expand...
Click to collapse
If super user is installed yes you can pull or push even in Android...But if not rooted it's only done while in recovery...
y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself
vincom said:
y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself
Click to expand...
Click to collapse
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..
mahanddeem said:
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..
Click to expand...
Click to collapse
k, but r u not installing any custom roms, as far as i know they are all prerooted, or u just need root todo ur own stuff
Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.
mmerlina said:
Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.
Click to expand...
Click to collapse
i agree its win7 and drivers
Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.
mmerlina said:
Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.
Click to expand...
Click to collapse
Not exactly a solution though, in that Sky ICS is still a TW-based ROM (as in, based off the stock ROM) and not an AOSP-based ROM like CM9 or AOKP.
I also had this issue. The problem was in fact a Windows driver issue though, even though I had installed them already. When I went to Device Manager it would always show up as generic "Android" device with no driver under "other devices". I right-clicked it, Selected "Update device drivers" and then I believe there was an option to select drive from existing installed drivers. I'm on my linux partition right now so I forget what the precise option dialogue was, but it was a separate option from the "Browse my computer" option. From there it opened up a long list and I scrolled down and found one of the Samsung entries listed. I believe it was Samsung Electronics Co. Ltd. (there were others like SAMSUNG in all caps, etc.). I then selected the driver from the list within that Samsung group and ADB worked again.
I've tried just about everything to get my fastboot working. I'm running on Windows 8. I've tried tool and scripts, different drivers, HTC Sync, EVERYTHING.
I've gotten ADB to work but fastboot won't recognize my phone.When I put my phone into fastboot mode, I can go into my computer and look up the phone in device manager and I do see the phone. Unfortunately, it presents an error that say the device has failed to start. This has been unchanged through out every "fix" I've tried. Any ideas?
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
timmaaa said:
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
Click to expand...
Click to collapse
Oops, sorry. I've tried the tools that are supposed to set up fastboot for you, I downloaded the SDK and got the fastboot and adb files but nothing shows up in the "fastboot devices". I've also tried the HTC Sync route as well as numerous drivers that are claimed to be the "fix".
What about some of the guides that are available that specifically address this problem?
{
"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"
}
Sent from my Evita
timmaaa said:
What about some of the guides that are available that specifically address this problem?
Sent from my Evita
Click to expand...
Click to collapse
I've tried all the results on that first page. Nearly every time, I get an error message with a yellow triangle for an icon:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
timmaaa said:
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
Click to expand...
Click to collapse
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
KungPow90 said:
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
Click to expand...
Click to collapse
Download latest HTC driver , go into your device manager in win 8 and in device mgr menu options on top make sure and click show hidden (not connected ) devices. You then will have to click onto the greyed out HTC or android name in device mgr tree and update manually . you have to actually go to the sub folder in the driver update and not just click the folder that its in. Lol its a pain but it does work. You can Google manually install HTC driver for win 8 and there is couple tutorials. Hope it helps. I beta tested win 8
And had to do that. Lol im back to win 7 and Ubuntu now
Senseless Power Unlocked
So, I'm having Droid MAXX ver. 12.15.15 and can't get root through Cydia Impactor.
USB Debugging is enabled, there is no screen lock, but every time time I try to start telnet daemon through Impactor
# start telnetd as system on port 2222
There is an error in attachment
{
"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"
}
Regular usb debugging through eclipse works fine.
Has anyone solved this problem?
Image is broken.
Sent from Verizon Droid Maxx
Repost screenshot and we may decide to help a droider in need
FreeRimJobz said:
Repost screenshot and we may decide to help a droider in need
Click to expand...
Click to collapse
Here is an attachment.
So, an update. Last night I spend about 4 hours investigating what was wrong. Even flashed using RSD stock 12.15.15 then, Cydia Impactor worked for me 3 times of ~7 and I managed to get root through RockMyMoto. Then I removed write protection using WpNoMoto. Then reflashed stock 12.15.15 to use SlapMyMoto and Cydia Impactor fails all day long. Can't make it work again to use SlapMyMoto.
naixx said:
Here is an attachment.
So, an update. Last night I spend about 4 hours investigating what was wrong. Even flashed using RSD stock 12.15.15 then, Cydia Impactor worked for me 3 times of ~7 and I managed to get root through RockMyMoto. Then I removed write protection using WpNoMoto. Then reflashed stock 12.15.15 to use SlapMyMoto and Cydia Impactor fails all day long. Can't make it work again to use SlapMyMoto.
Click to expand...
Click to collapse
Do you have a firewall/antivirus active? Shut those down. Also, look for the "if you're a windows user and having trouble click "HERE"" in Jcase's thread.
livinitwarrior said:
Do you have a firewall/antivirus active? Shut those down. Also, look for the "if you're a windows user and having trouble click "HERE"" in Jcase's thread.
Click to expand...
Click to collapse
No antivirus/firewall off. Where to click?
So, the times, it worked nothing on PC changed. It seems to me that it is device problem.
Dunno, how it worked for several times And I removed root by flashing stock rom for SlapMyMoto
naixx said:
No antivirus/firewall off. Where to click?
So, the times, it worked nothing on PC changed. It seems to me that it is device problem.
Dunno, how it worked for several times And I removed root by flashing stock rom for SlapMyMoto
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=47067076
You use this thread?
livinitwarrior said:
http://forum.xda-developers.com/showthread.php?p=47067076
You use this thread?
Click to expand...
Click to collapse
Sure. I applied RockMyMoto, when Cydia worked. It worked for 3-4 times out of ~40. I tried different wasy: reboots, reflash, etc.
Now I want to apply Slap, and it doesn't work.
naixx said:
Sure. I applied RockMyMoto, when Cydia worked. It worked for 3-4 times out of ~40. I tried different wasy: reboots, reflash, etc.
Now I want to apply Slap, and it doesn't work.
Click to expand...
Click to collapse
But are you using PuttyTel to open the port? That's a better q, sorry
livinitwarrior said:
But are you using PuttyTel to open the port? That's a better q, sorry
Click to expand...
Click to collapse
I can't use telnet, as telnet daemon didn't start by Cydia. I tried simple telnet server from the market, surely it doesn't work.
naixx said:
I can't use telnet, as telnet daemon didn't start by Cydia. I tried simple telnet server from the market, surely it doesn't work.
Click to expand...
Click to collapse
hmmm... Would I be correct in thinking that you deleted the cydia and redownloaded, rebooted your computer, closed all extra programs, made sure you're on the same wifi, made sure adb connects and you still have the same IP, etc? Little tiny bugs that could influence it.
livinitwarrior said:
hmmm... Would I be correct in thinking that you deleted the cydia and redownloaded, rebooted your computer, closed all extra programs, made sure you're on the same wifi, made sure adb connects and you still have the same IP, etc? Little tiny bugs that could influence it.
Click to expand...
Click to collapse
Even different computers
I noticed, that it works, when all Cydia steps go slow, e.g. testing, installing, starting activity takes about 10 seconds, then it works.
naixx said:
Even different computers
I noticed, that it works, when all Cydia steps go slow, e.g. testing, installing, starting activity takes about 10 seconds, then it works.
Click to expand...
Click to collapse
different computer? Hmmm... it might be best to go back to the original computer and start from the beginning- starting with getting the IP address, redownloading Cydia and everything, and making sure Android Devo was back on once you wiped it from RSD
naixx said:
Even different computers
I noticed, that it works, when all Cydia steps go slow, e.g. testing, installing, starting activity takes about 10 seconds, then it works.
Click to expand...
Click to collapse
Do you have device manager installed? What usb cable you using?
Some thing is wrong with your setup. May even be your router settings restricting traffic
Maxx'd out Kit Kat