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
Related
Hi,
My name is Joe aka AndroidSamurai.. I will be releasing more guides and media content in the weeks to come.
I'm currently very busy with "life events(new baby)" and apologize for my absence.
I will be updating this post since it was my original with a new guide updated to new SDK and Android methods.
Thanks again,
AndroidSamurai
Android4D Inc
<golf clap>
Well done.
</golf clap>
What do i do if the new hardware device notification doesnt pop-up ? NM i got it. Thanks for the writeup
@King_tee: Assuming windows, you follow the following steps.
1. Start > Control Panel > System.
2. Hardware > Device Manager
3. Click on the last icon below the File menu. It should correspond to "Scan for Hardware Changes."
If that doesn't work, try unplugging / replugging USB cable, different USB cable, restarting phone, restarting computer, etc.
If you never see the notification, navigate to the Device Manager(inside "System" in the control panel in XP and inside Device Manager on Vista).
You will see ADB Android Device at the top of the list with a Yellow Icon beside it meaning the device is not working. Right-click on the device and select "Update Driver".
Follow the dialogs that pop-up and navigate to where the unzipped drivers are at...
You should be good to go from there...
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
devildogg2001 said:
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
Click to expand...
Click to collapse
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
I dont know if thats the problem because when i plug it in, it doesnt show up as a notification, and when i go to the device manager it shows the little yellow triangle.. I'll look again. Thanks for the quick reply though. I am no expert in linux, but i have it installed, let me see if i can figure it out there..
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
devildogg2001 said:
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
Click to expand...
Click to collapse
Downloading
http://developer.android.com/sdk/1.1_r1/index.html
Installing
http://developer.android.com/sdk/1.1_r1/installing.html
Found through Google...imagine that.
as well as what xyrcncp said can you you can download it and just mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd you should be able to run the adb commands from any directory. not too hard to cd to the correct directory but i personally don't like to type cd ~/Phone/tools/android-sdk/tools every time cause i tend to make typographical errors. let me know how it worked but you shouldn't have any problems at all
umm no offense but your writing a tutorial for people that are not sure on how to do this, so you must assume that they do not know how to run an executable file...... write yourself a better tutorial without actually bashing the self esteem of some people... tutorials are positive not negative. I already know all of this but still... dont degrade someone due to the fact they dont know how, thats the whole point of writing your tutorial. Nothing should have been left out (including how to run a .exe .com or .bat
" (If you do not know how to install a windows executable file, please kill yourself now! ) "
this isnt honestly written with any hatred towards you, it was a good tutorial. Just might want to think about how you write it next time.
The "bashing" comments in my tutorial are directed towards the people with a true sense of humor. My tutorial was written to tell you how to simply complete a task and not to make you feel better about yourself. I do not get pleasure in abusing people's self esteem nor do I enjoy putting people down.
Just because you got a little sand in your crack does not mean you need to come in a very honest and informative thread and start bashing the people who are bending over backwards to help everyone out.
The reason I created this "tutorial" in the first place was because all the other threads are full of "start searching and stop asking so many damn questions" comments.
So start looking in the mirror when you wake up in the morning and stop saying "My, I think I will run over to good ole' XDA and be an @$$ to everyone today".
I am sincerely sorry that a little sense of humor has caused so much hatred in my thread. Please contact the forum moderators and see if the think my tutorial is so hateful.
lol i dont see any hatred but anyway when i download the adb driver when extracting it says unknown method
@ Nabzilla1990
Are you using Windows or Linux?
Are you using the built-in Zip tool or 7-zip from the links I provided?
Are you using a 32 or 64-bit OS?
using the same operating system as you 64bit vista ultimate sp1 and using winrar to extract
Try using 7-zip man, I have been using it for 3 yrs now.
Basically what I am saying is that everything in my guide is guaranteed to work.
Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt.
it worked with 7-zip thank you and also want to add if it doesnt work for some people plug in ur phone and update the usb mass storage with the usb driver from here and it should work i had that problem earlier
Okay, so I did everything and got up to run cmd, when I type in the cd C:\android-sdk-windows-1.1_r1\tools it says not a specififed folder, but when I type it without the \tools it doesnt work. can anyone help?
Anyone know what driver I need to mess with to get the 'adb' tool to connect to device (sprint mogul) via linux PC?
Setting up udev rules
kkruse said:
Anyone know what driver I need to mess with to get the 'adb' tool to connect to device (sprint mogul) via linux PC?
Click to expand...
Click to collapse
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.
boulderjams said:
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.
Click to expand...
Click to collapse
Since the Mogul is an HTC device it should be 0bb4.
Manufacturer-USB Vendor ID
Acer-0502
HTC-0bb4
Huawei-12d1
LG-1004
Motorola-22b8
Samsung-04e8
Sony Ericsson-0fce
boulderjams said:
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.
Click to expand...
Click to collapse
yea it is the issue really was something in centos and the kernel this time. I upgraded it to fedora core and it worked with the same adb bin.
kkruse said:
yea it is the issue really was something in centos and the kernel this time. I upgraded it to fedora core and it worked with the same adb bin.
Click to expand...
Click to collapse
I wrote up a post this afternoon on getting the SDK fully working on my blog...
I am using Ubuntu, but should be easy to translate to other distro's...
HERE
Hope this helps others out.
LG EVE adb access on ubuntu
I'm currently using an LG Eve(GW620R) and have had no luck getting adb to see the device on Ubuntu Karmic Koala. I used to have an HTC Magic, and adb would recognize the Magic without any issues whatsoever, but I cannot seem to get the Eve to play nicely. Adb is properly set up, since I had full access to my Magic when I had it. I've edited my rules file to add in support for LG devices, but it still won't pick it up. I've tried changing the rules file to 51-android.rules, and I've also tried 70-android.rules, but neither one seems to want to work. I've rebooted my system, reloaded udev, changed the rules file to read every kind of device, regardless of manufacturer, but I still have had zero luck. I thought that linux was supposed to require next to no effort to set up adb, but I've been trying for 3 days now, and I've still gotten no farther then when I started. If I run lsusb while the phone is plugged in normally, it sees it, but adb does not, if I put the phone into emergency mode or fastboot, it shows a different device ID, but even adding in those IDs to my rules file, I still get nowhere. Any suggestions?
still not working
alright, so I've tried editing the rules files in all kinds of ways, I've tried running adb as root, I've got debugging enabled on my phone, I've followed every instruction I've found to the t, and I still have had no luck getting this phone to connect to adb. Can anyone give me any advice, or at least point me in the right direction? I've read a bunch of stuff about different kernels having issues with different phones, but I can't see my kernel being the issue if I could get my HTC Magic to work just fine. I'm hitting brick walls at every turn, and I've had no luck getting it any further than two weeks ago now. I'm running 9.10, Karmic Koala, I've got the newest sdk (which I think might be the issue since the Eve runs 1.5, but doesn't the newest sdk include all the old drivers as well?), and I've tried changing the rules file to be a higher number then any other rules file in my /etc/udev. Any advice or information that anyone could provide would be incredibly helpful. I really want to get rid of all this Rogers crapware that I'm stuck with. I'm open to pretty well anything anyone can suggest, and I'm more than willing to provide any further information that anyone might want to try and help me work this out. Thanks in advance
Do not use these instructions anymore, Microsoft FINALLY fixed it, look here
....
HTC Driver Install Instructions
Go to Desktop, press Windows key + R, type in "shutdown.exe /r /o /f /t 00" and click OK.
Now click on Troubleshoot, then click Advanced Options then Start Up Settings.
Now click Restart. Let the PC restart and press either the number 7 or F7.
Download this and install it.
Wait for it to finish and then reboot and enjoy
Make sure you plug your phone into a USB 3.0 port EVERY Time when using Fastboot
....
If you have any problems with your USB 3.0 port afterwards and want to return it to original driver, follow these steps to return to your original driver
Press Windows key + R, type in "devmgmt.msc" and click OK.
Expand Universal Serial Bus Controllers.
The USB 3.0 port is listed as "AMD USB 3.0 Host Controller", double-click on it and select the Driver tab, click "Roll back driver" and select Yes.
Restart your computer
Thanks for sharing
Sent from my HTC One S using xda app-developers app
dd98 said:
Today I present to you a fix for fastboot on Windows 8.1 x64 on Intel and AMD machines with USB 3.0. This will NOT work on USB 2.0. This should work if you follow instructions exactly. I am not responsible if anything goes wrong and/or breaks. The Intel fix is NOT mine I'm just posting it here for convenience (Original Intel tutorial here)
All credits for the Intel solution go to the people here
Please hit the thanks button if it helped
Click to expand...
Click to collapse
im getting an error when extracting the amd fix zip
try 7zip or winrar to extract
dd98 said:
try 7zip or winrar to extract
Click to expand...
Click to collapse
Went nuclear and am installing Ubuntu as we speak... But as soon as it's done I'm going back to try this... I simply used whatever decompressor is in win explorer, even though I have both 7zip and winrar..... (Forehead smack) :silly:
i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA
dd98 said:
i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA
Click to expand...
Click to collapse
i truly appreciate you taking the time to do that for me.. truly!
however, since going to dualboot linux ive solved all those problems... have new ones now though
No radio, no firmware it seems... have a rom that boots but no way to connect..
Achieved S-OFF trying to fix it but no... nothing works... should i be using a sense rom?
thanks again!
you shouldnt need a sense rom, why dont you download amd fix.zip in ubuntu, extract it and move the files to your windows partition and then try to fix your usb then try running an ruu
try to fix adb on linux try this
1. Open terminal
2. type this: sudo gedit /etc/udev/rules.d/51-android.rules and hit enter
3. considering your phone is htc type in the following on the text editor window: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
4. save the file and restart your computer
or if this didnt work try this: http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
Morning gents,
Got my ONE yesterday and obviously trying to unlock when I hit this roadblock. I tried the intel fix above earlier this morning and last night. I was able to get the intel drivers to take, but lost all of my usb ports in the process and had to roll back. As soon as I accept the first intel driver for the eXtensible controller, all peripherals are dead. Am I missing the obvious here??
I've spent more time trying to get my old pc (with Win 7) up and going than trying to fight 8.1 into submission. Naturally the HDD on that unit is dead now. CURSES!
What is the forecast for a solution on this? Is it a windows update or just waiting for an HTC driver update?
Thanks for any guidance.
thanks a ton worked wonders :laugh:
Microsoft knows about this, but doesn't seem willing to provide a general fix. Ultimately the problem is that Microsoft added an extra validation to device registration that HTC devices don't seem to honor. They're releasing an update to fix particular devices, but we don't yet know if end users will be able to edit the white list.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Sent from my One S using xda app-developers app
I have windows 8 32 bit. I would like to know if i will have problem when i will update windows to 8.1 32 bit. My computer have only usb2.0 ports
The problem exist only with usb3.0 port or i wil have it also with 2.0?
thanks
The problem exists with USB 2.0 ports as well. The reason that the "fix" posted works for USB 3.0 ports is because it uses Intel's USB 3.0 drivers for Windows 8 to work around the problem. There's also "fixes" floating around that involve rolling back to Microsoft's Windows 8 USB drivers to make it work.
If you don't have another PC that you can use to do things in fastboot, stick with Windows 8 until a proper fix is available.
Thanks... Finally I can Fastboot on Win 8.1... :good:
I can't install the driver update...getting an error that states "The system cannot find the file specified".
are you sure you read the note at the start and followed the instructions EXACTLY
dd98 said:
are you sure you read the note at the start and followed the instructions EXACTLY
Click to expand...
Click to collapse
The only thing I did any differently was to download the files before the reboot. I can't imagine that makes a difference but please correct me if I'm wrong. I validated all aspects of the initial note, still no luck. Again, I'm trying the AMD fix.
Likeachampion3 said:
I can't install the driver update...getting an error that states "The system cannot find the file specified".
Click to expand...
Click to collapse
Same problem here
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?
Read carefully, this is about the installation of Windows 10 ARM32 on the Surface RT1. Previously tried the Elektrohax tutorial (video on youtube and also posted at Alexenferman.com) but I was unlucky on my attempts.
This is the mentioned tutorial:
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
I followed the instructions but failed twice. Now I know what was wrong. The tutorial IS FINE, it works. The thing is you have to first apply a patched version of Windows RT8.1 and run some scripts, that was fine, now the specifics:
Don't "RUN" the scripts, do not double click, this was the issue on my side. It doesn't matter if you run the script as "Administrator", I repeat, in my case this was the problem, DO NOT RUN or just double click.
INSTEAD, open a CMD window elevated to Administrator privileges. Move to the location of the scripts, this means get into the specific folder, only then run the script.
This means, if you placed the script on a folder named "whatever", right clicking with administrator rights and then execute does-NOT have the same effect as getting inside the folder as in "CD\whatever" and then "name-of-the-script".
I tried several times and I can confirm this is the thing that failed on my attempts.
- - - - - - - - - - - - -
Being that said, that website has all the instructions and links. Follow the tutorial carefully step by step. Keep the files on a safe place, who knows how long those will be kept on the web.
After my failed attempts I tried the chinese tutorial posted on Youtube by cong cheng on his channel. It worked, it even has some scripts working as installer, yes it works BUT after taking a deep look it's a method that applies a set of files made for some Nokia device, while it works, it is in chinese, has some broken things and it is SLOWER than Alexen Ferman method.
In short:
- Chinese - applies an already customized W10 version, way slower
- Alexen - it is an installer, you end up with a much better version
Good luck.
So what did you follow? The forums here seem to contain loads of broken links. Love to try W10 on my Surface since it's only collecting dust in my closet.
Thread edited and updated above and below.
Regarding Windows 10 on the Surface RT (CHINESE TUTORIAL)
I have no idea what's the risk on using a chinese modified pack. This one is different to the one at Alexen Ferman website, here I didn't need to apply all those patches (extras, after finishing the install), instead it worked out of the box. It's the same release as far as I know, but it's been customized.
My experience, what works:
o Edge works, better than IE11
o MyTube works (Youtube works amazingly well on this APP)
o System not as fast as W8.1
o I just clicked "Activate Windows" the usual way and it worked
o Cameras work out of the box (front and rear), no patches needed
o Can run ported apps (Paint.net, Halite, etc).
o YES, you gain access to some other apps on the STORE but hey, read below
X Office was in chinese (preinstalled) and slower, couldn't change it
X Removed it and installed the Office package provided by Alex Ferman
¬ After reinstalling, Office now is FASTER (tested and confirmed)
X No alternative browsers (just some but it's just IE with skin)
X Was kind of tricky to remove chinese (there are still some traces)
X Store doesn't fully work, just allows installing whatever is in my library (owned)
X VLC is way slower and ugly, worked way better on W8.1RT
- XX The Brightness control is kinda broken. You have to disable automatic changes and use only manual (via button), only there you can apply diff real levels of brightness to the screen, BUT, it won't work forever, after a while it will get stuck and you would have to reboot and set it right after going to the desktop.
- XX I'm still exploring this, I don't fully like it to be honest. The touch keyboard works, yes but in my case at times stops making sounds, and also stops working. Unplug and plug again fixes this but... meh.
It wasn't that great, I was actually considering going back to Windows 8.1 RT.
Now the final install I have (Alexen method):
Everything works, you just have to follow the tutorial and you will actually install W10, it's not an out of the box ready image, it is an installer. The only broken thing so far is the brightness control as explained above (it's an issue with the release so it won't go away), and the store didn't work for me, but there is an alternate method to install apps described at Alexen website.
Other than that EVERYTHING is better, it's fast, decent. I'm keeping my RT1 with Windows 10.
Read carefully, follow each step and don't give up. That's all I can say.
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Has anyone written a guide on how to go back to windows rt 8.1?
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
does anyone knows if it is possible to put google chrome book on W RT?
Haven't visited the thread until today.
xnappo said:
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
Click to expand...
Click to collapse
Great that you got it working, now that you mention that you don't have any need for the Surface anymore, consider selling it to one of the member of the team working on modifications, unless you change your mind now that your surface works differently. In case you decide to move on, consider posting here on the Discord community
Join the Open RT Discord Server!
Check out the Open RT community on Discord - hang out with 5,903 other members and enjoy free voice and text chat.
discord.gg
mickeyx323 said:
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Click to expand...
Click to collapse
I simply downloaded the package and ran the Office Installer on the Surface (now with Windows 10ARM), your comment makes me think perhaps, you don't actually have a Surface with Tegra processor, please check. .7z? search for 7zip, that's the program to extract the files from the compressed package .7z
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
Yup, the link was posted by another forum member above.
bikrtoursportugal said:
does anyone knows if it is possible to put google chrome book on W RT?
Click to expand...
Click to collapse
Nope, impossible. They didn't create a binary (executable app) for the platform and the way it's built (the source code) seems unlikely for someone else to do it.
Anyone interested please check the Discord link posted on this message.
ricky4695 said:
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
Click to expand...
Click to collapse
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Kolyei said:
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Click to expand...
Click to collapse
You should repart the drive using the official image downloaded from microsoft's site. If you want to come back to completely stock you have to re-install windows using the standard procedure, not the installation through wim file
im having an issue at the installing the wim using the dism. says system cant find the path specified. i verified the drive labels and all any ideas?
can some help me, after successful installed and load windows 10 on surface RT... when i want to run CMD as administrator. it gave an error "The Parameter is invalid".
Looking for some help, I got to the Win10 install stage and keep getting 0xc000000f blue screen error on Win10 boot. From the guide, it says I didn't choose to not copy system files when creating my recovery drive, but I didn't have any other options. I unchecked the only box available. Not sure what is wrong or how to fix. I can't reset, it asks me for my recovery drive, it doesn't accept the drive I created.
Edit: I ended up creating a new recovery drive from my Win10 PC, unchecked the box to copy system files, downloaded the Win RT recovery zip file from MS, copied the contents of that folder into the new recovery drive, copied the Win10 .wim from Alexen to the flash drive, and retried step 4 (I had already installed the hacked RT image and disabled secureboot, etc.). It is now booting, at least getting farther than it did before, after flashing the Win10 image.
Running into an issue right after the installing the patched image I get to the Region and Language select after the reboot and cannot select anything. After a bit the display just goes black. What can I do?