Related
Trying to root my sprint galaxy s3.
As a new user I am blocked from properly posting the link for the instructions I'm following, so you'll have to copy/paste. They are here:
galaxys3root.com/galaxy-s3-root/how-to-root-u-s-canadian-dual-core-galaxy-s3-on-mac-osx/
(I'm using linux not mac, but anyway)
When I plug in the phone, I can see in linux dmesg that it is connected. (I did enable USB debugging in the developer options)
However when I run adb-linux, it does not detect the device
# ./adb-linux wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
(hangs forever)
# ./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
#
So adb-linux is not detecting the phone-- the list of devices is empty
I'm using debian with linux kernel 3.2.0 (I also tried with kernels 2.6.38 and 2.6.32, same result. I'm running as root, note the # prompt)
Someone posted about a similar problem, and a helpful person recommended "Did you try the kext fix?" - but I have not been able to figure out what the kext fix is and if it is applicable-- the only place I found it mentioned was in relation to Odin.
http://m.youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=/watch?v=7Soapch0c5U
Riding the Uni on the GSIII
jwitt418 said:
youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=%2Fwatch%3Fv%3D7Soapch0c5U
Riding the Uni on the GSIII
Click to expand...
Click to collapse
thanks, but not helpful since it's a windows-only solution.
However I found a newer version of ADB (stands for Android Debug Bridge) and it is seeing my device! So I'll post back with an update as to how the root goes.
btw - running e.g. ./adb-linux version will show the version. 1.0.25 failed, and 1.0.29 seems to be working
success! Rooted my phone. upgrading from adb 1.0.25 to adb 1.0.29 made the difference.
I'm on the June security patch and I haven't been able to update anything OTA even though I have an AT&T SIM. Is there someway to force the Software Update check to work properly by using a pm command in the shell? Do I need to sideload the firmware to get it update to OREO and if so, what is the command and where can I find the full file. Any help would be useful.
please go here: https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/XT1789-04/
download the at&t rom for your device.
unzip into platformtools.
and run these commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
let me know if this helps you get back on track with being able to update from AT&T
i have used this in a bat script to install the AT&T rom on the tmobile hardware, then i was able to go back to stock once more and install updates.
Do these commands work on a locked bootloader which AT&T has? Does someone have a good understanding of how the following packages work regarding ota updates?
com.motorola.ccc.devicemanagement
com.motorola.ccc.checkin
com.motorola.ccc.mainplm
com.motorola.ccc.ota
com.motorola.ccc.notification
I was wondering if i could clear out the cache of one of them or disable then re-eanable one or more of them would that possibly fix my ota problems?
I am having the same issue, the phone is stuck on the June patch and no matter what I do I can't get any updates, nor will adb sideload or install update from zip in recovery work.
edit:
got it working, if you are still stuck on June security patch just download the AT&T update from the 2nd post above, put the phone into bootloader mode, and unzip the attached bat file in the folder then run it (ensure you have the Motorola drivers installed). as soon as I rebooted and set up I checked for updates and it started downloading the new 8.0.
DISCLAIMER: for AT&T Z2 Force models.... will wipe data.... this worked for me may not work for you... use at your own risk.... it's you not me.... this is your choice.
i did the same, now i have november update but i didnt get the oreo update afterwards.
Install the stock rom
Is there any way to flash the downloaded stock rom from post 2? No further OTA update
What do you mean will wipe data
Mrgabi said:
What do you mean will wipe data
Click to expand...
Click to collapse
It will wipe everything from your phone like a factory reset so make sure you have a backup of whatever you need to reinstall.
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next.
Thanks,
Click to expand...
Click to collapse
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
kingstu said:
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
Click to expand...
Click to collapse
OK well, I bought it on Swappa it was new (resale) so the box was opened but everything else wasn't and still had the plastic on it. So I contacted Motorola on their support forums and they said to just wait a little while and see if it'll update but too they also said they'd have someone take a look into it as they have my IMEI number so I guess will see what they say.
Thanks for the reply
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hello, Just checked and it says my warranty expires Sep 2018. So hopefully it shouldn't cost. Now though if I do return it I am assuming they'll just want the device nothing else and will they send me back a new device as this device is new no scratches or nothing and don't want to get back a device that has any marks or scuffs etc. Also, the first thing I did before even turning the device on was put on a tempered glass screen protector so I am assuming I'd take that off before I sent the device back to them. Either way, I hope I can get the issue fixed without having to return it but at least I know it's under warranty, Assuming that when it says Sep 2018 that once Sep 1st hits that the warranty will be expired?
Thanks again
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hey, I dropped my device off with FedEx on Sunday and Motorola said they received it yesterday, anyways just wondering how long your turnaround time. I have my Moto E4 that I can use so it's not the worst if I have to wait. Hopefully, it won't be too long especially if they're just going to send me a new device that should have Android oreo and updated security patches on it.
Thanks again for your advice.
Seems like it runs through script fine until the end
Script seems to run fine until the end. Phone wont boot and flashes at logo screen and then goes to bootloader logs saying your device didn't start up successfully. Need help. Can anyone help with this? I think the problem might be with the userdata not automatically formatting at the end. Nevermind, Everything all good after 3 or 4 tries. I still can't update to the latest build after flashing, which is OCXS27.109-47-11 according to what I looked @ att website. It says I have the latest version which is OCXS27.109-47-7. Anyone have the latest build to flash?
i had the same issue
I've used Lenovo Smart Moto Assistant and managed to get the last update
I have the same issue with T mobile. the phone says there is a new update, it downloads and tries to install but fails. I am on the May 2018 security patch, OCXS27.1.3. Android File Host and other sites don't list any new firmware. I have tried the Lenovo Smart Moto Assistant and it also doesn't recognize the new update. Any suggestions?
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
Click to expand...
Click to collapse
westec2 said:
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
Click to expand...
Click to collapse
Hello.
I don't know if i did not understand correctly, but when I have the phone recognized to do the update, i turn it off, and since the PC stops recognizing it is connected, the lenovo smart assistant goes back to the sync page.
How could you achieve that? Do you have another setting on your PC or lenovo assistant software?
Do you turn it off before clicking proceed?
Do you turn it off while the "all information could be wiped" is on screen?
Do you turn it off when the "loading bar" starts?
Could you be more specific? I would like to update my phone.
Thank you.
Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.2
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
If you prefer to not use the app, simply run this in an adb shell:
Code:
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
If you are unable to set those properties for whatever reason, like if you have returned to stock after flashing the mbn and no longer have root, there is another possibility to force VoLTE/VoWiFi; There's a secret code you can use to force-enable it, but unfortunately it does not survive a reboot (not sure why ASUS didn't make it persistent).
Enter this in the dialler:
Code:
*#*#3642623344#*#*
The number will clear itself, and you shouldn't see any output if it succeeded.
When you have done this, go to (System) Settings -> Mobile network and toggle Mobile data off then on again. You should hopefully see the VoWiFi or VoLTE icon in the status bar now, but like I said above you will have to redo this if you reboot the phone - so if you can, please use the properties method instead.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
Code:
<efstool port="2500" remote="true" baudrate="38400" password="FFFFFFFFFFFFFFFF" spc="000000"/>
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.
HomerSp said:
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.
Click to expand...
Click to collapse
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.
Cammarratta said:
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.
Click to expand...
Click to collapse
Make sure you dont have QPST server running. Its not required if using the tools. I ran into this issue and realized thats what it was that was using it.
How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!
Cammarratta said:
How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!
Click to expand...
Click to collapse
Open up QPST Configuration > at the top click Server > then Stop QPST Server. After that, see if efsTools give you anything. (efsTools efsInfo)
Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though
Cammarratta said:
Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though
Click to expand...
Click to collapse
What does it say for you? It won't find it if you turn it off. What is the COM port / driver that shows up in Device Manager
xbamaris1` said:
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?
Click to expand...
Click to collapse
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.
HomerSp said:
Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.1
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
You can test the connection by running this in the cmd window:
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards
Click to expand...
Click to collapse
Absolutely genius, your work here is greatly appreciated everything is working perfectly VoLTE and VoWiFi with caller display
I used the EE mbn included in the Xiaomi Mi 9T MBNs provided , So for anyone on EE i can say it works without a problem.
Thank you :good:HomerSp
in device manager it shows up as
Qualcomm HS-USB Android DIAG 902D (COM13)
EDIT: It started working oddly enough. Which mi9 file would I flash for tmobile USA to test?
Thank you in advance for this!
Edit 2: got it working! Had to Uninstall, reinstall qpst, open up app and click enable DIAG, then stop the server in qstp and input the commands and it worked!
HomerSp said:
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.
Click to expand...
Click to collapse
Thought so, just wanted to make sure.
https://imgur.com/a/WZvKteM is what I get. Is it possible to go back to an earlier RAW rom? I want to see if theres something in earlier ROMS that will make it work. I'm just at a loss. I'm not sure what I'm missing for this to work.
@HomerSp, thanks so much for all your efforts and skills - works a charm on ee UK using Mi9T MBN's
xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Same issue as you, i had it working at the start then it just stopped altogether. Hoping a next asus update could reset whatever i did to it and retry it again
Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?
killerdvd said:
Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?
Click to expand...
Click to collapse
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.
Cammarratta said:
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.
Click to expand...
Click to collapse
Thanks for the quick response. My device is already showing in device manager with COM 6. I never installed QPST since is not needed for USB connection. QPST is not even mention on OP.
I want to say the first part says that you need to have DIAG enabled.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Click to expand...
Click to collapse
Which I think needed QPST installed. Unless I'm sadly mistaken, then please disregard!
* Prelude
What started this journey was noticing that Tasker had restricted call screening
to android versions 10+. I would be delighted to hear what techniques fellow
forum members use to fight spam calls. I am a complete beginner, and so I
thought I would detail my journey in case it proves useful for others. There is
some outdated information and plenty of online tutorials, it just takes some
time to sort it out.
I have a Huawei P20 lite ANE LX3.
* Unlocking the Bootloader
I believe this is by far the most tedious step. Now that I am free from carrier
contracts, I know that my next phone will not be from a manufacturer with a
locked bootloader. In any case you may have some luck emailing Huawei directly
or through paid third-party services. What worked for me was potatoNV
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
The documentation on the repository is perfectly fine. Specifically in my case,
the device first showed under device manager as 'USP SER' and I had to reinstall
the test point drivers (found in the above README) for it to turn into 'Huawei
USB COM 1.0.' PotatoNV did its job and I managed to get my unlock code.
* Project Treble/GSI? Fastboot? ADB?
Again, being new to all of this, I did notice a lot of noise when searching
online for information. The most informative links I found useful:
- https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
- https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
- https://developer.android.com/studio/releases/platform-tools
What is worth repeating is to USE THE GOOGLE PLAY APP 'TREBLE INFO' over the
more popular 'Treble Check', which falsely informed my that I needed an A image
rather than being fine with an A/B image. This wasted a lot of my time.
Initially I went down the route of using TWRP to flash the image, but this led
me to a soft brick (could very well be my own fault). The phone was frozen to
the TWRP splash screen, 'adb reboot bootloader' would not work. Power plus
volume down or volume up also had no effect. With no access to e-recovery or the
bootloader, I had really dug myself into a hole.
* Unscrewing a bricked phone
My last chance at fixing this consisted of getting the stock service firmware.
[NO ROOT] [BOOTLOADER LOCK] How to install an update [DLOAD Method]
I'm very happy :D:D After spending a lot of time trying to figure out how to install an original firmware using the dload method, I managed to find a guide that explains how to do it and today I will report the main steps: First of all, we need...
forum.xda-developers.com
This forum thread was useful and on unscrewing the situation. The real useful
part of the above link was the 'Software Upgrade Guidelines' documentation.
So ultimately what unbricked my phone was following the direction to press all
three buttons (power, volume up, volume down) at once to enter "automatic
upgrade mode." I gather this was supposed to utilize the 'dload' folder I copied
over earlier. As an aside, it was a lifesaver that 'adb shell' gave me access to
some unix commands to make poking around easier. The automatic upgrade using the
'dload' folder failed.
BUT RESTARTING FROM THIS "AUTOMATIC UPGRADE MODE" GRANTED ME ACCESS TO RECOVERY
MODE VIA THE POWER BUTTON + VOLUME UP whereas before this was not the case. By
the grace of God this allowed me to download a recovery image from Huawei
servers. How much longer will their servers retain this image? I don't know, but
I'm grateful either way.
* Lineage OS successfully flashed
What instead worked for me was flashing the "GSI image without TWRP" - from the
2nd of the 3 links above. This is the image that I used:
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
For sake of completeness M Rahman's 2018 article was still mostly accurate, the
'-u' flag may be omitted from 'fastboot -u flash system name_of_system.img'. The
only other thing I would append to his instructions is -AIF-'s recommendation to
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow
warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe
data/factory reset'.Reboot . - From:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I say this because I had seen the power button + down volume/up volume technique
yield different results depending on whether the phone was connected to the
computer. I suspect this is the fault of HiSuite, but who is going to track down
a bug like this?
* Evaluation
Pros:
- I had solved my initial problem.
- The new phone feeling!
Cons:
The most noticeable deficiency was that adding an external SD card AS SYSTEM
STORAGE would never finish; I gave it about a day before giving up.
I will add further reports as they come up.
In conclusion I give props to Huawei for keeping that server image alive, but
last I heard they were pivoting away from smartphones into clean energy
altogether. If I were to do it all over again, I'm not sure it would be worth
it. This took a good day's worth of time.
Big thanks to the AOSP developers and the XDA community for buying
my old P20 lite a bit more time. I'm also interested in which companies the
community considers friendly to "popping the hood"/tweaker mentality.
Hope this was helpful for someone,
查看中文版教程 (Chinese version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To moderators: This phone originally had Windows 10 Mobile installed, so I posted it here. Please move it if topic is unsuitable in Windows 10 Mobile forum.
Code:
#/usr/bin/env python3
print('''
Your warranty is... still valid?
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
''')
First of all, thanks to pst125675 for testing Android dump on HP Elite x3 Retail unit. So far I can say converting HP Elite x3 into Android is completely possible - although there're some known issues.
To download HP Elite x3 Android dump, visit here:
https://forum.xda-developers.com/t/not-guide-android-dump-of-hp-elite-x3-for-future-use.4558603/
Known issues- IMEI will be erased. I don't know how to fix it for now, but you can make telephone call properly if your country/region's regulation doesn't require a proper IMEI value.
Known unaffected countries/regions: China, Russia.
- Unable to use fingerprint sensor, IR sensor.
- Difficult to revert it back to Windows 10 Mobile. Guess you don't want to revert it back anyway.
Applicable modelHP Elite x3 Open Market variant, both retail and prototype unit can be used.
Telstra and Verizon variants might be supported (same RKH), but they're untested - do it at your own risk!
DO NOT TRY IT ON OTHER WP MODELS!
Procedure for Retail Unit1. Disable Reset Protection (if applicable) in settings and downgrade the phone back to initial release (10.0.14393.953) with Windows Device Recovery Tool or FFUTool. If your phone is locked out from Reset Protection, there're some methods to bypass it which aren't covered here.
2. At this point, do not connect to Internet during the entire procedure. Enable Developer Mode and install Interop Tools, install NDTKSvc then enable Interop Unlock here. If you were always trying to hack your HP Elite x3 then I'm sure you've already known how to enable Interop Unlock.
https://forum.xda-developers.com/t/...es-now-on-github.3445271/page-7#post-68463839
3. Copy attached registry file to the phone, disconnect the phone and import it with Interop Tools. After that reconnect it to your phone.
4. Connect your phone back to PC, and browse to EFIESP folder\Windows\system32\boot, locate resetphone.efi file and rename it to resetphonex.efi.
5. Download the debugprod package from here: https://gus33000.me/2019/01/05/secureboot-flaw-for-all-wp-devices-literally/ and extract developermenu.efi from it, rename it to resetphone.efi and copy it to EFIESP folder\Windows\system32\boot of your phone.
6. Power off the phone and press both vol- and power key to get Windows Phone Boot Menu. Use power key to select Mass Storage mode.
7. Connect the phone to PC. You can use something to backup entire eMMC before doing any further, like HxD from https://mh-nexus.de/en/downloads.php?product=HxD20 or dd. Open disk with read-only mode (choose MSFTPhone eMMC) and find somewhere with at least 58.2GB storage space.
8. You may want to backup QCN before installing Android (in case you want to restore IMEI). This part will be mentioned in replies.
9. Now use Rufus ( https://rufus.ie/ ) to install the extracted Android dump to your phone. You'll have to tick "List USB Hard Drives" so your phone will be listed in Rufus. When you're ready, click START button to start Android installation.
WARNING: BE CAREFUL! DO NOT DISCONNECT THE PHONE DURING THE PROCEDURE, OR IT WILL KILL YOUR PHONE AND NO WAY TO REVIVE! IF YOU ARE USING A LAPTOP TO FLASH YOUR PHONE, MAKE SURE YOU HAVE SLEEP DISABLED AND KEEP EXTERNAL AC ADAPTER CONNECTED!
10. Now wait 1-3 hours for the procedure completes. Once the procedure completes, force reboot the phone.
11. Your phone will boot into Android. You may see an error message in Chinese that told you decryption failed. Simply tap the button "恢复出厂设置" to perform factory reset.
12. Enjoy Android OS on your glorious HP Elite x3.
Procedure for Prototype Unit
If you're not sure if you have a prototype unit, check if your phone meets any of following conditions:
- HP Sample, Not for Sale is printed on the back
- You can see Not for Resale text displayed during boot
- No fingerprint sensor and a more generally known HP logo is used
If your phone doesn't meet any of conditions above, then your phone isn't a prototype unit. This part is not for you.
Simply follow this guide to put your phone into EDL mode, use any Snapdragon 820 eMMC firehose programmer to backup/restore the entire phone. The prototype variant allows you to revert it back to Windows Phone variant whenever you want.
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
Special Thanksgus33000 and Rafael Rivera for discovering the production signed Developer Menu and Interop Tools development
My partner for discovering the existence of HP Elite x3 prototype with Android OS
pst125675 for his first trial and error procedure
Bootloader Unlock
It's possible to unlock the bootloader after installing Android. However since I cannot find Fastboot driver that completely suitable for HP Android devices, you'll have to force install Fastboot driver for other OEMs on it.
Once Fastboot driver installed, the bootloader unlock procedure will be pretty generic. Simply enable OEM Unlocking in Developer Options, reboot to Fastboot mode and execute this command, then confirm bootloader unlock:
Code:
fastboot flashing unlock
It's also possible to install Magisk root on this phone, simply use 7-Zip to open Android dump and extract boot.img inside, then patch it with Magisk.
Backup QCN
This procedure can be only done before you convert it to Android.
To enable diag port, you'll have to download attached diagnostic.rar , boot the phone into Mass Storage mode and execute this command under Administrator privilege. Assume your MainOS drive is mounted at drive G.
Code:
enableQCComp.bat G:\ SerialCompositeConfig
EnableMSFTStack.bat G:\ SerialCompositeConfig
Once 2 commands were executed successfully, reboot it back to normal OS and make QCN backup with QPST.
How about revert it back to Windows 10 Mobile?You'll need to build a TWRP, which obviously isn't available. Or at least enable Rooted ADB Shell under stock recovery.
I'm sure developers are talented enough to modify boot/recovery images to have it enabled.
hikari_calyx said:
you'll have to force install Fastboot driver for other OEMs on it.
Click to expand...
Click to collapse
first of all, many many thanks for the support in bringing our wonderful HP back to life, by providing all the files.
Can you also please guide me in the right direction on where to find/how to install fastboot driver? Is it needed on Ubuntu too?
a_petrov303 said:
first of all, many many thanks for the support in bringing our wonderful HP back to life, by providing all the files.
Can you also please guide me in the right direction on where to find/how to install fastboot driver? Is it needed on Ubuntu too?
Click to expand...
Click to collapse
For Windows, right click on Update Driver, Select Driver manually, and choose All Devices, select any generic Fastboot driver you have installed.
Fastboot driver installation is unneeded for Linux distro or macOS.
A known working driver is the Google driver provided on Google website: https://developer.android.com/studio/run/win-usb
Many thanks for your reply. I am struggling to enter fast boot mode.
adb reboot fastboot is not working, only adb reboot bootloader. Then I get the same menu as with "Vol - + Power" buttons combination :
START
Restart Bootloader
Recovery mode
Power Off
Boot to FFBM
Can you please explain how you got into fastboot mode in order to execute fastboot flashing unlock? I have already extracted boot.img from the dump, many thanks
a_petrov303 said:
Many thanks for your reply. I am struggling to enter fast boot mode.
adb reboot fastboot is not working, only adb reboot bootloader. Then I get the same menu as with "Vol - + Power" buttons combination :
START
Restart Bootloader
Recovery mode
Power Off
Boot to FFBM
Can you please explain how you got into fastboot mode in order to execute fastboot flashing unlock? I have already extracted boot.img from the dump, many thanks
Click to expand...
Click to collapse
You've already entered Fastboot mode.
Simply connect your phone to PC under this screen.
hikari_calyx said:
You've already entered Fastboot mode.
Simply connect your phone to PC under this screen.
Click to expand...
Click to collapse
I think I have tried that, but the phone was simply invisible to the computer.
Fastboot devices command was returning zero devices, but before that adb reboot recovery was working thus restarting the phone into this mode (fastboot mode).
a_petrov303 said:
I think I have tried that, but the phone was simply invisible to the computer.
Fastboot devices command was returning zero devices, but before that adb reboot recovery was working thus restarting the phone into this mode (fastboot mode).
Click to expand...
Click to collapse
Provide a screenshot of Device Manager.
Also, do not use Minimal ADB and Fastboot.
hikari_calyx said:
Provide a screenshot of Device Manager.
Also, do not use Minimal ADB and Fastboot.
Click to expand...
Click to collapse
thank you for your help, I think I understand what I was doing wrong - the fastboot command has to be entered via sudo (In Ubuntu)
How I will try root via magisk, if there is tutorial on that, please share
also, I was thinking, how realistic is to have a working TWRP for our phone and maybe some custom ROMs? Is it too much to hope for this model? )))
apetrov1x5 said:
also, I was thinking, how realistic is to have a working TWRP for our phone and maybe some custom ROMs? Is it too much to hope for this model? )))
Click to expand...
Click to collapse
I made a barely working TWRP based on existing ZUK Z2 TWRP.
I said "barely working", which means only ADB commands will work, you can't touch the screen at all. Also it exceeded 64MB so you can't flash it right into your phone, you can only boot into it with "fastboot boot twrp.img".
I'm not ready to post this to public.
Does it allow to work with hp lapdock (screen+keyboard accessory for the x3) from this android fw?
apg1983 said:
Does it allow to work with hp lapdock (screen+keyboard accessory for the x3) from this android fw?
Click to expand...
Click to collapse
Yes it does, you'll get a totally different experience.
hikari_calyx said:
only ADB commands will work, you can't touch the screen at all
Click to expand...
Click to collapse
hikari_calyx said:
查看中文版教程 (Chinese version)
View attachment 5864361
To moderators: This phone originally had Windows 10 Mobile installed, so I posted it here. Please move it if topic is unsuitable in Windows 10 Mobile forum.
Code:
#/usr/bin/env python3
print('''
Your warranty is... still valid?
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
''')
First of all, thanks to pst125675 for testing Android dump on HP Elite x3 Retail unit. So far I can say converting HP Elite x3 into Android is completely possible - although there're some known issues.
To download HP Elite x3 Android dump, visit here:
https://forum.xda-developers.com/t/not-guide-android-dump-of-hp-elite-x3-for-future-use.4558603/
Known issues- IMEI will be erased. I don't know how to fix it for now, but you can make telephone call properly if your country/region's regulation doesn't require a proper IMEI value.
Known unaffected countries/regions: China, Russia.
- Unable to use fingerprint sensor, IR sensor.
- Difficult to revert it back to Windows 10 Mobile. Guess you don't want to revert it back anyway.
Applicable modelHP Elite x3 Open Market variant, both retail and prototype unit can be used.
Telstra and Verizon variants might be supported (same RKH), but they're untested - do it at your own risk!
DO NOT TRY IT ON OTHER WP MODELS!
Procedure for Retail Unit1. Disable Reset Protection (if applicable) in settings and downgrade the phone back to initial release (10.0.14393.953) with Windows Device Recovery Tool or FFUTool. If your phone is locked out from Reset Protection, there're some methods to bypass it which aren't covered here.
2. At this point, do not connect to Internet during the entire procedure. Enable Developer Mode and install Interop Tools, install NDTKSvc then enable Interop Unlock here. If you were always trying to hack your HP Elite x3 then I'm sure you've already known how to enable Interop Unlock.
https://forum.xda-developers.com/t/...es-now-on-github.3445271/page-7#post-68463839
3. Copy attached registry file to the phone, disconnect the phone and import it with Interop Tools. After that reconnect it to your phone.
4. Connect your phone back to PC, and browse to EFIESP folder\Windows\system32\boot, locate resetphone.efi file and rename it to resetphonex.efi.
5. Download the debugprod package from here: https://gus33000.me/2019/01/05/secureboot-flaw-for-all-wp-devices-literally/ and extract developermenu.efi from it, rename it to resetphone.efi and copy it to EFIESP folder\Windows\system32\boot of your phone.
6. Power off the phone and press both vol- and power key to get Windows Phone Boot Menu. Use power key to select Mass Storage mode.
7. Connect the phone to PC. You can use something to backup entire eMMC before doing any further, like HxD from https://mh-nexus.de/en/downloads.php?product=HxD20 or dd. Open disk with read-only mode (choose MSFTPhone eMMC) and find somewhere with at least 58.2GB storage space.
8. You may want to backup QCN before installing Android (in case you want to restore IMEI). This part will be mentioned in replies.
9. Now use Rufus ( https://rufus.ie/ ) to install the extracted Android dump to your phone. You'll have to tick "List USB Hard Drives" so your phone will be listed in Rufus. When you're ready, click START button to start Android installation.
WARNING: BE CAREFUL! DO NOT DISCONNECT THE PHONE DURING THE PROCEDURE, OR IT WILL KILL YOUR PHONE AND NO WAY TO REVIVE! IF YOU ARE USING A LAPTOP TO FLASH YOUR PHONE, MAKE SURE YOU HAVE SLEEP DISABLED AND KEEP EXTERNAL AC ADAPTER CONNECTED!
10. Now wait 1-3 hours for the procedure completes. Once the procedure completes, force reboot the phone.
11. Your phone will boot into Android. You may see an error message in Chinese that told you decryption failed. Simply tap the button "恢复出厂设置" to perform factory reset.
12. Enjoy Android OS on your glorious HP Elite x3.
Procedure for Prototype Unit
If you're not sure if you have a prototype unit, check if your phone meets any of following conditions:
- HP Sample, Not for Sale is printed on the back
- You can see Not for Resale text displayed during boot
- No fingerprint sensor and a more generally known HP logo is used
If your phone doesn't meet any of conditions above, then your phone isn't a prototype unit. This part is not for you.
Simply follow this guide to put your phone into EDL mode, use any Snapdragon 820 eMMC firehose programmer to backup/restore the entire phone. The prototype variant allows you to revert it back to Windows Phone variant whenever you want.
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
Special Thanksgus33000 and Rafael Rivera for discovering the production signed Developer Menu and Interop Tools development
My partner for discovering the existence of HP Elite x3 prototype with Android OS
pst125675 for his first trial and error procedure
Click to expand...
Click to collapse
First of all, thank you for making a guide on how to install android to the Elite x3.
I've got a problem, after changing the registry files of the windows phone (step 3), the phone doesn't show on my computer. Am I missing something or doing something wrong?
luaadev said:
I've got a problem, after changing the registry files
Click to expand...
Click to collapse
How do u mean registry files,it is only one .reg file in rar.Try another cable,or interop tools installation gone wrong,at last try reseting win...
Is it only me or camera can't focus? And battery is draining somehow fast
kew1701 said:
Is it only me or camera can't focus? And battery is draining somehow fast
Click to expand...
Click to collapse
Yeah, battery drains faster than on W10M. And autofocus works fine, it's not an issue with your phone. You just bad at aiming
bebrahero228 said:
You just bad at aiming
Click to expand...
Click to collapse
anyway,thank authors for a hard work,i though it will never be android on x3,but "three years ljejter" ,they done it...
hikari_calyx said:
查看中文版教程 (Chinese version)
View attachment 5864361
To moderators: This phone originally had Windows 10 Mobile installed, so I posted it here. Please move it if topic is unsuitable in Windows 10 Mobile forum.
Code:
#/usr/bin/env python3
print('''
Your warranty is... still valid?
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
''')
First of all, thanks to pst125675 for testing Android dump on HP Elite x3 Retail unit. So far I can say converting HP Elite x3 into Android is completely possible - although there're some known issues.
To download HP Elite x3 Android dump, visit here:
https://forum.xda-developers.com/t/not-guide-android-dump-of-hp-elite-x3-for-future-use.4558603/
Known issues- IMEI will be erased. I don't know how to fix it for now, but you can make telephone call properly if your country/region's regulation doesn't require a proper IMEI value.
Known unaffected countries/regions: China, Russia.
- Unable to use fingerprint sensor, IR sensor.
- Difficult to revert it back to Windows 10 Mobile. Guess you don't want to revert it back anyway.
Applicable modelHP Elite x3 Open Market variant, both retail and prototype unit can be used.
Telstra and Verizon variants might be supported (same RKH), but they're untested - do it at your own risk!
DO NOT TRY IT ON OTHER WP MODELS!
Procedure for Retail Unit1. Disable Reset Protection (if applicable) in settings and downgrade the phone back to initial release (10.0.14393.953) with Windows Device Recovery Tool or FFUTool. If your phone is locked out from Reset Protection, there're some methods to bypass it which aren't covered here.
2. At this point, do not connect to Internet during the entire procedure. Enable Developer Mode and install Interop Tools, install NDTKSvc then enable Interop Unlock here. If you were always trying to hack your HP Elite x3 then I'm sure you've already known how to enable Interop Unlock.
https://forum.xda-developers.com/t/...es-now-on-github.3445271/page-7#post-68463839
3. Copy attached registry file to the phone, disconnect the phone and import it with Interop Tools. After that reconnect it to your phone.
4. Connect your phone back to PC, and browse to EFIESP folder\Windows\system32\boot, locate resetphone.efi file and rename it to resetphonex.efi.
5. Download the debugprod package from here: https://gus33000.me/2019/01/05/secureboot-flaw-for-all-wp-devices-literally/ and extract developermenu.efi from it, rename it to resetphone.efi and copy it to EFIESP folder\Windows\system32\boot of your phone.
6. Power off the phone and press both vol- and power key to get Windows Phone Boot Menu. Use power key to select Mass Storage mode.
7. Connect the phone to PC. You can use something to backup entire eMMC before doing any further, like HxD from https://mh-nexus.de/en/downloads.php?product=HxD20 or dd. Open disk with read-only mode (choose MSFTPhone eMMC) and find somewhere with at least 58.2GB storage space.
8. You may want to backup QCN before installing Android (in case you want to restore IMEI). This part will be mentioned in replies.
9. Now use Rufus ( https://rufus.ie/ ) to install the extracted Android dump to your phone. You'll have to tick "List USB Hard Drives" so your phone will be listed in Rufus. When you're ready, click START button to start Android installation.
WARNING: BE CAREFUL! DO NOT DISCONNECT THE PHONE DURING THE PROCEDURE, OR IT WILL KILL YOUR PHONE AND NO WAY TO REVIVE! IF YOU ARE USING A LAPTOP TO FLASH YOUR PHONE, MAKE SURE YOU HAVE SLEEP DISABLED AND KEEP EXTERNAL AC ADAPTER CONNECTED!
10. Now wait 1-3 hours for the procedure completes. Once the procedure completes, force reboot the phone.
11. Your phone will boot into Android. You may see an error message in Chinese that told you decryption failed. Simply tap the button "恢复出厂设置" to perform factory reset.
12. Enjoy Android OS on your glorious HP Elite x3.
Procedure for Prototype Unit
If you're not sure if you have a prototype unit, check if your phone meets any of following conditions:
- HP Sample, Not for Sale is printed on the back
- You can see Not for Resale text displayed during boot
- No fingerprint sensor and a more generally known HP logo is used
If your phone doesn't meet any of conditions above, then your phone isn't a prototype unit. This part is not for you.
Simply follow this guide to put your phone into EDL mode, use any Snapdragon 820 eMMC firehose programmer to backup/restore the entire phone. The prototype variant allows you to revert it back to Windows Phone variant whenever you want.
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
Special Thanksgus33000 and Rafael Rivera for discovering the production signed Developer Menu and Interop Tools development
My partner for discovering the existence of HP Elite x3 prototype with Android OS
pst125675 for his first trial and error procedure
Click to expand...
Click to collapse
were is the file in 4 step ??