I would like to root this phone so that I can remove bloatware and spyware.
However I am concerned that exploits such as Kingroot may themselves contain malware.
Also I have a Macintosh so I cannot run any Windows-based rooting utility, although I could run Windows in a virtual machine.
If I do run a Windows utility in a virtual machine, I would prefer that it be something official like SP flash tools from Mediatek. (In which case I would not be able to run it with the LTE version of the phone.)
However I've never seen a direct link to the Mediatek website to download this utility.
Does anyone have a URL?
Related
After making a cooked ROM and before flashing into device, is it possible to run on PC enviroment in some sort of simulation or skin to try it out?
I doubt it.
The stand alone emulator from MS actually runs ARM code and uses a bin image file to load the OS.
Trouble is ROMs for different devices have somewhat different structure and are usually encrypted to some degree.
If a tool does exist to RUN certain ROM on a PC it would have to be leaked from the OEM.
So i know the Intel atom in this thing supports Windows 10. I just can't figure out how to get the Windows 10 install disk to boot. Custom boot loader?
AceHack00 said:
So i know the Intel atom in this thing supports Windows 10. I just can't figure out how to get the Windows 10 install disk to boot. Custom boot loader?
Click to expand...
Click to collapse
Custom rom that microsoft has provided.... Win 10 is free for all device's.... Tho you may need a custom recovery in some cases.... Theres also a program that microsoft has that will convert it as long as you have root and able to connect it through usb...
ErocKxMoBz said:
Custom rom that microsoft has provided.... Win 10 is free for all device's.... Tho you may need a custom recovery in some cases.... Theres also a program that microsoft has that will convert it as long as you have root and able to connect it through usb...
Click to expand...
Click to collapse
This is... Just wrong. Microsoft provides no special tool to convert android devices into windows 10. They have released Windows 10 Mobile ROMs for 2 devices and they aren't distributed in a way that they can be ported.
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
ErocKxMoBz said:
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
Click to expand...
Click to collapse
Got any links or how to?
AceHack00 said:
Got any links or how to?
Click to expand...
Click to collapse
No. And there won't be.
ErocKxMoBz said:
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
Click to expand...
Click to collapse
Ok, those Intel tablets you refer to probably use a legacy bios booting system, which would support both Android in the x86 variant, and Windows x86. And MAYBE they support a custom bootloader, but I doubt it (you could provide some links as proof). If you refer to the Windows 10 Mobile ROM released for the Chinese phone a while back. That is literally the one exception, but it isn't Windows 10. Its Windows 10 Mobile, which isn't nearly as full featured, and provides no admin level access. And before someone mentions it, NO this cannot be ported to other devices, Android is much easier to port due to the fact that we know how things function due to the Open Source nature of Android, but Windows is not, and likely never will be Open Source.
Now, onto the "custom bootloader" you refer to. Firstly, no Nexus device EVER has been able to run a custom bootloader (lest I mention the Nexus One with S-OFF). All Nexus devices EVER (yes, even after unlocking the bootloader) enforce aboot (high level bootloader) signature verification, they just don't enforce kernel/recovery partition signature checks when the bootloader is unlocked. This means that flashing an unsigned bootloader (no, you can't sign a bootloader yourself, it would have to be released by Google, which they have NEVER done).
You also mentioned running it virtually? Did you mean like Hardware virtualization like VirtualBox and VMware? Good luck finding a functional x86 Virtual Machine manager for Android that doesn't run horribly.
And without links, or any proof, I have never heard of Microsoft (or any subsidiary) releasing a tool to convert Android phones into Windows phones. Because, it just isn't that simple. You don't just install a program and boom, its Windows 10. It requires a complete re-flash of the device, and different bootloader (which I told you is impossible on this device above), it would also require drivers that are more than likely closed source, or don't exist for the Windows platform.
Don't just go saying things you /think/ are possible. Just cause a CPU architecture matches the requirement of the OS doesn't mean that that. OS will ever run. Much more is required.
I just got my Moto X Play and wanted to root it and flash CM13. I installed the Google USB Drivers to get Windows to recognize the ADB interface, and getting into fastboot mode with ADB works just fine. But once there, "fastboot devices" fails to recognize the device. The device manager shows an unrecognized device "Fastboot lux S" for which the google USB drivers don't work. I've read that this should be fixed by installing the official Motorola drivers, but I would like to avoid that if possible - I'm doing this to get rid of the Motorola crap, installing more of it on my PC to do so would be disappointing.
So, I've got a heap of questions:
- Can I use fastboot on Win7 without installing Motorola-specific drivers? It seems that there should be a generic driver for the fastboot interface as it's a feature on all modern android devices AFAIK.
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
- Does my objection to the Motorola Drivers make sense? Are there any benefits to having the drivers installed if I flash CM on the device?
The drivers are irrelevant to the OS you want. You need the drivers, install the drivers. Your computer is trying to talk to the phone, and right now they are speaking different languages, the driver is an instruction on how to talk to the phone. It has very little to do with Motorola, google didn't build your phone, they supplied the OS. Fastboot is effectively the BIOS of your phone, imagine what would happen if you flashed the wrong BIOS on your computer., would you call Microsoft and say fix it? no.
Install the damn drivers and get over it.
ImWarped said:
It has very little to do with Motorola ...
Click to expand...
Click to collapse
That's exactly why I asked, I thought this was a standartized part of Android for which there might be a generic Windows driver - I guess that's not the case, thanks for the clarification. But I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
fckmoto said:
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
Click to expand...
Click to collapse
fckmoto said:
I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
Click to expand...
Click to collapse
Since my wife moved to an Android phone, our house is Microsoft free. Being a fairly novice user who likes to tinker, this always introduces extra layers of doubt and uncertainty ...even fear, at times. I am forced to wonder, in the presence of all the Windows software and Windows-based procedures and advice, does it work on Linux?
My answer, so far, over three phones, is that if it is adb or fastboot stuff, then, yes it does. Or, at least, so far, everything I've tried works.
Depending on your linux distro, you might have to install some extra package containing those commands. You might want to install the whole Google android package. 99.999% developer stuff, but includes the two commands that you want. It's probably more up-to-date than the Linux-distro versions.
You might have to insert a line with some manufacturer ID (I didn't for the X Play) in some configuration file.
Look... my anti-MS biases show even through a thick overcoat. But do the linux thing only if you want to do linux. By the time you've read this post, you could probably have installed those drivers .
Does my objection to the Motorola Drivers make sense?
Click to expand...
Click to collapse
No.
Thad E Ginathom said:
No.
Click to expand...
Click to collapse
Heh, I guess it's somewhat thick-headed to look for alternatives instead of just installing the drivers. My main problem with that is that Motorola doesn't offer a direct download of the driver but wants me to install a driver manager tool instead... I've kept my pc crapware-free thus far and intend to keep it that way If it's as simple as installing a few Android dev packages under Linux, I'll definitely take that route.
But with bash and the full Canonical repositories coming to Win10, maybe one could use the Linux adb and fastboot binaries under Windows in the not-so-far future... I wonder if those would then work without a device driver
Install 15 seconds adb 1.4.3 and run it in your fastboot folder you create in C of Windows7, no Motorola drivers.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Some useful links for those reinstalling Windows 10 at any point:
Builds - http://mdluup.ct8.pl
This uses Microsoft's UUP (unified update platform) to fetch specific full builds. Choose from Retail or Insider builds. At the time of writing selecting 17134 from the retail channel will get you the newest non-beta build with minimal Windows Updates following installation. Just specify x64/86/ARM, edition and language.
Using the blue Aria2 button will give you a zip which, on execution, will download and create a usable, full ISO for personal use - despite the use of the words "cumulative update" on-site. Just follow the instructions on screen. All images are compiled using Microsoft's internal imaging utility so they're close to what you'd get with a precompiled MSDN ISO.
MSMG Toolkit - http://m.majorgeeks.com/files/details/msmg_toolkit.html
This provides a frontend for component removal utilizing the official Microsoft DISM utility.
Use of this is straightforward and can remove Apps, Windows Features and components from an ISO.
Tip: Once you've mounted an ISO, open a separate command line and run DISM.exe /Image:<path_to_image_directory> [/Get-ProvisionedAppxPackages to get a full list of Apps in the ISO. Copy and paste the output, placing it in the provided RemoveAppsList.txt, removing any lines you want to keep.
Using install_wim_tweak.exe tool will also get you a full listing of all Windows Packages, most of which can be safely removed with zero side effects. NTLite can be a useful guide but its commercial software, so you won't be able to remove all the components you see listed if you install it.
AIO boot tool - https://www.aioboot.com/en/
This tool creates nifty bootable USB sticks that come in handy for booting anything. I recommend the precompiled WinPE 10 images which allow you to use a Live PE Windows Desktop (I.e. it has a full GUI) from a USB prior to installation. This should alleviate the need for making bootable USBs in future. As it's the same platform used during a conventional booted Windows Setup so you can run the setup once its loaded in, format hard drives, etc. Or actually use it as a desktop, I guess. It has its limitations.
DISM++ - https://www.chuyu.me/en/index.html
Post-install utility, you can thoroughly clean up redundant internal Windows folders, remove Apps, activate popular regedits and whatnot. Very useful.
Blackviper - https://github.com/madbomb122/BlackViperScript
Power shell script that makes running services in Windows slightly more efficient.
If people are interested I'm happy to create a tutorial to making your own properly-serviced Windows ISOs for those who want new builds of Windows with less to none of the Microsoft extras .
Dear friends,
Not sure if anybody still watch this forum but I will give it a try.
I have Lumia 640 LTE (RM_1072) updated to Win Mo 10 1703 (and later even 1709 with help of HWID registry change).
WP Internals reported successful bootloader unlock as well as successful root of the device.
Nonetheless, I struggle to benefit from that. There is very scarce information abot what actually the root allows you to do.
In the WPInternals intro video, @HeathcliffXDA says, that it disables checks on access rights, capabilities and privileges and run .NET console apps.
Nonetheless, when I try to write registry key from UWP app it fails on UnauthorizedAccess exception. I tried other things like to run other process from UWP (self hosted self contained console app for .NetCore3.1 on ARM) uploaded to Downloads. That also didn't work.
I am able to pinvoke some stuff from UWP.
Can somebody give me an insight what I am doing wrong?
Is there a howto for compiling .NET console app for Win 10 Mobile?