Related
This is my first modern Windows Mobile (I used Windows Mobile 11 years a go) and it seems Microsoft was crippled the operating system.
Model: Bush Eluma, Windows 10 native (rebranded Archos 50 Cesium)
Specification:
Snapdragon 210
Adreno 304
1 GB RAM
16GB ROM
MicroSD support up to 128GB
5" 720x1280 IPS screen
4G LTE
WIFI/Bluetooth/GPS
8MP rear/2MP front with flash
2100mAh battery
Spec. Sheet: archos [dot] com/corporate/press/press_releases/EN_ARCHOS_50Cesium_50eHelium.pdf
What I'm trying to do: Interop-unlock
What I've managed to do: Deploy apps, such as Root Tool and vcREG
Where I'm stuck: Setting the value for my model of phone - I have no idea where to look
I hope I've provided information in a clear format. I'd very much appreciate some help or feedback in order to interop-unlock this model
System\Platform\DeviceTargetingInfo
PhoneManufacturer
Value = "True" (I think this used to just say "ARCHOS")
Thank you for reading.
Was there any progress made with this? Looking to interop unlock phone too so any help would be great
you tried this?
https://forum.xda-developers.com/windows-10-mobile/acer-liquid-jade-primo-upgrade-to-au-cu-t3589156
Worked a treat! Thanks a lot.
user154 said:
Sorry to kinda hijack this thread, but I have this device and struggling to find any other owners. My understanding is that the archos 50 cesium is the windows version of the 50e helium. I have an emmc dump of the 50e helium, if you cant already tell where im going with this, I want to flash this dump to my eluma b2 but cant get qfil or thor2 to do this. Can anyone help? or even know if this is possible?
Click to expand...
Click to collapse
I say just enjoy the W10 phone while you can, or if you really want Android, go buy that model online some where.
It is not as simple as it sounds. You would need at least a flash programmer for the SoC in that phone which usually the manufacturers never release. Depending on the format of the dump you might need other flashers or files to understand how the Archos 50 eMMC is structured or to utilize them in the flashing process. You would also want to be able to put the phone into EDL mode. If you can manage to even boot the flash programmer and initialize a flash of the phone there is also high risk of bricking it. Because you would be flashing partitions that were not signed for that phone/SoC. So I am not sure if you would also need to unlock the boot loader on it or not...sounds like you would. IMO it would be best to unlock the bootloader so you can backup the current layout of the phone. This as far as I know is not possible, so I would just stop there.
I know there are some threads in other forums where they are trying to do this with the IDOL 4s, and maybe a couple devices in the past have worked out to be able to do this. However it pretty much hinges on unlocking the boot loader. Also from what I know once you flash it like that and even if device survives (it boots, the IMEI is in tact, etc.) you cannot revert it back or it is pretty much impossible to go back without bricking it.
user154 said:
It doesnt really matter if the device is rendered unusable, it is quite a long way down the list of backup devices I have, it was more for the fun of trying to do it. The device is the exact same as its android counterpart (hardware wise) this is what made me think it should theoretically be possible. The dump I have was made with infinitybox, I have managed to create the required rawprogram.xml and patch.xml from the gpt binary contained within the dump. I have also found a couple of flash programmers for the soc (prog_emmc_firehose_8909.mbn, and a couple of manufacturer specific ones, pretty sure iv got the filename slightly wrong there). I have been able to boot the device to EDL mode using a cable, however sahara fails to load the flash programmer to the device. I didnt think the bootloader would need to be unlocked to flash the device seeing as the device is in EDL mode and what Im trying to flash is signed as is just the dump from the android counterpart. Maybe this is where im going wrong. Also Im working on the assumption the IMEI will be wiped as I plan to flash persist.img from dump too, I thought trying to keep the partition where it is stored in windows 10 and repartition the rest of the emmc to the same as the android counterpart might make things more complicated than they already are. Also IMEI can sometimes be quite simple to repair on certain devices (A lot more simple than what Im trying to acheieve here anyway). Can you point me in the right direction as to where I can find instructions to unlock the bootloader of this device? for some reason it doesnt get recognised by wpinternals (In any mode, EDL, standard flash mode, no idea what thats called on windows haha, or booted normally)
Click to expand...
Click to collapse
Sounds like you're on the right path. I'm not 100% sure you need to unlock the boot loader, however it would definitely make things easier as you could dump partitions from the phone as it is and even possibly enable mass storage mode. I am unsure where you would look to unlock that phones boot loader other than here. The flash programmers you have may not be built for the Windows Phone eMMC and why they are not booting.
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
JoachimP said:
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
Click to expand...
Click to collapse
If you have qpst/qfil installed on your PC, and have used them recently. The services might still be running. Just hunt for them in task manager and kill them and run thor2 again. See if that helps.
Worked a treat! Much obliged.
@nate0
Hi, thanks for your reply. I am nearly sure, I uninstalled QFIL and shutdown my pc after use, but I will check on it.
So I uninstalled QFIL and rebooted. This is the result:
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode list_connections
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode list_connections
Process started Wed Nov 14 08:48:16 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084816_ThreadId-4796.log
Debugging enabled for listconnections
WinUSB in use.
Connection list START
0.1A07:0004:0004 {71de994d-8b7c-43db-a27e-2ae7cd579a0c} Emergency mode connected
Connection list END
Exited with success
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
Process started Wed Nov 14 08:48:52 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084852_ThreadId-7500.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Message send failed with error code -1
Waiting connection to DLOAD: 2 of 2
Check if device in Dload
Message send failed with error code -1
Failed to connect to DLOAD mode
Make sure that the COM port is free. Close QPST.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 8.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED
THOR2 1.8.2.18 exited with error code 85030 (0x14C26)
Any suggestions?
I'm grateful for any ideas at this point. The model no. is 4037R, the provider ID is: 4037R-2BVHCA1 (n.b. The Alcatel OneTouch Pop D3 is very similar if not same as the "Evolve 2" model).
Using SP Flash Tool I tried "Firmware Upgrade" as an option when I was having errors. But I had no preloader file to flash, note. Even though all options were checked, I only had the recovery.img file to flash. I think this bricking may have occurred because I flashed the wrong MT65xx MediaTek scatter file. The one that came with the files, MT6572, wouldn't work ending with a "BROM" error 1003. It said the chip was an MT6582. So I flashed a generic MT6582 scatter file. That finally gave me the "OK", but of course it wasn't OK. The phone is no longer recognized by adb, and just barely recognized by the PC.
Problem is, I'm not exactly sure what MediaTek chipset this phone has, and where to get the scatter file for it, and more importantly, where to get the firmware for it (which should contain the scatter file, if I'm not mistaken). Apparently, you can definitely unbrick these types of phones if you have the right scatter file! Needless to say, I did not make backups of anything!
I don't claim to be an expert but maybe I can be of assistance. Sounds like you might have flashed a wrong preloader or something. If the computer still reads it then you still have hopes of flashing the right one if you can get your hands on it. If you can provide a picture showing your model number/ provider ID, I might be able to assist you.
I'm grateful for any ideas at this point. The model no. is 4037R, the provider ID is: 4037R-2BVHCA1 (n.b. The Alcatel OneTouch Pop D3 is very similar if not same as the "Evolve 2" model).
Using SP Flash Tool I tried "Firmware Upgrade" as an option when I was having errors. But I had no preloader file to flash, note. Even though all options were checked, I only had the recovery.img file to flash. I think this bricking may have occurred because I flashed the wrong MT65xx MediaTek scatter file. The one that came with the files, MT6572, wouldn't work ending with a "BROM" error 1003. It said the chip was an MT6582. So I flashed a generic MT6582 scatter file. That finally gave me the "OK", but of course it wasn't OK. The phone is no longer recognized by adb, and just barely recognized by the PC.
Problem is, I'm not exactly sure what MediaTek chipset this phone has, and where to get the scatter file for it, and more importantly, where to get the firmware for it (which should contain the scatter file, if I'm not mistaken). Apparently, you can definitely unbrick these types of phones if you have the right scatter file! Needless to say, I did not make backups of anything!
You can unbrick it with the right file. Unfortunately i have them in OSP format which is probably useless to you since I don't have the password to unzip it. To find out the chip you can use MTK Droid Tools. Based on what you said, I can say with uttermost confidence that you have a preloader/boot issue seeing as you probably flash a blank partition over them. The right file will definitely fix it but i haven't found one yet. Will keep looking for you. Would be a breeze if you were in Saint Lucia. lol
Edit: Also something I feel the need to point out is that the 4037* phones have different chipsets and their roms are NOT interchangable. Even the same model (your for example) under different carriers (2BVHCA1 in your case) sometimes give mixed results which i learned the hard way (I had a 4037A working on recently)
That sounds very likely that I flashed a blank partition as you mention, since at one point I chose "firmware upgrade", to try to get past an error I was getting. This forces checkmarks on all ROM sections (including preloader), even though I only had a file for recovery. Unfortunately, MTK Droid Tools (and adb) is pretty useless to me now, as it won't recognize the phone. It looks like I can only flash things via SP Flash Tool.
Since I have no hope any longer of finding a stock ROM for a 4037R OneTouch Pop D3, much less a scatter file, I was really hoping that I could try to flash whatever ROM I can get my hands on that is the closest to it. ie. An "Evolve 2" (4037T)? But if what you say is so, that it has to be the exact ROM for this model, then I don't know how I''ll ever find that. Even a search on Alcatel's website for the 4037R turned up 0 results!
I wonder, if I had a 4037A ROM and flashed that.... could I at least use that to get the phone up and running, even if, say cell / wifi dont work??
As long as the computer reads in without a battery you should at least be able to pull a scatter .txt file which will tell you the chip version even if everything else may be useless. Also you can try the mobile upgrade tool and select 4037 as your phone model. I cannot try it myself but it might work.
http://www.alcatel-mobile.com/global-en/support/product?id=338&model=POP D3
Also if you can i suspect it might be easier to get a similar phone and get a rom dump because the internet isn't too happy about sharing that particular phone's firmware
I had already tried fixing it with Alcatel's Mobile Upgrade tool. I'm afraid it won't recognize the phone without a battery. Nor will MTK Droid Tool (battery in or out), so I can't use that to pull in a scatter file. The PC only seems to recognize the device when the battery is in. (In Mobile Upgrade, with the battery in, I get: "Read terminal information failed...unplug and remove battery". No battery also didn't work in SP Tools, when I specified "without battery" in the options). In fact, even though the PC recognizes a device when the battery is in, it goes bonkers (keeps restarting every 2 seconds). I am still able to flash using SP Tools, however.
I thought about getting another OneTouch Pop D3 to pull the necessary files off of that. But that's not possible, they don't sell it any longer since a long time. Is there maybe another ROM I can download you think might work? The 4037A perhaps? I realize it's risky, but what else can I do?!
I used my 4037R phone to generate a scatter file because I kept getting a BROM ERROR: S_CHIP_TYRE_NOT_MATCH(3168) with the scatter files that I would find online. But even with this generated scatter file I would still get a BROM ERROR: S_CHIP_TYRE_NOT_MATCH(3168) error.
The only scatter file that would work is the MT6582.
But now I can't find a recovery image that will flash properly. I keep getting a S_DL_GET_DRAM_SETTING_FAIL error with every image I try. Do you have a recovery image file that flashed with the 4037R ?
According to XPERIAblog, now we're able to use Flashtool for our device.
Long-term Sony Xperia users will be very familiar with Flashtool, it has been the da facto method of flashing firmware of Xperia devices to a different region. It has been around since the advent of Sony’s Android Xperia phones, but support was not added for any of the 2017 Xperia devices.
However, Flashtool developer Androxyde has updated the application to version 0.9.24.2, which now includes support for the Xperia XZ Premium, Xperia XZ1 and Xperia XZ1 Compact. Do note though that this new version of Flashtool has moved from Java 8 to Java 9, so you will need to run a 64-bit operating system. If you want to download the new version, click here.
Click to expand...
Click to collapse
Source: http://www.xperiablog.net/2018/01/1...t-xperia-xz-premium-and-xz1-devices-0-9-24-2/
Rejoice! Thanks @Androxyde
EDIT: Relevant post: https://forum.xda-developers.com/showpost.php?p=75141403&postcount=3641
Gave my thanks there, although I first saw the news from the same source as OP as well and came here to find more info.
Great news ! Thanks !
Could someone help me understand what the advantages of Flashtool are over Newflasher? I used flashtool on my old z3c...but is there a good reason to switch if newflasher works well enough?
jrbmed08 said:
Could someone help me understand what the advantages of Flashtool are over Newflasher? I used flashtool on my old z3c...but is there a good reason to switch if newflasher works well enough?
Click to expand...
Click to collapse
I think it's just nice and convenient because it's a one-stop shop for flashing xperia devices... it includes xperifirm and such, and has checkboxes for you to remove userdata.sin etc, so you don't actually have to go and do it yourself. Probably just preference and habit. If you're totally fine with newflasher I don't think there's any difference.
I've tried unsucessfully to download 9.24.2 version, can you tell me why ?
Nothing happen when i click on "Get it".
francois64 said:
I've tried unsucessfully to download 9.24.2 version, can you tell me why ?
Nothing happen when i click on "Get it".
Click to expand...
Click to collapse
The "Get it" link links to the download page you're already on, of course "nothing happens".
You need to click on one of the 3 links with your OS description, like "Windows", then decide if you want to download via BT or file host.
OK thanks
My US version XZ1c arrived Wednesday afternoon and I'm fairly new to the whole flashing scene (unrootable Samsung phones and locked bootloaders all my Android life, yay....), so forgive my stupidity. I've followed the guide on XperiaFirmware.com up to part C, which says to install drivers for Flashtool. I believe I've got Flashtool working right now, but I don't know what else I'm supposed to do. Are the drivers located somewhere not on the site, or are they included in the 47.1.A.12.34 folder from XperiaFirmware? I see it contains the newflasher program in there, but I don't understand what the other files are for.
CMT 1412-4444 'Fours' said:
My US version XZ1c arrived Wednesday afternoon and I'm fairly new to the whole flashing scene (unrootable Samsung phones and locked bootloaders all my Android life, yay....), so forgive my stupidity. I've followed the guide on XperiaFirmware.com up to part C, which says to install drivers for Flashtool. I believe I've got Flashtool working right now, but I don't know what else I'm supposed to do. Are the drivers located somewhere not on the site, or are they included in the 47.1.A.12.34 folder from XperiaFirmware? I see it contains the newflasher program in there, but I don't understand what the other files are for.
Click to expand...
Click to collapse
In the install folder for the Flashtool should be a folder called Drivers. Inside that there is an .exe you should run that will install the drivers you need. When you run it you need to select the flashtool drivers from the option as well as the drivers for your model of phone, usually down towards the bottom of the list. If you are running Windows 10 then you will need to disable driver signature checking before trying to run this file. (boot into safe mode and look under advanced menu).
Download the firmware you want to install with Xperiafirm, put it in the flashtool firmware folder.
Run the program, slect the lightning bolt, select the firmware, press ok. It will then start building the image. Then it will ask you to connect your phone.
Make sure your phone is powered off completely. Then plug the USB in whilst holding the volume down button (the led should turn green), Flashtool will recognise the phone, you can let go of the volume button and let Flashtool do it's job.
Edit: having used both Newfalsher and Flashtool, I think Newflasher is easier, but you're already there now so you may as well carry on.
Didgesteve said:
In the install folder for the Flashtool should be a folder called Drivers. Inside that there is an .exe you should run that will install the drivers you need. When you run it you need to select the flashtool drivers from the option as well as the drivers for your model of phone, usually down towards the bottom of the list. If you are running Windows 10 then you will need to disable driver signature checking before trying to run this file. (boot into safe mode and look under advanced menu).
Download the firmware you want to install with Xperiafirm, put it in the flashtool firmware folder.
Run the program, slect the lightning bolt, select the firmware, press ok. It will then start building the image. Then it will ask you to connect your phone.
Make sure your phone is powered off completely. Then plug the USB in whilst holding the volume down button (the led should turn green), Flashtool will recognise the phone, you can let go of the volume button and let Flashtool do it's job.
Edit: having used both Newfalsher and Flashtool, I think Newflasher is easier, but you're already there now so you may as well carry on.
Click to expand...
Click to collapse
I went ahead with Newflasher since the guide is much easier. +1 Thanks
I recently used Flashtool to flash my USA-purchased XZ1C to the .75 Customised DE firmware, and the process was about as simple and straightforward as I can imagine. I also like that provision of the firmware locator is built-in to the Flashtool installation, and the downloaded firmware archive contains a script which puts everything into place for flashing. By default, all user data and settings appear to be maintained. The only thing that might be confusing is that the dialog that pops up indicating it's time to connect the phone only refers to 2011 and 2012 models (both X Compact and XZ1 Compact use the 2012 method). Otherwise, everything proceeds smoothly. Have others had similar positive (or negative) experiences with Flashtool?
pseudonym58 said:
By default, all user data and settings appear to be maintained.
Click to expand...
Click to collapse
So even the apps, data, etc. remains, like when you update OTA ? I am considering updating my (very outdated) firmware without waiting for it to come from Sony, but I don't want to reinstall and reconfigure everything.
@jeff9891
As I indicated previously, nothing seems to have been lost when I used flashtool to install firmware. Of course I can't guarantee that you'll have exactly the same experience, but I have updated both an Xperia xz1 Compact and an Xperia X compact and have not lost any data. In any case I would advise backing up with Xperia companion first.
Thanks, I'll try it this week-end and report, if no OTA update arrives beforehand.
I must be dumb, but I can't find XZ1C in the list in "Flashtool-drivers.exe". Flashtools thereforce recognizes some device is connected, yet it does not display the device's name like it is supposed to do so as far as I read in tutos (even if the program says "driver installed : true") :
Code:
09/008/2018 12:08:31 - INFO - Flashtool Version 0.9.24.4 built on 01-02-2018 22:15:00
(...)
09/009/2018 12:09:10 - INFO - Device connected with USB debugging off
09/009/2018 12:09:10 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/025/2018 12:25:57 - INFO - List of connected devices (Device Id) :
09/025/2018 12:25:57 - INFO - - USB\VID_0FCE&PID_01F4\BH9043YQ9E Driver installed : true
09/025/2018 12:25:57 - INFO - List of ADB devices :
09/025/2018 12:25:57 - INFO - - none
09/025/2018 12:25:57 - INFO - List of fastboot devices :
09/025/2018 12:25:57 - INFO - - none
Sharing some XZ1C flashing process tips for those who may have to cope with the same problems I did.
1) There are no XZ1C dedicated drivers in the drivers.exe that comes with flashtools. Just select the generic "Flashmode drivers" in the list. Still necessary to install them before flashing, though.
2) It is normal that flashtools does not display your device name in its consol as it was supposed to do so with previous phones models. Source: https://www.youtube.com/watch?v=ctqKNAzrKpQ
3) Xperifirm (= the program to grab your phone's latest stock ROM from Sony) is integrated into flashtools. Click the "XF" logo in the top bar, then find your model and download it. It will automatically make it usable in flashtools without fiddling with the files.
4) Follow the general tutorial for flashing: https://forum.xda-developers.com/showthread.php?t=928343 . To enter flash mode with XZ1C, you can follow this tuto : https://www.youtube.com/watch?v=Eid4PApHffg Be aware that your screen will stay black in this mode, but your LED will turn green.
5) Once you plug the phone in flash mode, again, nothing will happen on the phone's screen, but you can follow the flashing on flashtools terminal. Do not be surprised (as I was) if the program does not indicate "flashing completed" or something like that. Just leave the phone and the computer until you obtain this (took like 10 minutes for me):
Code:
09/023/2018 17:23:49 - INFO - Sending Sync
09/026/2018 17:26:01 - INFO - Sync status : OKAY
09/026/2018 17:26:01 - INFO - Sending powerdown
09/026/2018 17:26:01 - INFO - powerdown status : OKAY
09/026/2018 17:26:05 - INFO - Device disconnected
09/026/2018 17:26:06 - INFO - Device connected in flash mode
Then you can just unplug it and turn it on.
jeff9891 said:
Sharing some XZ1C flashing process tips for those who may have to cope with the same problems I did.
[...]
Then you can just unplug it and turn it on.
Click to expand...
Click to collapse
Yes; one difference in my experience with flashtool might have been due to the fact that I had connected my XZ1C to my PC (Windows 10) using Xperia Companion first. I think that ensured that the proper Sony drivers would be in place before attempting to use flashtool. But I'm not sure.
In any case, I have restored the default USA firmware to the XZ1C, as using DE or UK, etc. seemed to restrict my ability to send group text messages (has to do with USA carrier protocols, I guess), and I don't need a fingerprint sensor at this time.
pseudonym58 said:
Yes; one difference in my experience with flashtool might have been due to the fact that I had connected my XZ1C to my PC (Windows 10) using Xperia Companion first. I think that ensured that the proper Sony drivers would be in place before attempting to use flashtool. But I'm not sure.
In any case, I have restored the default USA firmware to the XZ1C, as using DE or UK, etc. seemed to restrict my ability to send group text messages (has to do with USA carrier protocols, I guess), and I don't need a fingerprint sensor at this time.
Click to expand...
Click to collapse
I also used Xperia Companion beforehand on Windows 10, but I had to add the drivers nonetheless. Unsure of the reason it worked for you here. Future flashers will know both ways, though
With Customized_DE (before and after flashing), fingerprint sensor still works for me. Not quite sure, but I believe there are legal restrictions about that in the USA ? As for group text message, I have not tried yet. You mean sending a text to multiple people, or having actual synchronized group discussion using texts ? I thought it was impossible.
jeff9891 said:
[...] As for group text message, I have not tried yet. You mean sending a text to multiple people, or having actual synchronized group discussion using texts ? I thought it was impossible.
Click to expand...
Click to collapse
What I meant was:
Sending a text (with or without image) to a group of people, and have everyone see everyone's replies.
This seems only to be possible (when used in USA on AT&T carrier) when I have the default USA firmware flashed onto the phone. If I use the DE firmware, for instance, I can send a "mass message" to multiple recipients, but then cannot attach an image, and all subsequent replies are private, i.e. between two parties.
1st,
I know there are some threats concerning this issue, but did not found the right hint.
I was going forward and back, again and again - also by offline update, which went well only for the 1st stage:
-1st stage to 10586.107
-2nd stage, only found the cab links for 10586.962 full
but this did fail with same error, does not matter if starting from 8.1 or from 10
Lastly have completly gone back to original ffu 8.1 and than went forward only by using MS-servers...still always the same error <initial download works, then the preparation and install procedure as well, but shortly before 100% the error shows up>
My device should be supported, but later I even spoofed for an RM-1085 from which were used the obviously right boot loader files...I did this before knowing of the log output thought it has to do with lifecycle of the product
pls refer to attached update/install log @the last third - saying there are collisions (0x80070020 - ERROR_SHARING_VIOLATION) and not found files (iot device relelateds?).
Would be fine if someone could inspect the log - escpecially one of the build collector cracks
maybe to try online update or update over USB?
on 10586 make hard reset
enable developer settings and device portal
install Interop Tools https://forum.xda-developers.com/showpost.php?p=74628972&postcount=1071
make interop unlock
change registry to any W10M device (depend did you want AU or FCU), for AU use x30 device, for FCU use x50
now use online update or tool for update over USB https://www.microsoft.com/en-us/download/confirmation.aspx?id=56726
i always do n this way and never have any problem for old 8.1 lumia devices.... but i not recommend upgrade to FCU because AU work much better with old devices
you made my day dxdy
:good::good::good:
can't enough thank you...I will achieve this by pinning your advises onto the wall
not a word too much...this is so useful!
I think I had not the best packages and from now on I do not use "iutool"; the "OtcUpdater" seems so much more reliable - only it is hard to find which packages the files are representing (name scheme)
Also I'll do make hard resets even directly after flashing an full ffu
...will follow your suggestion to stay on AU; currently 14393.1066 - all updates by offline mode
so, :good::good::good:
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(