Database Users

[REF] The DEFINITIVE MTTY Thread!! MARK 2 - HD2 Edition

DaveShaw said:
This is the second attempt at this thread.
Please try and keep it civil.
Thanks
Dave
Click to expand...
Click to collapse
Here Here and thanks a lot for re-opening!
Note: EVERYONE (Self Included) PLAY NICE!! This thread is for discussion of MTTY and not alternatives.
If you have an alternative post a thread for your own discussions
Thanks All
MG
Click to expand...
Click to collapse
Cotulla said:
Hello,
task 29 should work.
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Click to expand...
Click to collapse
Seems it's just copy-paste from another function.
It always outputed, so it can be ignored...
-Cotulla
Click to expand...
Click to collapse
Hi,
After the success of the Diamond Version of this guide I decided to "BRING THE RAIN" over here!! I noticed a post about a rom having random hard resets so I knew my calling was up!!
After what happened in the Diamond thread with the Tourists Im going to try and remove all repeat questions BEFORE they get asked so READ THIS WARNING:
F.A.T.M.T.I.D.Q:
(Frequently Asked TOO Many Times Infuriating Damn Questions):
-------------------------------------------------------------------------
1: "After task 28, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in the Diamond thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
-------------------------------------------------------------------------
As we all know MTTY is the key here, but I can say from personal experience that this small piece of software is a MASSIVE pain in the ass to get working, i must have tried 15-20 different “recommended” procedures to get it work and all failed.
But I managed to find a failsafe method of getting MTTY working on Vista AND Windows 7, also x86 AND x64!! (I have all 4 windows installations and the methods detailed below worked on all)
NOTE: WORKS WITHOUT DRIVER INSTALL ON XP
If for some reason you cannot got this to work on XP do the following: (Thanks kgerry!!)
kgerry said:
Hi,
if you run XP and you have Problems to connect to USB try following:
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader.
5. Now, run mtty ...
... try again to switch from COM1 to USB and follow the instructions of perfect post 3
Hope it helps ... Kgerry
Click to expand...
Click to collapse
Here is how this thread works:
Post 1: Description
Post 2: Driver Installation
Post 3: MTTY Instructions For FLASHING FROM INTERNAL STORAGE
Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM
THANKS to:
Reb0rn - for pointing me to the light!
l2tp - for the images
lunasea - for providing me with working drivers
and of course to anyone else I forgot.
I hope this helps people!!
MG
Donations:
stokedanuk
Thanks VERY muchly!!!

Driver Installation
NOTE: Drivers only need installed ONCE. After this you can just connect in BOOTLOADER and use MTTY.
Pre-Cursor To Driver Installation – FOR EVERYONE (x64/x86 Vista/Win 7)
This will remove the need for users, x64 in particular, to use “Unsigned Drivers.” Also since in Vista SP2 (x64 & x86) they removed the “F8” options Completely!
Files Needed:
Driver Signature Enforcement Overrider
Remove Watermark V0.8
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
3: Go Back to Driver Signature Enforcement Overrider Select “Exit” then Click “Next”
4: REBOOT
5: Run the “Remove Watermark V0.8” for you OS type (x64 or x84)
6: In the Command Window type “Y” and wait for the process to complete
7: Once complete REBOOT your system and begin the driver install
NOTE: If you DO NOT complete the above, some users will need to press "F8" During Bootup - (ANOTHER NOTE FOR x64 USERS, EVERY TIME YOU NEED TO USE MTTY YOU MUST REBOOT YOUR COMPUTER, HIT F8 AND SELECT: "START WINDOWS WITHOUT DIGITALLY SIGNED DRIVER CHECK")
For Info See Post Below:
Reb0rn said:
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
-----------------------------------------------------------------------
Big thanks to maybeme for providing a host for the images!!
1: Download the relevant drivers for your system attached to this post: these work for both Vista and Win7, all you have to choose is x86 or x64
EDIT: It has been found that with different versions of Windows 7 x64 need different Active Sync Drivers... If you are using Windows x64 please try x64 AS Drivers Win 7 Tested & Working.zip FIRST!!!
2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer
3: Bring device into bootloader (Reset + Hold Vol Down), This will show the Red, Blue, Green screen showing "Serial" - Once Computer booted, connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Go to "Control Panel -> System -> Device Manager" and select Microsoft Usb Sync in Mobile Devices section (NOTE: This MAY say HTC USB Sync but as long as you select your device!!):
5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"
6: Choose to "Browse Computer For Driver" (the second option):
7: Select "Let Me Pick From A List...." (the second option):
8: Click "Have Disk":
9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):
10: You will get back to previous screen, then click Install
10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":
11: The drivers will be successfully installed:
12: When you get back to "Driver Properties" check driver version. If the "Driver Date" has changed from 2nd step (2003 instead of 2007 - The year does not matter as long as it is not 2007!!), the installation has been a sucess:
13: Lastly leave the device connected and in "Bootloader" and reboot you system. Upon Rebooting an "Unknown Device" is installed, this is your HTC device.
Now the Active Sync Drivers are Installed

MTTY - Flashing From INTERNAL STORAGE
Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY
a: FULLY COMPLETE POST 1
b: Before you start grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: LEOIMG.nbh
2: Copy LEOIMG.nbh to the "Storage Card" of your Device.
3: Bring device into bootloader (Reset + Hold Vol Down), at first your HD2 will attempt to flash the LEOIMG.nbh you just copied to your Storage Card, you will have 2 Options, Press Vol Down to CANCEL THE UPDATE!! (DO NOT FLASH NOW!!) after pressing Vol Down you will now see the Red, Blue, Green screen showing "Serial"
4: Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
5: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
6: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
7: Run following commands:
7a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
7b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>
---------------------
7c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
---------------------
7d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
8: Immediately DISCONNECT your device and hold "Vol Down" to Initiate ROM Flash
9: After ROM flash Hard-reset (Pen Reset, then Press and Hold Vol Up and Vol Down) again, on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and allow the ROM to boot.

MTTY - Flashing From USB
Before you start:
a: FULLY COMPLETE POST 1
b: Before you start grab:mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
2: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
3: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
4: Run following commands:
5a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
5b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>
---------------------
5c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
---------------------
5d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
6: Immediately DISCONNECT your device then Press and Hold Vol Down to bring the device back to bootloader and connect to USB.
7: Run ROM Flasher and flash via USB. After rom flash is completed Hard-reset (Pen Reset, then Press and Hold Vol Up and Vol Down) then allow the ROM to boot.

This is the second attempt at this thread.
Please try and keep it civil.
Thanks
Dave

DaveShaw said:
This is the second attempt at this thread.
Please try and keep it civil.
Thanks
Dave
Click to expand...
Click to collapse
Here Here and thanks a lot for re-opening!
Note: EVERYONE (Self Included) PLAY NICE!! This thread is for discussion of MTTY and not alternatives.
If you have an alternative post a thread for your own discussions
Thanks All
MG

Thanks a lot MG !!!
As i told you,
A big thanks to you for your work here and your help by private message !
MTTY works like a charm !
Cheers my friend !

Driver Signature Enforcement Overrider has been a Life Saver on Windows 7 64 Bit, not just for the ActiveSync driver, also for using Open Source Audio Drivers.

Noonski said:
Driver Signature Enforcement Overrider has been a Life Saver on Windows 7 64 Bit, not just for the ActiveSync driver, also for using Open Source Audio Drivers.
Click to expand...
Click to collapse
I know, its brilliant, its in the second post!!
Love it!
MG

Hi,
I did precursor thing but i have a last question :
After that :
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
Have i reboot ? Or i have to go to point 3 directly ?
Thanks

sonydesouza said:
Hi,
I did precursor thing but i have a last question :
After that :
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
Have i reboot ? Or i have to go to point 3 directly ?
Thanks
Click to expand...
Click to collapse
Reboot first, and you should then see the mention of this mode in the lower right corner of the desktop.
After that use Remove Watermark also from second post to keep your machine in this mode for ever and ever, without having the annoying Developer Watermark.

Ok ! Understand ! that's why this "ONLY" point didn't work !
Thanks for help !

sonydesouza said:
Hi,
I did precursor thing but i have a last question :
After that :
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
Have i reboot ? Or i have to go to point 3 directly ?
Thanks
Click to expand...
Click to collapse
yes Reboot, then step 3!
ill change so is clearer!
Thanks for pointing out.
MG

MysticGenius said:
yes Reboot, then step 3!
ill change so is clearer!
Thanks for pointing out.
MG
Click to expand...
Click to collapse
Your welcome
Seems ok now ! Will tell you when i will flash another rom
See ya Dude !

Love this procedure. now, it is taking less than 30 seconds to format before I flash a new ROM. Much faster than flashing a stock ROM.

ebliss said:
Love this procedure. now, it is taking less than 30 seconds to format before I flash a new ROM. Much faster than flashing a stock ROM.
Click to expand...
Click to collapse
I thank you!! Finally people are seeing the light!
Welcome to the MTTY Crew!! 15 Minute Flashes for all (uning internal storage method anyway!!!)
MG

Glad you got a new thread man!!
Peace Out Bro!
Squirrel

SiliconSquirrel said:
Glad you got a new thread man!!
Peace Out Bro!
Squirrel
Click to expand...
Click to collapse
Yeah! Thanks to Dave is clean again!
MG

I had some trouble using MTTY on Win7 x64. Soooo, i switched over to my business laptop running WinXP.
First time run, worked perfectly! Thank you so much for this. I have flashed my HD2 over 30 times and it started showing some funny things that other users didn't experience with the same ROM.
Again. Thank you.

vr6only said:
I had some trouble using MTTY on Win7 x64
Click to expand...
Click to collapse
Follow POst 2!!
glad you found useful, but the main point of this thread is the Driver installation on Vista & Win7!
MG

alphaxsMOD2.2.0.1

Summary
alphaxsMOD2.2.0.1
Based on V9_GENERICV1.0.0B03
"Clean" Rom + Rooted
With : recovery-clockwork-3.0.2.8-v9-gen2 by Sebastian404
Hardware butons dont'seem to start recovery so use quick boot...for now
alphaxsMOD2.2.1 will be realeasad next, with new boot logo and with the basic apps loaded, and other improvements.
It will be installed via recovery.
This one is installed via FTM flasher - Multisales.
And is a room to use to upgrade from 2.1 to 2.2., or some emergency.
How to Install:
(this part used gtranslate(its 02:00 got to go to slepp)
from: http://androidpt.com/index.php?option=com_...0&Itemid=30
Good Start for general tutorial to upgrade to 2.2
NOTE: Due to some errors advise drivers who have a machine with XP to use for this process, who do not have it you can create a virtual machine with virtual box (always the way trust me)
1 - Download from:
Sales_MultiDL_MSM7227
Sales_MultiDL_MSM7227_patched
alphaxsMOD2.2.0.1
2) Unzip everything to a directory
3 - Install the program Sales_MultiDL_MSM7227_V1.00.01
4 - Copy the file to the folder Sales_MultiDL_MSM7227_patched.exe program installation
5 - Run the program Sales_MultiDL_MSM7227_V1.00.01 and indicate the path to the directory where the room was extracted alphaxsMOD2.2.0.1
6 - With ZTE off removing the battery and wait 10 seconds, can touch the contacts of ZTE to accelerate discharge wastewater, and then reconnect the battery.
7 - Press (and hold) VOL (-) & VOL (+) and then also press the power button button, (you'll see the light flashes one time).
8 - Now turn on the ZTE with the USB cable to the PC;
9 - Go to My Computer, selecting with the right mouse button and choose to manage;
10 - Select the Device Manager and go to the port and see the number that appears;
11 - Go Sales_MultiDL_MSM7227_V1.00.01 window and select an ADC that port;
12 In low-in 'Information File' clicks SW Directory and browse to the folder 'alphaxsMOD2.2.0.1'
13 - Select 'Backup NV' and then 'Start All'
14 - Will you stay with a new file in the program folder called 'Channel1.nvm' (make a copy for safety) (if error, does everything till the end if you finish with FTM screen returns to repeat the process, the second time ja will create the file correctly (may be the first time at 0 kb)
Just checked myne and the imei changed to, so it must be the NV step!!!!
In my case it didn't want to do it so i was forced to skip it...
the second time it did created a NV file with no problem... but i figured now that it was it the wrong imei this time...
So try to make the NV backup
15 - Now in Action Mode select 'Download' and then 'Start All'
16 - Began ensures that not even turn off the PC or the tablet!
17 - If everything went well you have the 2.2 if you stay locked up on the screen MTF (if the file has 0 kb Channel1.nvm can happen, then repeats the process going and this time the backup already generates a file of any size. If FTM der again takes the battery and repeat the process that I explained before, then waits for the first boot takes more time. You can also try to link carrying power & vol +

Rooted Locked Razr M/ How do I get recovery/GSM Straight Talk

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.

Kogan Agora HDMI Smart TV Quad Core - Root Access

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.

How to unlock your bootloader, without losing your data

Disclaimer: Use at your OWN risk. Data loss is possible. If anything goes wrong, don't blame us. We are only trying to help.
Credit:
Person who came up with the idea @Naman Bhalla
Person who edited the rawprogram0_64G.xml @Naman Bhalla
Source to the original OPO Recovery tool and the drivers.
Credit to TWRP, for their 2.8.6.0 image we are using.
Source to the bootloader unlocker.zip
Special thanks to @indest on OP Forums for being a real trooper and risking its life for the community.
Download:
Tool + Driver + Bootloader Unlock zip
Also, download the ROM you currently have. The exact same version number!
I repeat, you must have a copy of your current ROM!
Setup:
Download the above files
Connect your OPO to the computer (Windows 7, 8 or 10)
Press the volume up + power button (at the same time) until you feel a vibration
If your device says fastboot, press the volume up + power button again, till your screen goes black and you hear a sound on the computer.
Start> Device Manager
The following drivers should be detected automatically in device manager (Qualcomm HS-USB QDLoader 9008)
If ADB interface is seen, read step 3 again
If you see QHSUSB_BULK
Start> CMD (RunAs Admin)
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Reboot your computer
Enter Device Manager (start> device manager)
Right click QHSUSB_BULK> Update driver software> Browse my computer for driver software> Browse
Select <path of unzipped files>\Drivers\Qualcomm 2012
Check "include subfolder"> hit Next
Navigate to '<path of unzipped files>\OnePlusRestoreTool" folder
Right click on the "OnePlusRestoreTool(64GB).exe" and 'RunAs Administrator"
The program should start automatically doing its thing. If not, select the line that says 'COM' and hit start.
Once you see green text, hit log and make sure you have a BIG GREEN OK.
Unplug the device and press the volume down + power button till you feel a vibration.
It is important that you do not boot into your system, else, your data partition will suffer!
TWRP should now load. Once loaded, click Mount.
Connect your OPO to the computer.
Toggle off/on MTP (MTP should be ON)
Using your computer, transfer your ROM and the OnePlusOne-BootUnlocker.zip to your "Internal Storage".
Hit the back button
Hit install> go to /sdcard/OnePlusOne-BootUnlocker.zip > swipe to install
Then hit install again> go to /sdcard/<rom zip> (the one you started with) > swipe to install
Reboot device.

Isn't indest the best?

Awesome as always

pass for archives?

Hi, the download link is asking for a decryption key
Also does this still work in 6.0.1?