Develop Bugs

Unlock Xperia Play Bootloader and Install custom firmware.

Hi all I'm a noob so apologies if this is the wrong place but Im having serious issues unlocking the bootloader on my xperia play. I want to unlock it as I'm having issues connecting to the wifi. A search of the internet shows no help as my wifi doesn't even turn on whilst my searches seemed aimed towards those whos wifi was on but not connecting to visible routers. I've done a factory reset and re installed up to date software using sonys pc companion but had 0 Joy. I've tried various routers such as those at works and cafe but nothing.
After a while of searching for answers I decide to try unlocking the phone for custom firmware just to see if it work but Im either overlooking something or am just a failure. I visit the unlockbootloader.sonymobile.com/ webpage and start to follow the somewhat confusing 16 steps.
1. First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu. I follow the instruction no problem and move to step 2.
2. In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked. I do and the phone says it can be unlocked. I do and the phone says it can be unlocked.
3. On your computer, click Continue at the bottom of this page to start the unlock boot loader process.
4. Read through the information in the pop up window and click Yes, I’m sure, if you are still confident you want to unlock the boot loader.
5. Read through and accept the legal terms. Click I Accept.
6. Enter your name, a valid email adress and the first 14 digits of your phone’s IMEI or MEID number (remove the last digit if necessary). Click Submit. You can view the IMEI or MEID number by entering *#06# on your phone.
7. The unlock boot boot loader key will be sent to your email. Save it for later use. I follow ructions and now have the unlock key sat in my inbox.
8. Download and install the latest Android SDK from developer.android.com. I followed the link downloaded and installed the program leaving its folder on the desktop but the folder it came is called adt-bundle-windows-x86_64-20130219 not sure if that matters.
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager. I followed the link and unzipped a sing file called " android-winusb.inf" and leave it on the desktop for safe keeping. Google usb is installed as revision 7.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager. I take the file from my desktop and drag it to theadt-bundle-windows-x86_64-20130219 folder go to sdk > extras > google and finalyy went in to usb_driver folder and pasted android_winusb.inf-file, there I was prometed and chose to replace the orginal.
11. Turn of the phone. So I did.
12. On your phone, push and hold the Fastboot button at the same time as you connect the phone to the computer with a USB-cable. The Fastboot button may differ between different phone models. See the Fastboot buttons page for more information on what button use on your phone. From research I figured the fast boot button was the search button. I plug in the cable and the blue led shows on the top of the phone. The computer also makes an unusual connection noise (beeps 3x) but shows no pop ups asking what I wanted to do with connected device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file. [COLOR="Blue"]This is the point where Im BAFFLED. I have no clue what to do. At no point was I asked for drivers. Looking online Im not the only one to have been confused at this point but Im yet to find an answer that I understand to solver the problem. Its something to do with using device manager to solect s1 boot fastboot and install the driver manauly by searching for it on the pc but I cant for the life of me figure the full process out. [/COLOR]
Step 14, 15, and 16 seem self explanatory but if no one can help with step 13 I'm screwed. Any help would be appricated. I'll worry about the installation of custom firmware later, there are hundred of how instructions on how to do it so Im sure Ill have a bit more success if I can get that far. Ive been going at this all night so thanks in advance for any help.

Updating AT&T OTA issues; need help sideloading

Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}

If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.

This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!

So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse

westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.

Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.

despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?

Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.

New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot

omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.

despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !

Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade

I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.

Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...

bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it

wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk

despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143

Android tablet, how to disable kiosk mode or install new firmware

I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"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"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.

You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.

My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.

Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?

zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.

sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.

zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.

sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.

zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.

sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.

To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz

Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.

1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at

sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.

zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.

Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?

paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !

Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

[GUIDE] How to install Android to HP Elite x3

查看中文版教程 (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 model​HP 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 Unit​1. 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 Thanks​gus33000 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 model​HP 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 Unit​1. 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 Thanks​gus33000 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 model​HP 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 Unit​1. 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 Thanks​gus33000 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 ??