Related
I'm sorry for being so loud, but I've seen a few "progress pages" in Wikis and I still can't get a clear picture of who (if anyone) is actually working on linux for the HTC Magician (Qtek s100, iMate Jam, Dopod xxx, etc.).
I found this project:
http://userpage.fu-berlin.de/~zabel/magician/README
and it appears to be very very promising; it already delivers some small functionality on the magician (I've tried it). But there is much much work to do before it can be released to the general public.
In general, I don't think there are many people working to get the Magician on Linux...
So I am asking here: are you working on this? do you know who is working on this?
I am a SW developer by trade, but I have no time at home to code.
However, I would like to give whatever little time I can find to:
- act as a beta tester;
- develop one or two patches (kernel mostly);
so we can get Linux running on the Magician.
Thank you.
Hi,
This doese indeed look promising.
I have no qualifications in software etc, but i do like fiddling with linux -).
I too would be a beta tester.
So is anyone working on this?
Hi. As vnevoa found out, I am working on the Magician when I find the time.
Unfortunately, to my knowledge, there is no-one else currently working on this. So developers are needed!
For people interested in kernel hacking, there is the [email protected] mailing list and the #htc-linux IRC channel on freenode.net
The biggest missing parts currently are battery control, sound and the phone.
For everyone else, any improvements to the Magician wiki pages would be more than welcome. To build a proper userspace image for the Magician, support for this machine in OpenEmbedded has to be improved.
Wow!
That haret thingy is wonderfull.
What is the current state of the version for the Magician? Does it boot to GPE?
This is a great thing, really. No need to flash a new firmware, and boot linux! Amazing. I'm using Linux on ipaq and it is very nice. But I would miss phone operation. With haret we can have both things running.
Good work. Has anyone tested USB host on magician under linux?
futaris said:
Good work. Has anyone tested USB host on magician under linux?
Click to expand...
Click to collapse
USB host works, but it is not connected to the usb plug.
The bluetooth chipset is a CSR usb chip.
pH5 said:
USB host works, but it is not connected to the usb plug.
Click to expand...
Click to collapse
does that mean, usbnet is not possible? in my case, nothing happens if i connect the magician to my computer. dmesg and lsusb say nothing about a new device. insmodding usbnet doesnt help either. tried the same with a htc universal, usbnet works fine on my machine.
[edit]works for now, if connected via external-powered usb-hub. maybe a driver problem? activesync in windows-mobile is possible without using the hub.[/edit]
And if you check the website you can see all teh file you need to download if anyone know a programm for make call/sms/mms or ONLY calls and run on this linux please give information about
ok i try this one in a few and i edit my post when i have test all
ok today the : 28.12.2006
mmmm i have some trouble with extracting the gpe archive it's seem to be corrupted soooo bad.
BUT the first problem it's this famous default.txt the script to run haret if anyone have a working script please copy information here of the .txt file that's can be helpfull.
the error of my default.txt is: Failed to load kernel \carte de stockage\zimage
must i need to rename the zimage file???
and i have a question ... it's possible to make a "bootable" SD? if yes i can try to run another handled linux perhaps???
OK i have found i must rename the magician-zimage-2.6.XXXX to : "zimage"
so i have downlaod latest version of haret and take the default.txt WITHOUT changing
harte start but of course i haven't the gpe file so it's say error BUT it's launch now i must really found a good archive i have try under linux but the archive still in read only i can't change it to read AND write so all i uncompress are still not working under linux it's better on windows don't know why .....
(mmm risk to brick my magician if i try another gpe file .......)
and of course: sorry for my bad english
now i edit the post when i have MORE important news
HUGE BREAKING NEWS!!! THIS JUST IN:
May 12th, 2008
ENTER "FrankenKaiser"
For the past several weeks, I've been working with Jocky on unbricking devices with nuked SPL's as a result of task 2a MTTY commands. Last week the amazing Jocky found a way to exploit OEMSBL & to Security Unlock a BRICKED device via dload mode. That's right, you heard correctly, Jocky Security Unlocked a bricked device, giving me access to all of the OEMSBL, Radio Boot Loader commands!!!
Subsequently, Jocky has written a tool that will then use this exploit to load a new SPL via Dload mode into ram & do some device initialization. After three chalenging & frustrating weeks, we were able to load a SPL into ram, get the spl to stick & voila.....I now have the first ever Kaiser recovered from being a nuked SPL brick!!!!
I won't give to many details, as this is really Jocky's baby & it's his place to share the information as he sees fit, but I'll tell you that this tool may be the start of something huge! It will allow you to test SPL versions & recover from bad SPL flashes. I believe this tool is also going to be the center of fixing the locked AT&T radio's.
I can take no credit for this tool, I was really nothing more than a brave & willing guinea pig, that occasionally floated theories, & remembered some of the little stuff.
Jocky did let me name the tool, based on the first thing I thought & said when we were talking about the theory behind the tool, which was "Oh my God, It's alive, it's aliiiiive!!!!", so the tool has been named FrankenKaiser!
If you have a Bricked Kaiser, Let me know, post it here in this thread until Jocky start a thread specifically related to this new tool. Please don't overwhelm Jocky with requests & PM's, as the tool must be moddified for each & every different OEMSBL version. If you have a task 2a or other bricked Kaiser, please PM me or post the info here on this thread & depending on the type of brick you have, someone will let you know if this tool can help you.
Okay, it's true I've put my Tilt thru hell & back trying to help out the noobie. I have done partial flashes, radio & rom, to recreate their problems in an effort to guide them thru the solutions.
I've alway been able to recover......Until now!
A WARNING TO ALL USERS FROM OTHER DEVICES NEWLY COMING TO THE KAISER!!!
After countless trips to hell & back for my device, it finally, It is totally dead. After doing a few MTTY task & info calls while assisting a noobie I decided to format my device & the nand storage to start afresh. Now I am stuck in OEMSBL.
Should you try and format or dump bad blocks as previously possible on some older devices using the task 2a command. There are several thing you need to know. Firstly, you'll need to immediately flash a new SPL BEFORE soft resetting. Otherwise, your device will not boot period. You will find that the service LED light stays green like it is fully powered, & the "GREEN" light will come on whenever you hit the power button, but when you plug it into the USB port on your PC, it will only be seen as new hardware & will add the following new devices: a NMEA GPS Device, a Qualcomm Data Device, an Qualcomm Diagnostic Interface, a Baseline Modem, Baseline Storage Device, etc. But A/S will not run & MTTY cannot communicate using standard commands nor can it be used thru the USB port.
The reason this happens is becauser you have just completely formatted the NAND, essentialy killing the Boot Loader or SPL.
As of this time, there is no known recovery for this type of brick. Several people are working towards a fix, but unless your device is security unlocked, there will be no miraculous recovery.
ALWAYS EXCERSIZE EXTREME CAUTION WHEN COMMUNICATING THRU MTTY WITH SPL OR WITH OEMSBL. DO NOT ASSUME THAT THE SPL COMMANDS ARE STATIC> THEY CAN & DO CHANGE BETWEEN DIFFERENT SPL VERSIONS & DEVICES.
As an example, Tilt Devices with the 1.56SPL can execute the boot command, whilee HTC 1.93SPL devices cannot & require a task 8 to reset.
If you do not know what SPL is, or have no idea the available commands & their effects, do not use them.
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Laurentius26 said:
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Click to expand...
Click to collapse
Laurentius is right; it would surprise me if the Flash from SD-card would not work for you!
Good luck,
Edward
sorry to say that but it is a true brick now, it is recognized by windows because there it falls back to qualcomm diagnostic mode (which will not help you at all) I had exactly the same situation and you won't be able to flash it, send it to htc for repair
No, The screen will not turn on & when plugged in it now acts as accessories or hardware for my PC.
The chipset inside the device is still getting power, & it is a chipset that is powerful & used for many, many things. So, it's no suprise that it sees the modem, the Basecom Interactive, Basecom NMEA device, etc...What it doesn't see is all of it integrated into a package & it actually creates 6 or 7 port connections thru XP Hardware Wizard for each "accessory".
What I believe has happened is that the unit has been completely formatted meaning the actual Windows CE has been destroyed, formatted, removed, kaput...
The only way to revive I think would be to reload CE into the device the way Mfg's & OEM's do.
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Da_G said:
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Click to expand...
Click to collapse
nope, there is now way to do that
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
GSLEON3 said:
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
Click to expand...
Click to collapse
sorry, that's a misunderstanding my post was referring to the use of pst software/mtty and usb connection, and I reckon that it's cruel to give the man hope, though you can always buy yourself a piece of software built based on jtag, special serial connector and a book how to to that but given the sources you mentioned I reckon you haven't read much about the problem yet, my kaiser is about two be back from service this week and if there was no breakthrough on the internet about that with last 2 weeks then there is no know way how to talk to qualcomm diagnostic software directly using usb.
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
_Alex_ said:
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
Click to expand...
Click to collapse
yes Alex, also SPL (which is the real problem here), and you can't use pdocwrite unless you could actually talk to the device which in qualcomm diagnostic mode you can't with this software as it will not accept any commands other than specific to that mode, I have flashed windows mobile device for about 4 years now and that's actually the first time I ended up with a real brick but of course htc can easily fix it (they did it in 1 day, most likely in less than 30 minutes) but they have equipment to do that which I don't and only few users on xda have that kind of equipment, to get more info about it you could look in the search for task 2a there were bricks like this before us
Alex,
Yes CE, Radio, SPL, OS... All see to be completely wiped with the task 2a command. I don't think pdocwrite will work as its still needs a medium to connect to my device. That medium is what I have yet to find. The first step would be to somehow restore boot loader. I am currently trying to see if I csan use qpst to push linux to the device. I haev found some CE restore utilities for reverting from linux, but first I need to be able to at least boot to SPL or another Bootloader.
Whats about Windows CE and KITL Mode?
The device stays in OEMSBL. If you use the MotorolaQ drivers, you will be able to connect to the right COM port and issue radio bootloader commands. You will probably be able to unbrick it depending on what problem it has. First try the easy one:
* Execute "setboot 0" and "cego" commands.
If this does not work, then probably your SPL has been erased in NAND, you can check that by dumping radio memory address 0 right after executing "cego" command. (commands: "cego" and "mb 0 40000").
If it's all 0xFF then your SPL has been erased. Here's how to fix that:
1) Issue command 'setboot 1' (with the default 0, the application ARM is hang because it tries to execute 0xFF), this way it keeps the SPL in memory after reset.
2) Copy a full SPL at address 0 by issuing 256K times 'mb <address> 1 <byte>' (i've written a small app that does this for you...)
3) Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader, in my case (OEMSBL version 1.27.12) the patch was 'mw 901708 1 0000a0e1' you'll have to figure it out yourself if you have a different OEMSBL version.
4) execute 'cego' and see the bootloader 3color screen appear again (keep the bootloader keys pressed if you have not used a patched SPL in step 2)
5) Flash HardSPL.
6) Connect to OEMSBL again and execute "setboot 0".
7) See the device booting OS
Thanks pof!
setboot 0 returns ARM9BootMode:0, so it is communicating. However, I get invalid command errors with the cego & mb commands. You think there is a way to flash an spl.nbh using OEMSBL thru pnewbootloader? I believe you're right on the money & from what I've learned playing around today is that the task 2a command indeed formats the NAND. So bye bye bootloader. I think it's now just a matter of finding a way to flash spl back. That said however, I can figure things out given a lot of time, but I'm definitely nowhere near a bright bulb on the XDA X-mas tree, so to speak. So you'll have to forgive me if the meaning of "Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader" escapes me.
Thanks again!
When I used to work @ symbol we used to interface with our devices directly in IPL mode using hyperterminal (included in windows). I wonder if you could accomplish something like that?
From there we used to use IPL commands (I dont remember them because this was a long time ago)
GSLEON3 said:
Thanks Oli!
However, I get invalid command errors with the cego & mb commands. Also, where can I find the spl patch app you've written? I searched high & low.
Thanks again!
Click to expand...
Click to collapse
I think POF is talking about JumpSPL correct? I am surprised it didn't work after what POF recommended his right on 99% of the time!
I believe s right. I just think the cego command isn't correct for my device. I think maybe this command has changed just as spl commands can change between versions. The mb command also returns an invalid argument.
But it's definitely down the right path.
GSLEON3
I really wish I could help you out man. You have done alot on this forum for alot of people. Unfortunately I'm about as lost in here as a hooker in a pecker patch. Sorry bro, wish I could help.
pof's method only works if your device is security unlocked
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?
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?
It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
FantasyCookie17 said:
It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
Click to expand...
Click to collapse
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
abprie said:
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
Click to expand...
Click to collapse
The first links seems to be basically the same as what I found. The last one only works if the bootloader is still there, which is not the case. That's also the reason why I think, while not actually had looked into them, that it's not just adb and fastboot commands (those won't work anymore with my device). ADB only works in Android, and fastboot only in the bootloader. But yes, I'll look into it and see if I can do anything.
So, after looking into it, I noticed I basically understand even less of that script than I do understand Unix shells. I guess I'll probably ask in that thread however, as this seems to be the original developer of the script(s). (actually, there's several scripts, XMLs and so on there)
I had a quick look at the update_image_EDL.bat file and noticed that the file itself calls an executable in Windows format. I guess this won't be easy to convert.
But did you try to run this in wine?
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
aleksander002 said:
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
Click to expand...
Click to collapse
This would require the OP to own a win10 version and if that was the case, (s)he could also boot from a installation disk and run the scripts on a live boot. But still, maybe a true Windows version is required.
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
aleksander002 said:
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
Click to expand...
Click to collapse
True, might work...
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
FantasyCookie17 said:
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
Click to expand...
Click to collapse
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
abprie said:
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
Click to expand...
Click to collapse
Afaik Dragonboard is just the name of that line of SBCs which also uses Qualcomm SoCs. So while the Zenfone very likely doesn't use a Dragonboard as PCB, the SoC modes and such should be similar. The device-specific instructions most likely won't work, however the software should work on all Qualcomm-based boards.
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
FantasyCookie17 said:
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
Click to expand...
Click to collapse
Meaning that even the Windows scripts that reflash the bootloader did not work?
Interesting. Looks like the issue was the cable; it worked with a different one (though both cables had both data and power lanes).
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Marlin79 said:
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Click to expand...
Click to collapse
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
FantasyCookie17 said:
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
Click to expand...
Click to collapse
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Marlin79 said:
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Click to expand...
Click to collapse
Yes. Happened to me, too. The problem was that the phone is not recognized as a Qualcomm device in Windows. I had to open it and bridge two points on the board. See this: https://forum.xda-developers.com/showpost.php?p=82965385&postcount=66
I finally got to the stage where i could execute update_image_EDL.bat script
It ran for a minute or so but then terminated in an error.
Code:
13: E:\firmware\prog_firehose_ddr.elf
06:28:01: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
06:28:01: ERROR: function: sahara_main:983 Sahara protocol error
06:28:01: ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'QMSL_MSVC10R.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at QC.QMSLPhone.Phone.QLIB_DisconnectAllServers()
at QC.QMSLPhone.Phone.DisconnectAllServers()
at QC.QMSLPhone.Phone.Finalize()
2020-07-11 06:28:02.931 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
press any key to continue . . .
Any ideas what that is about? The file it mentions QMSL_MSVC10R.dll does exist in the firmware directory