Database Develop

Runnning the unlocker step-by-step

This excruciating step-by-step might help someone...
Wherever I mention establishing a WMDC/AS connection, make damn well sure that the connection is established... If you don't, you won't kill your device, but you won't unlock either.
-Establish a WMDC(Vista) or Activeysnc connection(XP)
-Confirm this!
-Start the unlocker program on your PC.
-Click "Flash SPL" (Step 1)
-Click "Yes"
-On the Treo you are prompted to allow the install of itsutils.dll and jumpspl.exe. Say YES to both.
*****The Treo will reboot. Don't click anything on the PC until the treo is back up and a WMDC/AS connection is re-established
-On your PC, you will see "Cheetah RUU". Click Next.
-Click Next again
-Click Next
-Click Update
-Click Next
-Click Next
******The Treo will reboot into bootloader mode and flashing begins. The device will reboot after the flash completes. Don't click anything on the PC until the Treo is back up and a WMDC/AS connection is re-established
-Click finish
-Click "Unlock Radio" (Step 2)
-Click Next
-Click Next
-Click next
-Click Update
-Click Next
-Click Next
******The Treo will reboot into bootloader mode and flashing begins. The device will reboot after the flash completes. Don't click anything on the PC until the Treo is back up and a WMDC/AS connection is re-established
-Click Finish
-On the PC is a notice "Read this through!". Confirm that you have a good WMDC/AS connection.
-Click OK
-On the Treo click "Yes" to allow athena unlock.exe
-On the Treo follow the instructions - check off SIM and CID unlock
-On the Treo click "Unlock" and wait for it to finish, then click OK on the athena unlocker on the Treo, and then click OK on the Treo to close the athena unlocker.
-On the PC, click OK
-Ensure you still have a WMDC/AS connection.
-On the PC, click "Flash normal radio" (Step 3)
proceed through the series of "Next", the device will go into bootloader mode and flash one more time. The device will reboot when done, and you should be all set.

Hey Summiter. Thanks for your tutorial. Got one question. I've done the whole process and now my SPL-says 1.40.01 OliNex. So I'am assumming that all went well. The only thing that gets me is that in you guide you state that this process will hard reset my device and all info. will be lost. My information as well as my programs all remained intacked. Is this OK. or am I missing something.
Thanks.

My bad..it won't do a hard reset. My device hard reset when I was running a different process, not the released unlocker. =) Sorry to cause concern.
As for the slow 3G speeds, Olipro is looking into it.
manfly9884 said:
Hey Summiter. Thanks for your tutorial. Got one question. I've done the whole process and now my SPL-says 1.40.01 OliNex. So I'am assumming that all went well. The only thing that gets me is that in you guide you state that this process will hard reset my device and all info. will be lost. My information as well as my programs all remained intacked. Is this OK. or am I missing something.
Thanks.
Click to expand...
Click to collapse

summiter said:
My bad..it won't do a hard reset. My device hard reset when I was running a different process, not the released unlocker. =) Sorry to cause concern.
As for the slow 3G speeds, Olipro is looking into it.
Click to expand...
Click to collapse
Thanks for your quick response.

Can anyone check Radio Ver after last step
Can someone verify the Radio Ver after 3rd step (Normal Radio Flashed Back to Device) , Olipro said to my post that by having Radio at 1.16 , i didnt complete last (3) step , but i defenatly did , and my Radio still 1.16 , where i had 1.52 before unlocking ???????????????????
Hitec

I called cingular tonight because i have been trying to get my 750 paired with my tom tom one 3rd edition for use of the weather updates and cameras and such. Through conversation with a support representative, and trying to troubleshoot why it couldn't use the wireless connection of the phone, the representative asked me to check a few things on my phone. While answering some questions, one of which was about device software and such and i told him i had windows mobile 6 installed.
From this point on he led into reasons why i should be using it with out it being released and such which is to be expected. He also stated that doing to much to the phone can possibly make the phone upgradable when the real WM6 update is released. This he mentioned were changing the boot loader, IPL and SPL software in the phone, that and using bogus releases of software. The reason being he said was that the soon to be released update probes the phone deeply because everything has been updated including the boot loader stuff.
Now i cant confirm or deny any truth to these statements but the only thing i had done with mine was a try a few new firmwares but after my conversation with them i quickly reverted back to WM5.

jhowle said:
From this point on he led into reasons why i should be using it with out it being released and such which is to be expected. He also stated that doing to much to the phone can possibly make the phone upgradable when the real WM6 update is released. This he mentioned were changing the boot loader, IPL and SPL software in the phone, that and using bogus releases of software. The reason being he said was that the soon to be released update probes the phone deeply because everything has been updated including the boot loader stuff.
Click to expand...
Click to collapse
F.U.D.
That's utter ****ing bull****, the RUU will do no such ****ing thing, and even if it does, there'll still be a base NBH to dump and flash... complete crap.
the bootloader might well have been updated, but the Hard-SPL one on there isnt going to let it overwrite it, mate.

jst passing on the info dude,, don't blame me.. they said it

mines unlocked anyway, but i did a remote unlock with GSM libeerty.com only cocts 39 bux and it does work. i figured if i spent 39 bux and avoided the potential of bricking my treo than it is worth it.

jhowle said:
mines unlocked anyway, but i did a remote unlock with GSM libeerty.com only cocts 39 bux and it does work. i figured if i spent 39 bux and avoided the potential of bricking my treo than it is worth it.
Click to expand...
Click to collapse
well not really, but you paid your money and took your choice

i guess i just see how the HARD SPL really does any different besides bypass the lock function. I have tried some very similar programz with my black berries and even after they said they were unlocked you could still goto the SIM CARD Screen under advanced options and hold ALT and press M - E - P - 2 and walla the code entry screen window would still come up.

after completing step 2, I don't even have the option to install athena unlock.exe ?
Also, it gives me an error after I click "Read this through"
What's going on?
Am I doing something wrong?
EDIT:
itsutils.dll didn't even install
During step 1, jumpspl and enterbootloader are installed, NOT ITSUTILS
Any help is appreciated

Why no flash?
I just tried running the unlocker. I have an AT&T branded and locked Treo 750 with Windows Mobile 6. When I run the unlocker, it installed itsutils.dll the first time, but the freeze that i am supposed to look for never occured. Then it installs the jumpspl.exe, and restarts. Then i wait until the ActiveSync is reconnected, and run the RUU. The RUU says that it fails flashing either radio (the patched one or the stock one) after 7%, and gives me an error. But then the unlocker application ran on the phone, and said it was successfully unlocked. I check the SPL version and there is nothing about 1.40 OliNex. Is there a step that I am obviously missing? I thought i had to CID unlock it first, but it gives me the option to CID unlock and it says it is unnecessary on the unlocker itself. Im sorry for being such a bonehead, but any suggestions? Thanks.

just goto www.gsmliberty.com it onlu cocts 39.99 for a remote unlock and there is no risk of bricking ur phone

unhandled exception error
Treo 750 with AT&T running WM5 trying to unlock to use on another GSM carrier. Downloaded the current treo 750 unlock software from this site. after step 2 I get unhandled exception error and cannot continue. Phone is synced properly and I have followed all steps to the "t".
I see this question asked many times throughout the site but never an answer. can someone let me know what causes it and how to fix it. I know lots of people would appreciate it.
Thanks in advance for your time.

JBoever said:
Treo 750 with AT&T running WM5 trying to unlock to use on another GSM carrier. Downloaded the current treo 750 unlock software from this site. after step 2 I get unhandled exception error and cannot continue. Phone is synced properly and I have followed all steps to the "t".
I see this question asked many times throughout the site but never an answer. can someone let me know what causes it and how to fix it. I know lots of people would appreciate it.
Thanks in advance for your time.
Click to expand...
Click to collapse
I think I manually copied the Athenaunlock.exe to the phone and ran it at that step. Note - this was after the special "unlock" radio had already been flashed. Finally, I did a hard reset and then installed a new OS - ROW 2.23 which previously would not load on phone (because it was locked).
I hope this helps.

unlock not working. unhandled exception
I get the following error after I finish the radio patch and it trys to run athen unlock.exe
Unhandled exception has occurred in your application. If you lcick continue, the application will ignore this erro and attempt to continue. If you click Quit. The appication will close immediately. (below are the details)
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at AthenaUnlocker.Form1.runExecutable(String path, String args, String wdir)
at AthenaUnlocker.Form1.button2_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
AthenaUnlocker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
zip
Assembly Version: 0.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
AthenaUnlocker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Same issue
Am currently trying to run from the SD card after updating .NET. Keep you posted

Can't get past the .NET error despite reloading latest version of .NET
Suggestions anyone?

alerner1 said:
I get the following error after I finish the radio patch and it trys to run athen unlock.exe
Unhandled exception has occurred in your application. If you lcick continue, the application will ignore this erro and attempt to continue. If you click Quit. The appication will close immediately. (below are the details)
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at AthenaUnlocker.Form1.runExecutable(String path, String args, String wdir)
at AthenaUnlocker.Form1.button2_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
AthenaUnlocker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
zip
Assembly Version: 0.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
AthenaUnlocker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/user/Desktop/CheetahUnlocker.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
Click to collapse
And NOW?????????

[Q] Rooting troubles

Hello,
I was looking for some help. I was using Perception 9.5 for several months, but decided it was time to change. I used Odin to wipe my Captivate. Now I'm trying to re-root so I can flash Serendipity. I've been running into some trouble getting my phone rooted again though. I've tried several different ways. Most recently, I tried the "One click root" format. When I get to the "root" click, it gives me back "Unhandled exception has occured in your application...
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at WindowsApplication1.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Galaxy One Click Root
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Collin/One%20click%20root/Galaxy_One-Click_Root.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box."
I also decided to try "Chaos Central"'s Captivate root from Android forums. I renamed the files to update.zip, but can't figure out where to copy them to.
Any help would be appreciated. Thanks a lot.

xThaNaturalx said:
Hello,
I was looking for some help. I was using Perception 9.5 for several months, but decided it was time to change. I used Odin to wipe my Captivate. Now I'm trying to re-root so I can flash Serendipity. I've been running into some trouble getting my phone rooted again though. I've tried several different ways. Most recently, I tried the "One click root" format. When I get to the "root" click, it gives me back "Unhandled exception has occured in your application...
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at WindowsApplication1.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Galaxy One Click Root
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Collin/One%20click%20root/Galaxy_One-Click_Root.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box."
I also decided to try "Chaos Central"'s Captivate root from Android forums. I renamed the files to update.zip, but can't figure out where to copy them to.
Any help would be appreciated. Thanks a lot.
Click to expand...
Click to collapse
I guess the first questions are,
did you flash back to JF6? did you do a Master Clear? Which version of Odin did you use?
I use One Click all the time, and have no issues at all
Edit** Oh yeah, have you enabled debugging on your device?

why are you even bothering to go through the trouble of rooting?
there are literally thousands of copies of the update.zip floating around here that you need in order to boot straight into CWM....in fact, heres another one
you dont even need to boot into your stock 2.1 in order to begin flashing...

I already got through the master clear with Odin3, so that wasn't a problem. It's just getting the root files to read that I'm having trouble with.
I was rooting because I need a root for Titanium backup. I have all my apps saved to that, and I will need to re-install them all once I get a new ROM flashed. What does that zip file do?

xThaNaturalx said:
I already got through the master clear with Odin3, so that wasn't a problem. It's just getting the root files to read that I'm having trouble with.
I was rooting because I need a root for Titanium backup. I have all my apps saved to that, and I will need to re-install them all once I get a new ROM flashed. What does that zip file do?
Click to expand...
Click to collapse
that zip file is clockworkmod recovery
if you need to root to do a TiBu, have you tried SuperOneClick?
http://forum.xda-developers.com/showthread.php?t=803682
enable usb debugging

I'm sorry, that's what the error was from. The big one that I listed was the error that I received from SuperOneClick. I can't figure out where to go from there.

You do not need to root. Use the clockwork mod update.zip posted on this thread. Reinstall packages twice, install zip from SD, choose, flash rom. Done
Sent from my Captivate using XDA Premium App

Am I supposed to be copying the zip to the internal or external SD then?

Okay, I did install, choose, then it has "meta-inf", "res", or "sbin". Which do I choose?

xThaNaturalx said:
Okay, I did install, choose, then it has "meta-inf", "res", or "sbin". Which do I choose?
Click to expand...
Click to collapse
please step away from your captivate
you didnt 'install' anything. copy the .zip to your internal sdcard....reboot into recovery, reinstall packages, it will reboot back into recovery, reinstall packages again and you will be in clockworkmod recovery
THIS WILL NOT DO A TITANIUM BACKUP FOR YOU!
if you really need the TIBU, i suggest you fix your java problems on your computer

mcord11758 said:
You do not need to root. Use the clockwork mod update.zip posted on this thread. Reinstall packages twice, install zip from SD, choose, flash rom. Done
Sent from my Captivate using XDA Premium App
Click to expand...
Click to collapse
This is what I was doing. I reinstalled packages twice. Then i Did "install zip from sdcard", then "choose zip from sdcard", and then I don't know where to go from there.

xThaNaturalx said:
This is what I was doing. I reinstalled packages twice. Then i Did "install zip from sdcard", then "choose zip from sdcard", and then I don't know where to go from there.
Click to expand...
Click to collapse
when you select 'choose zip from sdcard' you point it to the rom you want to install.
i would highly suggest you read a little more before you break your phone....you dont sound too confident

That's what I've been trying to do. I'm not very confident at all about it. But I was following what he said in reply to your zip file.

xThaNaturalx said:
That's what I've been trying to do. I'm not very confident at all about it. But I was following what he said in reply to your zip file.
Click to expand...
Click to collapse
from what it sounds like, you unzipped the rom somewhere?
you dont unzip anything when it comes to flashing....you just point it to the actual ZIP file to flash

Pirateghost said:
from what it sounds like, you unzipped the rom somewhere?
you dont unzip anything when it comes to flashing....you just point it to the actual ZIP file to flash
Click to expand...
Click to collapse
I didn't end up unzipping it. I didn't finish the last step of his process because I couldn't figure out what the last one was and didn't want to mess it up. Thank you again for all your help so far though.

xThaNaturalx said:
I didn't end up unzipping it. I didn't finish the last step of his process because I couldn't figure out what the last one was and didn't want to mess it up. Thank you again for all your help so far though.
Click to expand...
Click to collapse
his last step is 'flash rom'
what is confusing about that...point the 'choose zip' to the rom.zip thats on your internal sdcard.....select it and thats it.....it will flash the rom. then you reboot and you have new rom

Pirateghost said:
his last step is 'flash rom'
what is confusing about that...point the 'choose zip' to the rom.zip thats on your internal sdcard.....select it and thats it.....it will flash the rom. then you reboot and you have new rom
Click to expand...
Click to collapse
Well I just successfully got the root complete and Serendipity flashed. Thank you for all your help.

[TOOL][ROOT][RECOVERY]Ouya Toolbox v1.1.2 - 07/10/2013 - One-Click

Ouya ToolBox v1.1.2 - 07/10/2013
One-Click-Style Root/Recovery/Backup/Restore/Sideload/WifiADB
{
"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"
}
This is a compilation of commands that I found in tcollum's post in this thread in order to obtain a usable su binary, Superuser, CWM Recovery, BusyBox, and some other cool tweaks!
THIS DOES NOT CONFIGURE DRIVERS OR ANYTHING LIKE THAT!
YOU MUST HAVE YOUR DRIVERS INSTALLED PROPERLY OR THIS WILL FAIL
This is for the people who do not know how to download/setup Android SDK/ADT, or know much about ADB in general, and will root for them!
If you've never rooted before - this will root your device.
If you've lost root for some reason - this will root your device.
If you've lost root due to an OTA update - this will root your device.
(for the record: if you have lost your su binary from /system/xbin, you need to reinstall an ota update to recover it. this program does not restore that file, yet.)
If you are having any problems with this program not working right, or getting "exception" errors while using it, please use the TEST VERSION below!
Download:
Ouya ToolBox v1.1.2 - Download
Ouya ToolBox v1.1.2 *TEST* - Download
*TEST VERSION* If you're receiving an 'unhandled.exception' error when you load the program, PLEASE USE THIS VERSION FOR NOW!
50% of you guys are having issues with 1.1.1 or 1.1.2, and the other half aren't (myself included.) There is a problem with the way AndroidLib.dll interfaces with the Ouya's ADB responses. The author, @regaw_leinad and I are going to try to work together to get it resolved!
This version WILL work for you, for root and recovery, but there is NO detection support! It will ALWAYS say that the Ouya is connected!
Instructions
Connect Ouya to your computer via usb
If you're not already rooted (or have lost root,) your first step is to click the Root button. This will configure SU.
Next, install both Superuser and Busybox.
On the Ouya, run Superuser and select "Install" (NOT install from recovery!) from the options.
Run Busybox, grant it root access when it asks, wait for the files to verify on the screen, then select Smart Install.
After that, the rest is up to you! I would suggest installing CWM Recovery and making a full backup!
This program takes a few seconds to open when you run it, because it scans your computer to see if an Android device is attached, and also generates all of the files needed during the process.
I will be implementing more features very soon, and will try to make it look prettier for you guys!
PLEASE let me know of ANY bugs or problems that you encounter! This program is nowhere near complete or finished!
Working
* Root (su configuration)
* Install Superuser
* Install Busybox
* Device detection
* CWM Recovery Installation
* Sideloading APKs
* Manually reboot to.. system/recovery/bootloader
* Manually boot into cwm recovery from bootloader
* Real-time logcat system log viewer
* Open a standard user, or root shell
* Manually mount filesystem as RW or RO
Not Working YET (coding now)
* Wifi ADB toggles
* System Backup/Restore
* APK Backup/Restore
* Wireless ADB connection support
Thank you guys!
Changelog
Ouya ToolBox 1.1.2 (released 07/10/2013)
Modified AndroidLib.dll (thanks to regaw_leinad!) bug fixes&features:
* More detection bug fixes for those with Exception errors.
* Chaned gui appearance slightly
+ Manual installation of APKs
+ Links to FAQs
+ Manually mount filesystem as RW or RO
+ View logcat in real-time
+ Manually open a standard or root shell
+ Manually reboot to Bootloader
+ Manually boot into CWM from Bootloader mode
Ouya ToolBox 1.1.1 (released 07/08/2013)
Complete rewrite of root and recovery functions:
* Fixed broken root script from 1.1
* Fixed broken recovery script from 1.1
* Again fixed detection issues
+ Upgraded to AndroidLib 1.5.1.0 for better stability and improvements
Ouya ToolBox 1.1 (released 07/07/2013)
+ Added CWM Recovery feature
Ouya ToolBox 1.0.1 (released 07/07/2013)
Bug fixes:
* Fixed major bug where su file was not being generated sometimes
* Modified device detection, and it should not hang/freeze now
Ouya ToolBox 1.0 (released 07/05/2013)
This was the first public GUI release:
+ Auto-detects Android device connection
+ Configures SU binaries
+ Installs Superuser.apk and Busybox.apk
+ Quick system reboot
+ Reboot to recovery
+ Displays connected device ADB ID
+ About section with support and donation links
+ Manual device connection scan with Refresh Device button
+ Events disable functions if no device is found
+ Kills adb server upon exit
+ Auto populates resources if they're not found
Ouya ToolBox 0.1a (released 07/04/2013)
This was the first alpha, command-line batch script release:
* Configured SU binaries through ADB
* Installs Superuser and BusyBox APKs through ADB
Very special thank you to:
Natan G - For his $20 donation!
Dennis G For his $4 donation!

foil said:
This is a small .bat script that will run the commands listed in tcollum's post in this thread in order to obtain Superuser (su) and BusyBox!
THIS DOES NOT CONFIGURE DRIVERS OR ANYTHING LIKE THAT!
YOU MUST HAVE YOUR DRIVERS INSTALLED PROPERLY OR THIS WILL FAIL
This is for the people who do not know how to download/setup Android SDK/ADT, or know much about ADB in general, and will root for them!
This does not do anything else (ie: setup wireless ADB, etc..,) so check his thread if you want to manually do those things.'
I figured I would post this for now, until I finish my one-click style GUI application that I'm currently working on that will root/wifi-adb/backup/restore/install/recovery for the Ouya
I will modify this thread once my application is complete!
eta: 1-2 days
Download:
http://www.f0il.com/OuyaToolbox.zip
Instructions
Run ouya.bat
That's all
(package includes: adb, adbwinapi, adbwinusbapi, ouya.bat, smile.txt, fastboot, superuser apk, su binary, busybox apk)
Please let me know if you you have any problems, as this is just something that I threw together very quickly before work!
Thank you guys!
Click to expand...
Click to collapse
Thanks a lot, what is the differences with Ouya sdk helper ?
My edition : it'snt the same thing.

I'm not sure what sdk helper is??

foil said:
I'm not sure what sdk helper is??
Click to expand...
Click to collapse
this : http://news-ouya.blogspot.com/2013/07/ouya-sdk-helper-beta-2.html

simbaba said:
this : http://news-ouya.blogspot.com/2013/07/ouya-sdk-helper-beta-2.html
Click to expand...
Click to collapse
Oh wow, I've never seen that before! Looks pretty cool, though, I'm going to check it out.
Thank you!

Very cool!

When I go into SuperUser I get an install via recovery or install option. I picked the plain install option and it fails.
Something ain't right here, because I had SU before but jacked up my system trying to do the App store mod, so I had to manually sideload the latest ota update through adb.
Sent from my Nexus 10 using Tapatalk HD

Could you pare this down so that it only gets su back up and running after an OTA? I've been doing it with the Google sdk, but that is getting annoying to do so frequently.
Sent from my SCH-I535 using Tapatalk 4 Beta

Sorry if this is obvious to others, but I wanted to ask to make sure.
This can be used after losing root from an update? I originally followed tcollums instructions, but after each update you lose SU binary's.
I'm also assuming this script tries to sideload SU and busybox, but in my case those are still installed, so would you consider making two files, one that does everything from scratch and one that is made for those who have lost root from an OTA update?
One last question, and I'm pretty sure I know the answer, you just run this from your computer connected to the OUYA, right?
Thanks!

JLCollier2005 said:
Sorry if this is obvious to others, but I wanted to ask to make sure.
This can be used after losing root from an update? I originally followed tcollums instructions, but after each update you lose SU binary's.
I'm also assuming this script tries to sideload SU and busybox, but in my case those are still installed, so would you consider making two files, one that does everything from scratch and one that is made for those who have lost root from an OTA update?
One last question, and I'm pretty sure I know the answer, you just run this from your computer connected to the OUYA, right?
Thanks!
Click to expand...
Click to collapse
Yes, if you lose root after an update, just connect your Ouya to your computer via usb, run this script, and it will setup everything you need in order to be rooted again.
For everybody else that asked - I have added a NoAPK package in the original post, that does not contain Superuser or Busybox apk's, only SU binaries.
Kevinb - choosing the regular "install" option (not install from recovery) was the right choice, it should have worked for you.. When you run the script, are you seeing any errors or anything? I've ran it on my Ouya quite a few times before I posted it, and it worked every time, along with a few other people that were testing it for me.

foil said:
Yes, if you lose root after an update, just connect your Ouya to your computer via usb, run this script, and it will setup everything you need in order to be rooted again.
For everybody else that asked - I have added a NoAPK package in the original post, that does not contain Superuser or Busybox apk's, only SU binaries.
Click to expand...
Click to collapse
Thank you, foil! This is perfect! I was thinking of doing a script for it, but I have such limited knowledge of how to do them I was worried I might screw something up, so again thank you for doing this! I downloaded it and will be trying it out in a few minutes.

JLCollier2005 said:
Thank you, foil! This is perfect! I was thinking of doing a script for it, but I have such limited knowledge of how to do them I was worried I might screw something up, so again thank you for doing this! I downloaded it and will be trying it out in a few minutes.
Click to expand...
Click to collapse
You're welcome!
I'll be uploading my actual GUI program later tonight, and it will modify SU binaries, install superuser/busybox/cwmrecovery, and also reboot to recovery and backup/restore system, and sideload apk's

Hey foil, getting an error and I'm not sure why.
Maybe you can help me understand why it didn't work? I manually did it and I got SU back.
I did have to manually navigate to the platform-tools folder using 'cd' in order for the push su to work, which I have no idea why. I didn't have to last time.
Thanks!

JLCollier2005 said:
Hey foil, getting an error and I'm not sure why.
View attachment 2095906
Maybe you can help me understand why it didn't work? I manually did it and I got SU back.
I did have to manually navigate to the platform-tools folder using 'cd' in order for the push su to work, which I have no idea why. I didn't have to last time.
Thanks!
Click to expand...
Click to collapse
That's really weird.. you shouldn't have to cd into any directory at all.
Which of my packages did you download? And where did you extract the files to?
You shouldn't be extracting the files into your platform-tools folder at all, but in it's own folder instead, with all of the files in-tact.
Do you have google talk? I'd like to have you beta-test my gui, if you don't mind.

foil said:
That's really weird.. you shouldn't have to cd into any directory at all.
Which of my packages did you download? And where did you extract the files to?
You shouldn't be extracting the files into your platform-tools folder at all, but in it's own folder instead, with all of the files in-tact.
Click to expand...
Click to collapse
Yeah, that's what I thought too, didn't make any sense to have to change the directory. I downloaded the no apk one and extracted it to it's own folder on my desktop.
Do you have google talk? I'd like to have you beta-test my gui, if you don't mind.
Click to expand...
Click to collapse
I sent you a PM about this.

Original post completely updated, new GUI version of Ouya ToolBox is now released!

Very interest app Thx very much I wait wifi adb
Envoyé depuis mon Transformer en utilisant Tapatalk 4 Beta

Now you've released this, theres not really much point in me carrying on with my multi function script.
Thanks, you've given me the gift of time
If you need any help testing give me shout.

Application get's stuck
Hi!
I use win8 pro x64 and I'm sorry to tell you that the app get's stuck after the "device detected" dialoge.
When I start it with my ouya connected the gui doesn't even show up.
If I first start this app and then connect the ouya and press "Refresh Device", I get the "device detected" message and the gui freezes.
I disabled the comodo protection since i had similar problems some time ago with my smartphone.
The diver is setup correctly as adb lists the device.
let me know if you need more information.
Edit: I just disconnected my ouya and got this error (german os):
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei RegawMOD.Android.BatteryInfo.Update()
bei RegawMOD.Android.Device.Update()
bei RegawMOD.Android.AndroidController.GetConnectedDevice(String deviceSerial)
bei OuyaToolbox.Form1.Button6_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18046 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
OuyaToolbox
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Users/devil_000/Downloads/OuyaToolBox_v1_0/OuyaToolbox.exe.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 11.0.50709.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18045 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18046 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18022 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18046 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
AndroidLib
Assembly-Version: 1.1.0.0.
Win32-Version: 1.1.0.0.
CodeBase: file:///C:/Users/devil_000/Downloads/OuyaToolBox_v1_0/AndroidLib.DLL.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18010 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18010 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Zum Beispiel:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

Khaos666 said:
Hi!
I use win8 pro x64 and I'm sorry to tell you that the app get's stuck after the "device detected" dialoge.
When I start it with my ouya connected the gui doesn't even show up.
If I first start this app and then connect the ouya and press "Refresh Device", I get the "device detected" message and the gui freezes.
I disabled the comodo protection since i had similar problems some time ago with my smartphone.
The diver is setup correctly as adb lists the device.
let me know if you need more information.
Click to expand...
Click to collapse
I haven't personally tested on Win8 at all, although I do have a Win Server 2012 x64 machine here.
I'm wondering if the problem is within the AndroidLib.dll that I used, because at launch, and also when Refresh Devices is clicked, it calls a function from there.
I can compile a separate version without AndroidLib.dll, and we can see if that's the problem, but it won't detect the device at all (I'm not going to re-code that part.)
I can do that now, if you'd like to test it, but until I get the version 1.5.x version of AndroidLib, I'm not able to do much with it.
Edit:
I've uploaded a no-detection version for you to try, it's in the original post. Please reply back and let me know if it works for you or not.
Thank you!

Nokia OST couldnt run... pops microsoft .net framework error!

Hello,
i tried to launch OST but popping error... i dnt know why its like dat and i have searched online for help but none gotten yet. i have attached screenshots of the error here too!
i have windows 10 pro/64bits. i need help please!
thanks...

whalesplaho said:
Hello,
i tried to launch OST but popping error... i dnt know why its like dat and i have searched online for help but none gotten yet. i have attached screenshots of the error here too!
i have windows 10 pro/64bits. i need help please!
thanks...
Click to expand...
Click to collapse
Could you post all text information about the details of the error? (Right click, select all, copy)
Are you running the tool with administrative elevation?

dbpm1 said:
Could you post all text information about the details of the error? (Right click, select all, copy)
Are you running the tool with administrative elevation?
Click to expand...
Click to collapse
here is tha error code..... thanks big!
Im running the tool without administrative elevation.
I have net framework v4.7 installed.
Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MainForms.Form1.DisableOptions()
at MainForms.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at MainForms.Form1.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OnlineUpdateTool
Assembly Version: 6.0.4.0
Win32 Version: 6.0.4
CodeBase: file:///C:/Program%20Files%20(x86)/OST%20LA/OnlineUpdateTool.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MRG.Controls.UI
Assembly Version: 1.0.4854.21889
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/OST%20LA/MRG.Controls.UI.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

@bidhata @hikari_calyx @dbpm1 and others please help..... Thanks!!!

whalesplaho said:
System.NullReferenceException: Object reference not set to an instance of an object.
Click to expand...
Click to collapse
@whalesplaho I could not reproduce the error on two computers which i have tested.. but from what I could gather information about the error referenced above, there may be a problem with your .net install.
I've found two utilities that may help you fix the issue, but they should only point to problems on the .net installation, not directly solve them! You may run them just to have information on which version is crippled and then you should uninstall and install again.
Raymondcc .NET Detector
One way to check which versions of .NET are installed is through the system registry. If a .NET package is installed, its information should be correctly entered in the registry. We decided to use this method and create a little tool which does the plain and simple task of telling you which versions of .NET you have installed.
The tool couldn’t be simpler to use, just run the executable and it will tell you which .NET’s you have by showing them in dark text, the grayed out entries aren’t installed. Clicking on a non installed package will take you to its download page at Microsoft. The information from the window is copied to the clipboard to paste into help files etc. The program is able to detect .NET Frameworks from 1.0 up to the latest 4.7.2 (including versions specific to Windows 10), is portable and works on Windows XP and above.
Read More: https://www.raymond.cc/blog/how-to-...osoft-net-framework-is-installed-in-computer/
Download: https://www.raymond.cc/blog/download/did/1741/
Click to expand...
Click to collapse
.NET Framework Setup Verification Utility.
The .NET Framework Setup Verification Utility by Aaron Stebner is a very small and portable tool at only 272KB in size that you can use to verify the presence of files, directories, registry keys and values for the .NET Framework that is installed in your Windows computer. The latest version of .NET Framework Setup Verification Utility is able to automatically perform a set of steps to verify the installation state of the following .NET Frameworks:
.NET Framework 1.0
.NET Framework 1.1
.NET Framework 1.1 SP1
.NET Framework 2.0
.NET Framework 2.0 SP1
.NET Framework 2.0 SP2
.NET Framework 3.0
.NET Framework 3.0 SP1
.NET Framework 3.0 SP2
.NET Framework 3.5
.NET Framework 3.5 SP1
.NET Framework 4 Client
.NET Framework 4 Full
.NET Framework 4.5
Only the .NET Framework that the utility detects on the computer will be listed for verification so you won’t be seeing all of the above versions of the .NET Framework on the program. To verify the install state of a .NET Framework, simply select the version at the drop down box and click the Verify Now button. If the current status shows “Product verification succeeded”, then it means no problem but if you get a failed message, then you can consider reinstalling the .NET Framework version that has failed the verification.
Read More: https://www.raymond.cc/blog/net-framework-setup-verification-utility/
Download: https://www.raymond.cc/blog/download/did/2148/
Click to expand...
Click to collapse
If you have problems uninstalling or repairing, follow the tips here: https://www.raymond.cc/blog/uninstall-microsoft-net-framework-with-aaron-stebner-cleanup-tool/
Remember to reply if the issue was solved or not for future reference:good:
Good luck mate!

Tried everything and other method but no luck... I installed on a friends Windows 7 Ultimate and works very well!!!
Really don't know why its not working on my laptop... Really frustrating!!!

whalesplaho said:
Tried everything and other method but no luck... I installed on a friends Windows 7 Ultimate and works very well!!!
Really don't know why its not working on my laptop... Really frustrating!!!
Click to expand...
Click to collapse
That's really bad man, there must be something wrecked with .net on that laptop!
Can you run other .net dependant apps? Like Paint.net for example: https://www.getpaint.net/

dbpm1 said:
That's really bad man, there must be something wrecked with .net on that laptop!
Can you run other .net dependant apps? Like Paint.net for example: https://www.getpaint.net/
Click to expand...
Click to collapse
I have net framework working on my laptop... I have Paint.net app

Same problem here

V1c70rs said:
Same problem here
Click to expand...
Click to collapse
Had to reformat my laptop...

whalesplaho said:
Had to reformat my laptop...
Click to expand...
Click to collapse
Reformatting isn't a proper solution. Anyways, the error changed into "Culture id 3072 isn't a supported culture" when i updated OST LA to 6.37. After googling a bit, found out culture problem is related to Region and Language of Windows 10. So changed Region and Language to United States English even though I am not in USA. That got rid of the Culture problem and OST 6.37 started up fine but this version needs needed id and password. So uninstalled it, installed 6.04 version and it started up fine.
So, in short, the Solution is;
Change Region and Language to United States and United States English respectively.

This
Mist978 said:
Reformatting isn't a proper solution. Anyways, the error changed into "Culture id 3072 isn't a supported culture" when i updated OST LA to 6.37. After googling a bit, found out culture problem is related to Region and Language of Windows 10. So changed Region and Language to United States English even though I am not in USA. That got rid of the Culture problem and OST 6.37 started up fine but this version needs needed id and password. So uninstalled it, installed 6.04 version and it started up fine.
So, in short, the Solution is;
Change Region and Language to United States and United States English respectively.
Click to expand...
Click to collapse
This was the solution for me. Had been tearing my hair out because of this error. Just changed my region and boom! Thank you!

Mist978 said:
Reformatting isn't a proper solution. Anyways, the error changed into "Culture id 3072 isn't a supported culture" when i updated OST LA to 6.37. After googling a bit, found out culture problem is related to Region and Language of Windows 10. So changed Region and Language to United States English even though I am not in USA. That got rid of the Culture problem and OST 6.37 started up fine but this version needs needed id and password. So uninstalled it, installed 6.04 version and it started up fine.
So, in short, the Solution is;
Change Region and Language to United States and United States English respectively.
version 6.1.2 solved it for me.
Click to expand...
Click to collapse

Question Bricked with Black Screen. See on windows devices list account not ADB fastboot

My phone is has an unlocked bootloader, I had TWRP but i think i mistakenly formatted the recovery partition.
Now my phone is black screen only. It makes a noise when connected to PC but thats all. I have tried abd devices nothig listed
I tried me flash tool but it cant install driver -
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\n\Desktop\folder\MiFlash20181115\log\[email protected]'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at XiaoMiFlash.code.Utility.Log.w(String msg, Boolean throwEx)
at XiaoMiFlash.code.Utility.Log.w(String msg)
at XiaoMiFlash.MainFrm.RefreshDevice()
at XiaoMiFlash.MainFrm.btnRefresh_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
XiaoMiFlash
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/n/Desktop/folder/MiFlash20181115/XiaoMiFlash.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4550.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4395.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MiUSB
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/n/Desktop/folder/MiFlash20181115/MiUSB.DLL
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4435.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Any tips on how to recover this situation

If you have a black screen it looks you only can use EDL (testpoint) mode to recover the phone.
In that case you problably need an engineering rom or patched firehose file to pass the Mi authentication.
Maybe a modded Miflash tool without authentification could work too.
​
(For Poco M3 there is a description how you can do this)

I cannot strip open my phone its only a month old.
Elinx said:
If you have a black screen it looks you only can use EDL (testpoint) mode to recover the phone.
In that case you problably need an engineering rom or patched firehose file to pass the Mi authentication.
Maybe a modded Miflash tool without authentification could work too.
​
(For Poco M3 there is a description how you can do this)
Click to expand...
Click to collapse
I cannot strip open my phone its only a month old.

Unambiguous said:
I cannot strip open my phone its only a month old.
Click to expand...
Click to collapse
Then only you can contact the seller or Xiaomi service center

Unambiguous said:
I cannot strip open my phone its only a month old.
I cannot strip open my phone its only a month old.
Click to expand...
Click to collapse
Surely you can get to EDL mode without opening phone, there is a few ways. Have you tried reinstalling with miflash, relocking bootloader?, are you saying that your pc is not detecting the device at all.

Unambiguous said:
I cannot strip open my phone its only a month old.
Click to expand...
Click to collapse
You also can try first, very long power press. Without or with charger connected.
Sometimes this resolve the blackscreen problem.

Very frustrating. I don’t know what mode or state the phone is in. But it makes a noise usb noise when connected. Can’t detect in miflash
Will try another pc. If anyone is Will to join a zoom call to help
Am open to that too

gazza35 said:
Surely you can get to EDL mode without opening phone, there is a few ways. Have you tried reinstalling with miflash, relocking bootloader?, are you saying that your pc is not detecting the device at all.
Click to expand...
Click to collapse
Very frustrating. I don’t know what mode or state the phone is in. But it makes a noise usb noise when connected. Can’t detect in miflash
Will try another pc. If anyone is Will to join a zoom call to help
Am open to that too

Unambiguous said:
Very frustrating. I don’t know what mode or state the phone is in. But it makes a noise usb noise when connected. Can’t detect in miflash
Will try another pc. If anyone is Will to join a zoom call to help
Am open to that too
Click to expand...
Click to collapse
Have you just tried the long power button press, hold the power button for about 10 seconds, that should force a reboot, after a few minutes, connect to pc and try miflash again to see if it connects, you could also google XiaomiMiTool v2, that is another way of bypassing Xiaomi authorisations, has lots of useful tools to unlock \ Lock BL, flash etc, that may work for you, just need to get windows to detect the phone.
XiaoMiTool V2 Easy installation tool – Xiaomi Tools
xiaomitools.com

But overall the bad news is, the black screen of death as its known, usually requires a service at an outhorised repair shop, problem is youd probably have to pay, but i really dont think the charge would be too much, once repaired, i wouldnt mess with it again, id keep it stock.

gazza35 said:
But overall the bad news is, the black screen of death as its known, usually requires a service at an outhorised repair shop, problem is youd probably have to pay, but i really dont think the charge would be too much, once repaired, i wouldnt mess with it again, id keep it stock.
Click to expand...
Click to collapse
Ok thanks will have a look or send it for service
Phone only shows up on windows device manager not ADB list

I opened a service request via xiaomi uk and they are sending a jiffy bag. If they dont fix ill consider.
thanks for sharing. Am still miffed why i cant fix it myself.

Unambiguous said:
I opened a service request via xiaomi uk and they are sending a jiffy bag. If they dont fix ill consider.
thanks for sharing. Am still miffed why i cant fix it myself.
Click to expand...
Click to collapse
Glad youre getting it sorted. I know everyone likes to mess, flash, root, mod etc, but the development for this phone is patchy at best, nothing id consider a solid daily driver without issues, (NO disrespect to Devs intended because they work hard on these things for free). But my advice is simple, Unlock bootloader yes, but stick to to Stock Miui, whatever version you want to be on, at least ya guaranteed to still have a warranty and not worry about problems with bugs. Its a shame, but always issues with china phones, my previous was a Huawei, development again on that was really poor and you had to pay to unlock the bootloader. If youre looking for a phone you can constantly flash or mod then id suggest switch to a Samsung, me, im happy with Miui, especially for the macro camera and 4k video, its very good.

gazza35 said:
Glad youre getting it sorted. I know everyone likes to mess, flash, root, mod etc, but the development for this phone is patchy at best, nothing id consider a solid daily driver without issues, (NO disrespect to Devs intended because they work hard on these things for free). But my advice is simple, Unlock bootloader yes, but stick to to Stock Miui, whatever version you want to be on, at least ya guaranteed to still have a warranty and not worry about problems with bugs. Its a shame, but always issues with china phones, my previous was a Huawei, development again on that was really poor and you had to pay to unlock the bootloader. If youre looking for a phone you can constantly flash or mod then id suggest switch to a Samsung, me, im happy with Miui, especially for the macro camera and 4k video, its very good.
Click to expand...
Click to collapse
this will be my mums new phone...so good advise indeed.