Related
Boo Hoo ... I love my HTC-HD2, (despite all the grief HTC should have avoided inflicting on us), ... and so I was really looking forward to the 1.66 ROM Upgrade. BUT it won't load for me...
I downloaded the ROM ("GCC & Egypt" version out of Middle-East & Africa site - I'm an expat living in Dubai), connected my phone to my PC by USB & ActiveSync, ran the ROM.exe on my PC, carefully ticked and clicked my way through all the dialogue boxes and when I hit the last "next" button to launch the ROM upgrade, ActiveSync decides to disconnect leaving the phone hanging in the tri-clour bootloader mode and 10 seconds later, (with the connection dropped), I get Error [266] UPDATE ERROR (see attached screen shot).
Happily a quick restart after removing the battery restored the phone to its un-upgraded state. Thinking I may have tweaked something I shouldn't have on my phone (with loaded software, reg-edits and xda-tweaks), I hard reset it back to the original factory 1.43 ROM condition and retried the 1.66 Upgrade; but no go - same ActiveSync disconnection/bootloader hang. Tried again with firewall and virus protection turned off; and again on a different PC; and again and again holding my tongue in every conceivable different position - but no joy and now I have a bald patch from all the hair I pulled out.
I might just be thick and missed something, (though - as a last resort - I did read the instructions seven times), ... so I'm desperately seeking assistance. Any help would be greatly appreciated ... as I'm finding it difficult to suppress the rising anger and loathing I developing for Team HTC - who have now predisposed me to blame them for everything that goes wrong including global warming; - this is turning out to be pretty much like my relationship with all the old Landrovers I've owned - but I digress - can anyone suggest a solution or point out my error ... before I send the less than complimentary email I'm drafting to HTC, who will then have to blacklist me from buying the HD3 and then I won't have anything to complain about, (because my current Landrover Discovery 3 is uncharacteristically perfect !!).
That's because Windows needs an extra driver for the phone in bootloader mode. It is then no longer connected via Activesync.
Put your phone into bootloader mode, connect it to your PC, wait for the driver to install, then flash again (while the phone is in bootloader mode).
ROM Upgrade Utility / Phone connection problem persists
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)
eViking said:
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)
Click to expand...
Click to collapse
What version of Windows are you using? If you are using Windows Vista or Windows 7 64 bit you may need to install the required drivers by yourself, rather than automatically updating drivers.
Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???
eViking said:
Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???
Click to expand...
Click to collapse
Strange. I guess you have tried using different USB ports, and not using a USB hub port. Are you using the stock USB cable that came with your HD2?
You might also try flashing a ROM with your storage card. That should bypass your USB problem. You can find instructions here.
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the LEO Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to LEOIMG.nbh
4. Copy the LEOIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Reset the device while pressing the volume down button to enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???
eViking said:
Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???
Click to expand...
Click to collapse
I do not understand all the mechanics of it, but no, not all micro-USB cables are the same, apparently some do not carry enough current, or some such thing. I am searching for more information for you now. If I find it, I will post it here.
For the life of me, I cannot find the information I was looking for. I read somewhere that others solved the problem by just disconnecting and reconnecting the phone during the flash process when the error occurs.
Well try another HTC cable as that sure seems to be suspect now. If all else fails, I would try flashing through the memory card method.
Keep us update. Hopefully soon you will get what you want.
Success!!! Flashing from a 3rd (more powerful) PC, went without a hitch and I'm now up and running.
My observations for what they're worth:
1. As noted by "FreyBerry", when running the Upgrade Utility from a PC using an ActiveSync connection to the phone, the connection gets dropped when the phone goes into bootloader mode and the PC is supposed to detect the phone as a USB device and reconnect - loading the appropriate driver. If driver and/or connection fails to load quickly enough the Utility times-out and you get the error message.
2. Though my USB cable may have been my problem, it seemed to work flawlessly on the 3rd PC. So other possibilites could be:
3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
4. On the 2nd attempt, using my office PC, our network/virus protocols/firewall or simply the aging PC may have been too slow or obstructed in reconnecting.
If the problem re-occurs I'll be opting for the SD-Card Flash method you suggested.
Many thanks for all the help ... I can already feel my pulled-out hair re-growing. Cheers.
Windows 7 seems to be the problem. I have the same problem if I want to upgrade the ROM on Windows 7, not on Windows XP.
3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
Click to expand...
Click to collapse
I never succeeded in flashing from a virtual machine on OS X.
@wereldbol No, it should work fine with Windows 7, both 32bit and 64bit.
Just last week I flashed a rom on a Vista x86 no problem. Now I've got Windows 7 x64 on a brand new computer and I'm now getting error 266. I don't have the option of using the old computer so I'm lost on what to do. I was already even able to flash HSPL3 to my wife's phone on the Win7 pc and didn't have this kind of trouble. But now I can't install a rom.
The device drivers installed. If anyone has any help. It would be much appreciated.
I already have my samsung usb and android modem drivers installed. but everytime i plug my phone in with usb debugging on, the "Found New Hardware" window keeps popping up, why?
im not sure, but it could be the problem to why it always says "waiting for device" on superoneclick
My day job is pc tech, I have seen this a few times but going to follow the steps, first give me some info
Which version of windows?
32 or 64 bit?
How proficient are you at driver maint. *add and removeal ov drivers*
When did this start?
windows xp - 32 bit - and im pretty proficient at maintenance. i think its always been like this.
Ok, Do you always use the same USB port? and have you tried a different cable? and have you tried it on other computers? if so did it do the same thing there?
First we got to get rid of the drivers on the pc.
http://download.cnet.com/DriverMax/3000-18513_4-10572602.html
This is a free program that has a few nice features but most important is that it can tell you the name of the files that are used as drivers. After you install and register (its free, they just want to know who you are.. name, email, that kind of stuff) there will be an entry on the right side called "Installed Drivers Report". Make sure you phone is connected before you click this as it scans active drivers. it will generate a report you can scroll through and find any samsung driver entrys. Write down those file names, we will need them in a moment.
Go to device manager and remove the device there. Windows XP was kinda lame about device removal it did not actually remove the device just broke the connection. Vista and 7 give you the option to actually delete the files which make this easier. Since your on XP after the devices have all been removed UNPLUG your phone from the PC then start a search for those files in the Windows directory. Delete (or move) those files and the rerun the driver install program from here
http://forum.xda-developers.com/showthread.php?t=728929
After that it may setup and find new hardware a few times. Mine did it 3 since there are multiple different methods it can connect with and each uses differnet hardware. Also each time you use a differnt USB port it sees it as new device in a new location so it also goes through new hardware setup again.
Report back and let me know if this helped any.
okay thanks for the quick response. i will try it when I have time and ill get back to you. first, imma try it on a different computer.
also, when its plugged in and i open device manager, theres 3 yellow exclamation marks, one on the android modem, device, and in the "OTHER devices" section, the USB controllers. if that means anything.
just turn off usb debugging... and it will stop. turn it back on if you need to use it for something.
The situation is this: Friend got a Droid Razr M, and I went and rooted it. I have learned that it's impossible pretty much to unlock the bootloader since his was built May 24th and has the most current OTA update.
What he would like to have is the phone on the Straight Talk Network. He would also like a custom recovery and ROM. I'm a little lost on this phone and have spent 3 hours reading at least on the forum between last night and this afternoon. Is it possible someone could give me some pointers?
DanRyan85 said:
The situation is this: Friend got a Droid Razr M, and I went and rooted it. I have learned that it's impossible pretty much to unlock the bootloader since his was built May 24th and has the most current OTA update.
What he would like to have is the phone on the Straight Talk Network. He would also like a custom recovery and ROM. I'm a little lost on this phone and have spent 3 hours reading at least on the forum between last night and this afternoon. Is it possible someone could give me some pointers?
Click to expand...
Click to collapse
GSM unlock http://forum.xda-developers.com/showthread.php?p=38485323
Custom recovery for locked device is safe strap...http://blog.hash-of-codes.com/downloads/safestrap/
how tohttp://blog.hash-of-codes.com/how-to-safestrap/
As far as ROMs for safe strap I don't believe there are many at all... but IMO debloated stock works its what I use even being unlocked just a little theming here n there n its good to go... hope this helps...
Sent from my XT907 using xda app-developers app
ezknives said:
GSM unlock http://forum.xda-developers.com/showthread.php?p=38485323
Custom recovery for locked device is safe strap...http://blog.hash-of-codes.com/downloads/safestrap/
how tohttp://blog.hash-of-codes.com/how-to-safestrap/
As far as ROMs for safe strap I don't believe there are many at all... but IMO debloated stock works its what I use even being unlocked just a little theming here n there n its good to go... hope this helps...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
I prefer using the NV Item method with CDMA NV-Items Reader Writer, offered free from CDMA-Ware.
(Credits for this go to tehjolly81 for his PagePlus guide to connect phone)
1) With the phone off, do the three-finger salute (hold Volume Up and Down and Power to boot) and boot into BP Tools mode (looks just like normal boot).
2) Now connect phone to PC via USB cable. If you are on Win7 x64 like me, Windows should find 4 new devices but won't have the drivers to install any of them. If prompted to install anything by Windows, (i.e., Add New Hardware Wizard, etc) cancel out of it.
3) Click 'Start' -> right click on 'Computer' and choose 'Properties'. Click on 'Device Manager' on the left. Here you should see 4 items from the phone that are missing a driver (they will have a yellow question mark next to them).
4) One of the items with a question mark should be labeled something similar to "QC Interface" (NOT the NMEA interface). Right click on it and choose Update Driver Software. Now choose Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Show all devices -> Motorola -> Motorola QC Diag Port. Finish running through the wizard and it should install the correct driver. After installed, it should show the COM Port # that the diagnostic interface is installed on under the "Ports (COM & LPT)" section of Device Manager.
After getting the QC Interface and getting a com port, just download the free NV-Items reader writer from Here.
Unrar the exe and run it;
1: Select the com port of your phone and hit connect
2: Press read at the top, bottom should say this: Log message: > SPC is correct. Phone unlocked
3: In Range (Dec): put 8322 in the left box 8323 in the right box and hit read; it will prompt to save as a text file.
4: Open the file and change the first 01 to 00 under the 8322 section DO NOT MODIFY 8323. Save the changes.
5: Tap Write and select the saved text file, it should show Writing NV-items from a file: Done at the bottom.
6: Tap Mode > Reset then tap Disconnect and close the program, GSM should work fine after that.
I find this method easier and less dangerous than the Radiocomm method.
This is *IF* you want to use Straight Talk's GSM BYOP, they DO offer CDMA BYOP now, which then should just activate like a normal Verizon phone after you buy their network code and activate the MEID with them.
Hi,
So I have had a good experience with the Kogan Agora 7" a couple of years ago. I flashed a new ROM and my 6 year old still idolizes it. It's perfect for games and movies while traveling and cost bugger all.
I was considering getting my kids a console unit for games but came across the new Quad core HDMI Dongle. I though to myself there is the ticket, When traveling i could use it as a smart TV (plug and play is King) Or it may be possible to replace or augment my Media-portal HTPC system.
I bought one and on the face of it it appears to do all that I require from an Android device like web surfing, mail checking and video streaming fine, except when it came to installing the Playstation controller.
I needed Root access and it was a bit of a pain to get it done. BUT I found it!
I used RK3188_ROOT for CX-919 FW0715 MOD by Everal. found here.
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Enjoy.
So if anyone decides to purchase one of these to play with, you will be glad to know that it is a Rockchip RK188. Weather you think that hardware is good or not is irrelevant but it is useful to know as I tried many methods to gain root but once I had this bit of info it became easy.
Those infinity Pocket PC's may be the same although I can't be sure.
I managed to pair a sixaxis controller and am working on getting it running in a game. I will post if i have any more issues and or success.
Raskern said:
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Click to expand...
Click to collapse
Thanks for posting this info. However I'm not able to get this to work. My PC doesn't recognise the device when it's in "USB Debugging" mode. In the device manager it just appears in "Other Devices" as "KHSTVQCDONA". I've tried updating the software, selecting the "usb_drivers" folder containing drivers provided in the downloading Zip file, and also tried downloading the "Google USB Drivers" directly from Google, but Windows doesn't find the drivers for this device.
If I disable "USB Debugging" the device does connect successfully under "Portable Devices", but clearly that's not much use.
I can't seem to figure it out.
Below are the steps I took in trying to get it to work. I was going to write it as a guide for dummies, but I never got it working...
Download the software from the link above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the bit "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC.
Make sure the Micro-USB port of the device is connected to a power source (either your PC or the provided AC adapter). The port doesn't seem to transfer data.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open the Windows "Device Manager".
In the "Device Manager", expand "Other Devices", then right-click on "KHSTVQCDONA" and click on "Update Driver Software".
Click "Browse my computer for driver software".
Navigate to the "usb_drivers" folder of the software you extracted earlier, select it, and click "OK".
Click "OK". THIS DIDN'T WORK, stating that "Windows was unable to install your KHSTVQCDONA" and "Windows could not find driver software for your device".
[*] Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator".
[*]C:
[*]cd RK3188_ROOT
[*]TPSparkyRoot.bat
At this point I see the following:
*---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
--- Plug in your device, make sure debugging is enabled in Developer Options
--- This script will now copy files over to your N101 II
error: device not found
error: device not found
error: device not found
--- Reboot 1/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
error: device not found
error: device not found
--- Reboot 2/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
--- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and star
t over
Press any key to continue . . .
Click to expand...
Click to collapse
I terminate at this point
I've also done the following
Un-ticked "Verify apps over USB"
In "Security", ticked "Unkown sources", and un-ticked "Verify apps"
At this point I'm totally at a loss.
I had already started using the device initially, so I did a factory reset, but this hasn't helped at all.
Can you see anything I'm missing, or point me in the right direction?
Many thanks in advance! :good:
Ok So I know i messed around with many drivers installing and uninstalling before it worked. I Thought it was the last set that came with the Root method but I may be wrong.
Also I cant remember exactly now but I am pretty sure if you activate the connect to computer you bypass the ROM and connect to the SD card and the U SD. So that would not help when accessing the root files.
Try re-installing the drivers after connecting without the box checked in settings or try the ones from super oneclick 2.3.3 or even the pocket pC ones. you may also need to uninstall the device then reconnect to get a clean run at it. Windows likes hanging onto what it thinks is the best driver even when they don't work or are completely wrong.
Also I ran the batch file form within windows not in console, Just right clock to run as administrator.
I have just used it for a couple of weeks in Japan get let the Kids watch Aview (iView) and it worked a treat. Also the latest sixaxis updates made the controller even better than before. I can probably have a tool around with it later this week but I am busy before then so wont be able to help any. It can be done!
PM me if you cant find the drivers mentioned above I can email them to you.
Thanks for the quick response.
Can you just confirm that you were connecting using the blue Male-Male USB cable, and not a USB-Micro-USB cable?
When I connect to the Micro-USB port it doesn't see a device at all. It just seems to provide power.
When I connect with the blue Male-Male USB cable, unless I have "Connect to PC" ticked, it also doesn't see a device.
I don't have a micro-SD card installed, but that doesn't matter right?
I'll try those drivers you suggest. Thanks.
I am quite keen to figure out what is different but I cant access it for a couple of days sorry.
I definitely used a full sized USB to Connect, I may have used another one, and powered it from the Micro USB direct to power supply. If you are connecting it to the PC for power it may cause problems.
I know that you cannot access the recovery menu unless you are powering through the Micro USB only. Another thing I meant to mention in my original post. I may have posted it elsewhere.
SUCCESS! After I got the SuperOneClick software to forcibly install the drivers the device was then recognised and I could root the device.
Thanks. I'll write up the full instructions.
Excellent!! Thanks for writing up the guide.
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
I had to do things differently......
Used rocketchip_batch_tool_1.7 for drivers, superoneclick didnt do anything.
I ran the batch from the folder on my desktop.
For EACH device re-boot i had to RE CHECK connect usb on cx919 settings.
I got a few errors about no more storage on my device when it tried to copy some stuff, although i have the super user and i tried sixaxis controller which requires root and it worked. Not sure what the files were.
update:
Hmm and it seems SSL websites dont work now as well as Netflix or the Store.
ill have to try something else!
Update:
did a factory wipe. all seems ok now.
TeqTeq said:
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
Click to expand...
Click to collapse
Worked fine since then. All a sudden same prob, no Netflix no store. Wtf?
Just wanted to post an updated root method since i got one of these second hand last week
1. get the universal rockchip drivers, or the latest generic google ones. both worked for me on two different PC's. (including windows 8.1 x64)
2. Enable USB Debug mode in developer options. you know the drill.
3. the kogan device has a "USB" menu in settings, that has a 'connect to PC' setting. turn that on or ADB cuts out shortly after the system boots - turn it off after rooting for it to work normally.
4. connect PC to kogan dongle via the USB port next to the power LED. The other one doesnt work.
5. root with whatever method you want - i used kingo root which rooted it flawlessly first time.
6. have fuuuuun!
3 and 4 stumped me for days til i figured out what was going on. not something i'd ever encountered before, and likely unique to this device and why some people cant figure it out.
Hey guys,I hope that all the awesome people here can help me to solve a huge Problem.
My GF had a Galaxy S5 Neo,she thought it would be a great idea to drop it directly on the screen so it broke and won't show anything anymore.
No we need to backup some important files from that device.
Gladly I was able to remove the lockscreen protection with her Samsung Account,but still not able to do more.
The device is on the latest official update,not rooted and no USB debugging enabled.
So I tried to get in recovery and use adb,witch will work every now and than,but I found out that the adb in stock recovery is limited,so now way to do anything there.
If I had enabled USB debugging,I could easily use visor to controll the device.
If I connect it via USB to my PC,it shows up,but as an empty device.
And I can't change the USB mode,because screen is completely dead.
Can I change the USB mode without the screen?
Can I enable USB debugging without the screen?
If I could change at least the USB mode,that could help out at least a little.
Long story short,I need an way to backup file from that thing.
If there is a solution for this,you guys would really help me out.
K-Town Rules said:
Hey guys,I hope that all the awesome people here can help me to solve a huge Problem.
My GF had a Galaxy S5 Neo,she thought it would be a great idea to drop it directly on the screen so it broke and won't show anything anymore.
No we need to backup some important files from that device.
Gladly I was able to remove the lockscreen protection with her Samsung Account,but still not able to do more.
The device is on the latest official update,not rooted and no USB debugging enabled.
So I tried to get in recovery and use adb,witch will work every now and than,but I found out that the adb in stock recovery is limited,so now way to do anything there.
If I had enabled USB debugging,I could easily use visor to controll the device.
If I connect it via USB to my PC,it shows up,but as an empty device.
And I can't change the USB mode,because screen is completely dead.
Can I change the USB mode without the screen?
Can I enable USB debugging without the screen?
If I could change at least the USB mode,that could help out at least a little.
Long story short,I need an way to backup file from that thing.
If there is a solution for this,you guys would really help me out.
Click to expand...
Click to collapse
Hey, i have similar problem, i cant unlock the phone so i have empty device at computer, i was wondering if you have any news on it
You Need OTG
Assuming
- you have stock 6.0.1 and
- you have enabled Developer options,
Here is an easy way:
1. Wait for boot to complete.
2. Once you feel like you're at the Touchwiz home screen, attach a keyboard to your S5 Neo.
3. On your keyboard, press Windows + N (Quick Settings tray).
4. Press Tab twice and Enter (Settings).
5. Keep on pressing Down Arrow for 5 sec.
6. Up Arrow one time and Enter (Developer options).
*** You can now (A) enable USB debugging and/or (B) change USB configuaration to MTP ***
7(A). Down Arrow * 7 times and Enter (USB debugging).
7(B). Down Arrow * 22 and Enter (USB configuration).
8(A). Right Arrow and Enter to allow USB debugging (OK).
8(B). Press Down Arrow and Enter (MTP)
9(A). Connect your phone to your PC *** You MUST keep your keyboard connected ***
9(B). Connect your phone to your PC.
10(A). On your computer, run "cmd" and type "adb devices" to authorize. *** You will see "unauthorized" from your cmd window ****
10(B). On your computer, you will see your device connected.
11(A). On your keyboard, press Tab * 3 and Enter (OK).
12(A). On your computer, type "adb devices" again to see if USB debugging works properly.
Note that this may or may not work for you depending on your firmware/settings.