Database Info

Activesync doesnt work, cant access File explorer what to do?

Hi,
my Vox was ok with Fireburned Clean WM 6.1 ROM.
I wanted to install the 96 DPI cab taken from
http://allshadow.com/forum/viewtopi...k=t&sd=a&sid=4e574745def746ba36125fd49101481a
I installed correctly following the instructions, and rebooted.
Now, after boot, the following things dont work.
1. File explorer - so i cant go to any folder or delete any files on \windows folder.
2. activesync connection is broken so i cant install a new ROM.
3. recently accessed app list shows blank.
4. my home screen is blank.
The only thing that works is the dialpad where i can make voice calls.
Can anyone tell me how to do a hard reset (any key combination or shortcut??).
Thanks in advance.

I recommend you to uninstall 96 DPI update. To do this, flash your Vox from SD card instead of using ActvieSync connection. How to do this, check Vox Wiki.

Hard Reset Second Way:
Turn off your phone, then press both *SOFT KEYS* and *POWER ON* device. After moment release both soft keys. On the black screen asking for confirmation press *GREEN PHONE BUTTON* and wait couple minutes for phone to initialize.
If you cant make it with this [you must have good timing].. turn off your phone, hold camera button, and plug usb.
the u can run a rom update utility.

akumalol said:
Hard Reset Second Way:
Turn off your phone, then press both *SOFT KEYS* and *POWER ON* device. After moment release both soft keys. On the black screen asking for confirmation press *GREEN PHONE BUTTON* and wait couple minutes for phone to initialize.
If you cant make it with this [you must have good timing].. turn off your phone, hold camera button, and plug usb.
the u can run a rom update utility.
Click to expand...
Click to collapse
i tried trizzos method. but everytime i press camera and plug usb power, the "upload from sd card" screen would come and then just show the bootloader. i formatted twice to FAT32 but still no luck.
Then i followed akumalol's two ways,
the hard reset via soft keys + power key combo didnt work. i tried few times.
But, the second method worked!!!!!!!!!
that is
1. switch off phone
2. hold camera button and plug in usb power cable
3. phone boots to bootloader
4. now use any of the OS drop posted by our Gurus, and execute Flash.exe, it then connects to the phone via activesync and downloads the image.
Thanks very much guys. i will take note of this method as this is my first bricking the phone although the phone came up but no activesync no file explorer.....
Thanks again Trizz and Akumalol.....

Well I tought hardreset would be ur lasta alternative... the method posted by akumalol is the only one i ever used and it works but you have to put ur finger on the softkeys in less than a second after u have powered on the device..this is why some users have no luck with it...u have to be VERY VERY QUICK!

i tried 4 times with no result.. it directly booted to the current OS.
maybe i have poor reflex than you folks..

ahahah no it's a tecnique issue...put your thumbs on the softkeys and with an other free fingers power on the phone... don't tell this to anyone it's a secret tecnique

hahaha. thanks. i will try it when i bust my phone again !!!!.
anyways. thanks for your help.

Clarifications Needed: for a VIDEO GUIDE version of HOW TO FLASH A ROM...

I've been working on a step-by-step CLOSE-UP VIDEO guide to Flashing a ROM, including how to HARD SPL, to make available to users here. Here are things I'm still not clear on.
(These were posted recently to the Guide written by mskip in the Kaiser forums. He answered some questions, but these are still unanswered. )
Flashing via ActiveSync with USB Lead
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
Click to expand...
Click to collapse
** When is this step necessary & required (whether during initial HARD SPL or FLashing a ROM post-HardSPL) , as opposed to simply "Best Pratices"? What is this step accomplishing?
8. After a few seconds the tri colour screen will appear on the phone and "USB" will be displayed at the bottom
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
Click to expand...
Click to collapse
** Please explain #9, what it is accomplishing & thus why recommended?
"Active Sync" vs "USB connection"
Please tell me if this is accurate or not:
(1)When installing via PC vs installing via Storage Card: After data has been backed up to PC by way of "Active Sync", thereafter, when performing any ROM updates (HardSPL or flashing a new ROM) the app "Active Sync" is technically no longer involved in the flashing process, but rather, what's necessary is simply having a USB connection from device to PC, correct? Is the distinction that Actice Sync can foul up the basic data connection from phone to PC necessary to flash a ROM. I want to be very clear. Is this accurate?
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
11. Microsoft ActiveSync icon will now have a red cross in it and the program will say "Connection Disabled"
12. Run the ••••••RUU.exe file on your PC thats in the same folder as the HardSPL .nbh file and follow instructions (ticking boxes and clicking Next) *DO NOT reenable USB Connections in Activesync*
Click to expand...
Click to collapse
** same as above: Are these just more compensations in order to disable MS's incorrect assumption that the insertion of a USB cable always equals "launch an Active Sync session" ?
15. Unplug USB cable from phone then REPLACE SIM & SD CARDS !!
**Remember to re-enable "Allow USB connections" in Activesync connection settings after a successful flash**
Click to expand...
Click to collapse
Why, exactly, is it required to unplug the USB cable? Is it, again, a "Best Practices" precaution to prevent any kind of accidental read/write of data?
A few questions re entering Bootloader mode, various scenarios:
1. In some older guides, even for when flashing a rom to phone device from your PC , sometimes a step is specified to "enter Bootloader mode by holding & pressing the xxxx and xxx keys on your phone, and then xxxxx".
2. But if you have an RUU folder that includes the Bootloader.exe app, along with the RUU.exe and .nbh file, then by running the RUU.exe app, the entering bootloader mode is handled automatically, sending the commands to phone, which automatically place the phone into the tri-color screen mode? -- as opposed to one having to manually press xxxx and yyyy on phone to enter bootloader mode? Correct or not?
3. If correct: then, does it matter on which screen or in which mode your phone is currently on in order to begin the flash-ROM process? Could I just as well be on a Total Commander app screen or on a TouchFlo Today screen?
4. Some guide-writers recommend users hard reset their phones before starting a new flash-rom session, just for "best practices". Others consider this superfluous & irrelevant, and what matters most is a Hard-Reset be run immediately AFTER flashing a new ROM. ... Any opinion on this?
Flashing Via ActiveSync
<snip; this is deep into the flashing process >
2. Turn phone back on and wait until it syncs with your PC
Click to expand...
Click to collapse
** Would it be more accurate to say here "until your PC confirms it has a USB connection to your phone"? (You're not looking to run a sync session, but rather just getting a USB connection for files to be transferred from PC to phone.) I think the term "Active Sync" often creates more confusion than helpfulness in this whole realm of moving files from PC to phone. )
Question re RUU.exe file on PC:
From what I have seen in the ROMS I have used in years 2008-2009, the extracted ROM folders I've downloaded from the chefs have typically all had the file " Bootloader.exe " within the RUU folders, and that (in the case of mskip's Flash Guide for Kaisers) KaiserCustomRUU.exe calls the Bootloader.exe app which sets the phone into bootloader mode from the PC, without one needing to manually set the phone into bootloader mode.
But this is your response from your initial quick-reply, which confuses me"
The customRUU automatically puts the phone in bootloader mode thus there is no need for the seperate file (bootloader.exe).
Click to expand...
Click to collapse
** This confuses me. I am principally trying to distinguish between when one needs to manually set phone into bootloader mode -- and when this step is handled by the PC's RUU.exe process. In the older (around year 2007) "How to flash" guides, users were often told they needed to create a folder, make sure they have the correct RUU.exe file inside it, make sure they have the correct .nbh file, make sure they don't have files that are there for those with soft SPL phone, etc. And as far as I can recall, in those older Guides, this bootloader.exe file was not included. And thus users were instructed to manually put their phones into bootloader mode...
The difference being that for the past year or more, chefs currently are now providing the whole contents of the RUU folder in the .rar file, so that if you've hard-SPL'd, then that .rar file has eveything you need, and all you need to do is launch the RUU.exe -- never having to set your phone manually into bootloader mode.
Yet you are saying
Quote:
thus there is no need for the seperate file.
Click to expand...
Click to collapse
I'm not a coder, but I don't get this. Why would bootloader.exe be inside practically every RUU Folder nowadays if it were unnecessary to set the phone into bootloader mode to initiate the flashing process? You were saying the RUU.exe app itself would contain some method of setting phone inot bootloader mode without even needing that bootloader app present in the folder.
Could someone please clarify.
And secondly: Does it matter one bit of difference which screen your phone is on when you commence with running RUU.exe ?
And third : If users happen to be confused, and think they must manually set their phone into bootloader mode, as part of running RUU.exe, and they do manually set their phone inot bootloader mode and get the tri-color screen: Does that conflict with or hamper in any way the running of the RUU.exe program from the PC? Or does the RUU process just simply proceed, and send an "enter bootloader mode" instruction to the phone, which then causes the phone, already in tri-color screen, to be reset again into bootloader mode (and there is no problem that the phone was already in bootloader mode) ?
After New Rom is Completely Installed and You Have Customized Your Phone:
** I think it in dutty's guide where he says "after customizing your phone, power down your phone, then power it back up". Is this power-down/ power-up cycle equivalent to just doing a soft-reset? What is the difference as it pertains to that specific step after customization?
Quote:
Flashing Via MicroSD Card
<snip>
3. Goto the Roms Folder and rename the .nbh file to KAISIMG.nbh
4. Copy the KAISIMG.nbh file to your MicroSD Card
Click to expand...
Click to collapse
** Where does one get the correct 4-LETTER CODE for their phone if one has a DIFFERENT phone than Kaiser and wants to flash via MicroSD card?
-----
Thanks to anyone who can please clarify these points

2. Removing the battery is not required in any level of flashing a ROM. removing the battery for Hard-SPLing is not required on all devices. For instance, my polaris doesn't require removing the battery.
9. Not sure why you need to do that but it IS necessary (you can pm Olipro about it) but i'm pretty sure it has to do with updating the connection between the PC and the PDA since while in Bootloader the PDA doesn't act as a plug-and-play device.
11. I don't recall this being an important step as I flashed hard-spls and roms without changing the AS state. you HAVE to have an activesync connection with your PC in order to flash (doesn't have to be synced, but the PDA has to be recognized by activesync, hope this is clear).
15. Yes, it is not a MUST. you can flash roms and spls while leaving the cable connected.
---------------------------------------------------------------------------------------------------
2. Yes, if you have the full library containing bootloader and everything you can flash without entering bootloader manually prior to flashing.
3. flashing doesn't require a specific state. you can start the process whenever.
4. Hard-reseting before MIGHT make a difference... in some cases which i'm not familiar with. maybe there's an app which can disturb the flashing process.
Hard-reseting after is pointless as flashing a rom performs exactly that WHILE switching the OS.
-about the syncing.. yeah, you don't need an actual sync-session. a usb connection is enough (AS LONG AS the comp identifies the hardware of course)
-it doesn't matter if you have the bootloader.exe file inside or not (I assume it depends on your device as well.. but not sure). RUU runs bootloader automatically. about HARD-SPL.. yeah, i haven't seen a hard-spl which doesn't contain bootloader.exe.. (i again suggest you pm olipro about this)
-again, it doesn't matter which screen you're on when running the ruu
...
-about the phone codes for flashing... you can find all codes for all phones in the forum
for instance,
Polaris -> POLAIMG.nbh
Hermes -> HERMIMG.nbh
Blackstore -> BLACIMG.nbh
Diamond -> DIAMIMG.nbh
Raphael -> RAPHIMG.nbh
Trinity -> TRINIMG.nbh
yada yada...
you can search, and i'm pretty sure not ALL devices have this option..
the wifi also contains info about flashing from SD card.
also, wonderful initiative and i hope you will agree to post this in the GUIDES thread.

RhodiumW Hard-SPL Release

preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!

-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-

Consider yourself... sticky

Thank you Olinex. Great WORK

thank you! can someone please tell me what this does for my vzw tp2? thank you so much .

buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.

Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.

You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.

Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.

What specific error message(s) are you getting?

Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.

You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.

but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.

Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.

That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!

thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.

Have you tried taking out the battery of the phone, reinserting it and turning it back on?

trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol

buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.

I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?

[SOLVED] - [Q] Fujitsu Simens loox N560 died after bad firmware

hi.
I'v got loox n560 that was upgraded to WM6.1-6.5 servel times without any problem.
the last time i did update, i did it accidentally with a bad firmware file(uncompleted download).since then, the device wont boot(just a white screen).and the pc wont recognize it.
any way to save it? or i made myself a nice paper weight?
thanks.

I think there was a way to put the N560 in bootloader mode by pushing some keys and soft-reset hole manually (the "monkey grip" it was called or something similar...) and with the file of the rom to be flashed in a SD card... perhaps you can google for information on this ancient -and more unsure that the cable one- flashing mode. Worth to try it better than have a paperweight...
Good luck!

I give you more information (shame that FIRSTLOOX information is not there anymore)
For manual bootloader mode: press On-Off button + left side button (voice recording) + stylus soft reset (for some seconds). Keep pressed On-Off and recording untill the dolphins appear.
I can't find references to flash from SD card. Anyway, for incomplete flashing, Newplowe gives this procedure:
"You should close process "wcescomm.exe" on PC in task manager. Then hold button record, power and puch reset after that you will come in boot loader. Run the program mtty.1.42 and select usb connect. If You will see the any error just start again mtty. Put command l c:\os_213u.nbf (You should put correct flash file in c:\ or use correct path to os_213u.nbf, l - like L but small). When it will done You should start PocketLOOX5xxFlashTool.exe and flash you PDA."
I got this reference from "http://forum.xda-developers.com/showthread.php?t=429148&highlight=flash+n560+card".
Good luck anyway.

this is very interesting...
i was able to put the device into boot loader mode and ran the command "L c:\os_213u.nbf" ("l" didnt work, but L did).
it did something to the device, a progress bar till the end of the screen.but the device didnt reboot.when i try to run POCKETFLASH program it couldnt connect to the device.
i runing windows 7, so i guess it the problem(ACTIVE SYNC is a XP PROGRAM).
i'll try installing XP on another computer and try this again.
thansks.

almost...
i have installed Windows XP just for this, and everything seems to go well, i connect with MTTY, put the l c:\os_213u.nbf command and the device respond.
the next stage i to flash with PocketLOOXN560FlashTool.
when i start it, i receive connection error, and then i go to recovery mode.the program try to communicate with the device, but i get at the end error that the ROM language is different than the language on the device.it says "(ENGLISH)" and there are also empty
()
Click to expand...
Click to collapse
at the end.
i doubled checked this with the original WM5 English rom, and its the same.
is there a way to change the language with MTTY?
any other ideas? its a shame to stop now after i can get a response from the device...
thanks.

The only idea I have is to check if after the failed flashing your N560 is still an "english" one. Perhaps the defective rom has changed the language of your device to something else...
If your device respond to communication with the XP computer, perhaps you could make a rom dump (in newplowe's page you can got tools for doing that) and check in the dump file with an hex editor which language actually has. You can always check newplowe's blog and forum (with google translator ), or ask him

Sorry i didnt post an update.
i have fixed the rom language.it had a gibberish mark at the end of the ENGLISH, after i have fixed that, .the device was flashed correctly and its working!
thanks for thelp guys

[GUIDE][Cube i6 Air (3G or Wifi)] How to install Windows 10 !

Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Update your EFI BIOS
Install Android 4.4.4 (Stock & RemixOS)
Disclamer: This process might contain ROM hacking, this is for advanced users.
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
2 Flash Drives (1Gb or more, and 4Gb or more)
OTG cable
USB Hub (3 Ports recommended)
WinPE for Win10 (Downloadable on my drive)
Win10 32 bits ISO (link in tutorial)
THIS IS THE LINK I'M REFFERING TO WHEN SAYING "THE DRIVE"
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
What to do :
1.) Start by plugging the first usb drive (1Gb or more) into your computer, and format it to FAT32 using any formatting tool,
MAKE SURE YOU CHANGE PARTITION TABLE STYLE TO GPT, EITHER YOU WILL END UP WITH ERROR ON WINPE INSTALL
2.) Now you need to download WinPE from the drive, go to your device folder, then go into the windows folder, and download it.
Once you downloaded it, uncompress. You will find a "WinPE_XX" folder inside, take all of its content, and extract it to your freshly formatted drive.
Heres what looks like the root of your key:
3.) Your USB Install Drive is ready. You can plug it off and save it for later.
You now need to download a 32Bits ISO version of windows, if you already have one, it should work, if you don't, you can download it from Microsoft Website
4.) Now take your downloaded ISO, and mount it with either windows, daemon tools, PowerISO, or any Disk Image Manager.
Once mounted, you need to navigate to the X:\sources\ folder, and extract "Install.wim" anywhere on your PC. Thats the windows system we will install.
5.) Go to the drive, into your device folder, go to windows folder, and download the "Image_Recovery_Extra.zip" you can find there.
It contains recovery + Files mandatory for install (because the Windows PE we're using is hacked from Cube).
6.) Take your second USB Drive (of 4Go minimum, it needs to hold windows), and format it to NTFS Filesystem with any formatting tool.
Now you can extract the "images" folder of the previously "Image_Recovery_Extra.zip" downloaded (KEEP THE IMAGES FOLDER THIS TIME)
And also copy inside that "images" folder your previously extracted Install.wim image file.
7.) You're good to go ! You can unplug the keys from your PC, and start working on the tablet as of now !
You need to boot to BIOS settings, using "ESC" key at startup of tablet. Once there, go to SCU Settings, the bottom right square.
You need to set your primary boot to "Windows" in the boot tab, or the key won't boot. If it is already, you can exit SCU and start step 8.
If it is not, just select it, then press F10. Tablet should reboot. Press ESC again at startup, and start step 8.
8.) Now everything is straightforward: Just select "Boot from EFI File", select your USB key in the list, and go to EFI folder, then go inside BOOT folder, and select "Bootia32.efi"
The tablet should boot to a command prompt (it lags much, but we will install drivers later) and it should install windows automatically then shut down.
If install fails, update your BIOS and try again or post here for some help.
Preparation looks like this:
Working device looks like this:
9.) Now you can get rid of the installation USB keys, you only need mouse and keyboard. Fire up your tablet freshly flashed, it should boot to a chinese logo with a circle under it. it might reboot a few times, it is actually expanding filesystem and populating your win10 install. Wait until you end up in language screen. if it shuts down, put it on again if it does not automatically.
10.) Windows is ready, now follow the instructions, language, set your name, until you end up on the windows desktop. When you are here, you need to download from the drive the Driver Package for windows 10, which is located inside the driver folder, inside the windows folder of your devices folder. It sould be named "Z37XX_CPU_Chipset.zip"
Extract it on the tablet, and run the included "Setup.exe". When finished, reboot your tablet.
you can also find various driver i added for os switch and gyrometer
Congrats! You successfully Installed Windows 10!
I do not guarantee it works on every device, nor with every windows version, but it works in my installation with a regular Win10 x86 Pro.
There might be some upgrades to do, as I personnally hacked the WinPE that is available on Cube's site, with Windows 10 ADK WinPE,
so feel free to report bugs, enhancements to this method. and report cube for not doing this so far !!!
Regards,
Max.

Top! Thank you!
I had exactly the same issue and want to fix it this weekend. My I6 arrived on Thursday. Now I follow your instructions to update to Windows 10.

Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards

stalker2106 said:
Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards
Click to expand...
Click to collapse
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?

scharrrfi said:
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?
Click to expand...
Click to collapse
Alright, i don't know what ISO of windows 10 you have, but i found a tutorial on how to convert esd to WIM, so no worries (http://www.intowindows.com/how-to-easily-convert-install-esd-to-install-wim/) furthermore, i would recommend using PowerISO for extracting the file, as i'm not aware of how to extract from ISO with 7zip

Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.

scharrrfi said:
Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.
Click to expand...
Click to collapse
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side

stalker2106 said:
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side
Click to expand...
Click to collapse
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!

scharrrfi said:
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!
Click to expand...
Click to collapse
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.

stalker2106 said:
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.
Click to expand...
Click to collapse
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920293. I think it is an older one.

scharrrfi said:
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920290. I think it is an older one.
Click to expand...
Click to collapse
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?

stalker2106 said:
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?
Click to expand...
Click to collapse
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing

scharrrfi said:
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing
Click to expand...
Click to collapse
Thats some freaking bad news ...
I uploaded 204 BIOS to the drive... cheers, fingers crossed.

It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?

dahuzi said:
It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?
Click to expand...
Click to collapse
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.

stalker2106 said:
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.
Click to expand...
Click to collapse
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.

dahuzi said:
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.
Click to expand...
Click to collapse
Hi, bad manipulation yesterday led me to delete archive from drive, but its uploading again !
I tried again the tutorial because of the problem of " scharrrfi" to check if its not broken in any manner, and it worked flawlessly !
Furthermore, the system is yours, and therefore, is not activated by default, it asks for a serial key !
Files should be on the drive later today
EDIT: The files are up on the cloud !

Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...

scharrrfi said:
Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...
Click to expand...
Click to collapse
Yeah, I admit that was kind of my fault telling you that upgrading your bios would change anything in your boot configuration, i'm so sorry
Let's hope this will work, still hope, windows 10 will make its way to your tablet no worries !
After some days of using it i report some glitches though:
Orientation sometimes get rekt, i dont know why but you have to set it manually...
Also the tablet is not as responsive as it is on android, but I guess power consumption is higher on windows, as it heats much more !
Sometimes i touch the part near the lens and it feels really hot !
Btw when on low battery, the power saver settings got me doubling my battery time, which is nice !
And on idle, locked, the battery charge way faster than on android.

Hi I have an other error - if I boot with the bootia file I got short 4 error messages: UEFILINUX ERROR [uefi_get_battery_status:121] Failed to get battery status - und error 160, 121 again and 149, all error with the battery. I haved update the firmware from 201 to 206. The battery is over 90% full in windows. Have you an idea whats wrong?