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
Well here I have a wonderful problem, I have two devices, according to the working one and cpu z:
4x ARM cortex A9 @1.42 ghz
revision r3p0
Rockchip RK3066
Model rk3188
Manufacturer Zowee
Android version 4.4.2
bootloader unknown
java vm Dalvik 1.6.0
kernel 3.0.36+ (eng.candy.20150403.110733)
The device that has the problem is the exact same model and all, however, after plugging it to the AC current, it tries to boot up but enters into recovery mode, none of the options work at all, looking into youtube I found out that I can extract the firmware, so far so good, but, I can't use that method because RKROMDUMPER and RKAndroid_v1.29 need the tablet to be plugged and there is the problem, the faulty tablet does not load in that mode while plugged to the computer.
So I was left with the option of getting into recovery mode and attempt to update from external storage, so far the only "Firmware" or "ROM" I've got is the one I extracted from the working tablet, I have, backup.img, boot.img, kernel.img and so on, the biggest one is the system.img which is near 6GB size.
I really don't know how to proceed from this point, do I have anything usable with those .img files? I have tried downloading a 4.4 Android rom, the recovery tried to load the files contained in the zip folder yet the loader showed messages such as, bad footer, or invalid image or always a denial message of whatever sort you may imagine.
So, I am stuck, reading further more I discovered that there are other methods or even other roms that can be loaded, but the Zowee guys have near to nothing to work with.
Could you please help me with this? Are the .img parts usable or in some way "joinable" like merge them into a single file or directory?
The device was not rooted, so I am left with only the chance of fresh installing from sd card and nothing else.
Thanks in advance.
Hello and thank you for using XDA Assist,
please create an account and post here:
Android Q&A, Help & Troubleshooting
The experts there will be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist
Many have faced this problem while using a new phone (Lollipop, Marshmallow and later) with MTKDroid Tools.
Here is the issue - MTKDROID ships with an older version of ADB. (The program hasn't been updated for a few years but it still works.)
This ADB cannot recognize the newer phones. So the obvious solution is to replace the older adb.exe from the 'adb' folder of MTKDroid Tools. But MTKDroid recognizes this and refuses to start, showing us the 'It is impossible to start ADB' error.
I have made a workaround which starts MTKDroid with the older adb and immediately when it finds everything to be OK, replaces it with a newer one. It worked for me. So I hope it will for you too.
Download the zip in attachment.
Instructions.
Goto your MTKDroid/adb folder and delete everything in it.
Open the zip file you have downloaded with winrar or 7zip or anything.
Inside the zip file, there will be 8 files. Copy all these files to the adb folder.
Now you can double click StartMTKDROIDTOOLS.bat and press enter to start MTKDroid Tools. A few black console windows will come and ask you to wait 10 seconds (this is to make sure MTKDroid is loaded completely), wait and don't worry it will close itself when the work is done.
There you go problem fixed and MTKDroid is ready for your command!
NOTE: This fix will help you to start MTKDroidTools and use it to create a scatter file for flashing and backup purposes with SPFlash tool. From what I learned, you can't use this to root your phone unless you enable the temporary root shell from Engineering Mode.
To do that, open your phone dialer, dial *#*#3646633#*#* .
Swipe left to reach Log and Debugging section, there select user2root, in it enable root shell and now connect your phone using the above method.
This method is not guaranteed to work on every phones out there and I still recommend flashing SuperSU the old fashioned way.
Please reply back with any of your troubles or suggestions.
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
pig_slay said:
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
Click to expand...
Click to collapse
I hope it lives.. :fingers-crossed:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
DMcRitchie said:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
Click to expand...
Click to collapse
You're welcome.
I have included the changes you suggested.
Also I found this on stackoverflow which might help on w32.mal.heur detections.
W32 is the platform: Windows 32
Malware is the Category
Heur (Heuristic) might refer to what usually is the family or might be some specific naming of your AV
The heuristic term usually refers to detections based on generic signatures which look suspicious.
That detection looks very generic and might be a false positive.
Click to expand...
Click to collapse
Since the nature of the tool is indeed a hack itself your AV might be showing a false positive.
Still it's all up to you to decide.
All the very best.
Post updated.
Added a 2 sec delay to call MTKDroidTools. (Thanks @DMcRitchie)
Added a guide on rooting.
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Edit: Fixed it. I had to turn off then back on UBS Debugging, simply revoking the USB did not work. It's seeing my device now but says it can't root my device and sends me to an html page with lots more instructions. The tool tells me my device can be rooted this way. https://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 Grrr.. time to spend days jumping through more hoops.
Divergent Droid said:
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
So this didn't fix it, just made it worse. Is there another way to fix? I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Click to expand...
Click to collapse
This was supposed to fix the 'impossible to start error'. You shouldn't have used it if you were not facing that issue.
Don't worry you can just redownload MTK Droid Tools to fix that.
As for rooting, MTK Droid Tools CAN NOT ROOT phones newer than kitkat. Your best bet is to flash a custom recovery and flashing super su.
This guide is for those people who can't use SP Flash Tools because they need a scatter file which MTK Droid Tools can't make for newer androids.
All the best.
Thanks.
You gave me the most detailed answer so far. I got the info to use MTK Droid Tools from a website claiming it will work for Android 6.0 Marshmallow. That's why I tried it. If you are very knowledgeable about rooting in general, perhaps you'll answer my other thread asking someone to help me understand these things better. it seems according to you, i would be able to flash a new rom and SuperSU? See my other post and answer there. https://forum.xda-developers.com/general/help/guru-to-discuss-rooting-t3683594 - I did try the folks at the SuperSU sub forum and they cant help me.
When i connect Infinix Note 4 Pro X571 (bricked) to pc for Mtk to detect, it just boots to recovery mode (twrp)
tried using Maui Meta, it automatically installed vcom drivers then it said "it cannot find Kernal USB comport for AP and Modem handshake. Please check the usb driver version or find the driver owner to check"
thank you so much!! it works
I Get This Only :/ What's wrong? Noob Mistake?
qounik said:
I Get This Only :/ What's wrong? Noob Mistake?
Click to expand...
Click to collapse
I have the same issue. I just want to backup some stuff.
EDIT: this worked for me https://forum.xda-developers.com/showpost.php?p=75722412&postcount=14
Hi
Great fix but I still have a problem, I only have the hardware and baseband detected nothing else, so I can not save.
An idea ?
Thanks
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