Related
I've seen that some apps can be uninstalled. Is a bug or feature? Lumia640 XL fast ring.
Have you tried to uninstall ?
This should not be a feature. It should be a bug.
May be this is .provxml bug.
Yep, right now i uninstalled xbox.
All this is hapening after hard reset.
djamol said:
Have you tried to uninstall ?
This should not be a feature. It should be a bug.
May be this is .provxml bug.
Click to expand...
Click to collapse
Not a bug, MS decided to enable uninstall button in the system apps in RS2 and RS1 latest build. UnistallDisabled is set to false in the default prov.xml.
So we can modify prov.xml file and then hardreset?
augustinionut said:
So we can modify prov.xml file and then hardreset?
Click to expand...
Click to collapse
Of course. You could also entirely delete the provisioning files and later install it from store iff you need a clean state without any apps aside from system apps.
Ghoul159 said:
Not a bug, MS decided to enable uninstall button in the system apps in RS2 and RS1 latest build. UnistallDisabled is set to false in the default prov.xml.
Click to expand...
Click to collapse
Ok, good to look xmls. Thanks.
augustinionut said:
So we can modify prov.xml file and then hardreset?
Click to expand...
Click to collapse
Modifying's .provxml would break the signatures of it. So .provxml will be skipped and that specific App installation will skip.
I wish to uninstall Cortana. Damn, battery eater.
MrCego said:
I wish to uninstall Cortana. Damn, battery eater.
Click to expand...
Click to collapse
No you can't. However, you can disable it in the policy manager
How?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Experience\AllowCortana]
"value"=dword:00000000
Default is 1. Change it to 0.
I want to uninstall OneDrive cz it's broken
djamol said:
Modifying's .provxml would break the signatures of it. So .provxml will be skipped and that specific App installation will skip.
Click to expand...
Click to collapse
Phone\Windows\System32\Manifests ...... all can be modified and used after softreset. I changed inside EnterpriseInstall.xml :
DisplayOnAppList="false" to true and after soft reset i was unable to deploy xaps from phone explorer
So atleast inside Manifests are no signature.
Which builds of RS1 have this feature enabled? Don't have it on 10.0.14393.351.
I said UNABLE.
To install Enterprise Xaps, Xaps must be signed and .AETX file must be installed on your device.
Hello, is there any way to uninstall system apps on w10m 10586?
mirasal2 said:
Hello, is there any way to uninstall system apps on w10m 10586?
Click to expand...
Click to collapse
Yes, you can do that using Interop Tools.
Nightsteed said:
Yes, you can do that using Interop Tools.
Click to expand...
Click to collapse
Any suggestions for this message?
mirasal2 said:
Any suggestions for this message?
Click to expand...
Click to collapse
Yes, you have to Interop Unlock your device first!
I have a completely updated HP Elite X3 and have tried various ways to unlock the file system for modification with no success.
Does anyone know the proper way to unlock the file system on the HP Elite X3?
I've tried vcREG with no luck. Thanks All.
dfeldt91 said:
I have a completely updated HP Elite X3 and have tried various ways to unlock the file system for modification with no success.
Does anyone know the proper way to unlock the file system on the HP Elite X3?
I've tried vcREG with no luck. Thanks All.
Click to expand...
Click to collapse
could you please explain more what did you do ?
Witch version of vcREG dd you used ?
I'm prety sure you didn't check this post
http://forum.xda-developers.com/showpost.php?p=68479867&postcount=72
ngame said:
could you please explain more what did you do ?
Witch version of vcREG dd you used ?
I'm prety sure you didn't check this post
http://forum.xda-developers.com/showpost.php?p=68479867&postcount=72
Click to expand...
Click to collapse
Thanks for the response. I have followed the vcREG thread but did not do the part you just showed me with changing the name. I am attempting to do so in vcREG but it is not reading anything.
Would you mind telling me the steps to change the DeviceTargetInfo?
dfeldt91 said:
Thanks for the response. I have followed the vcREG thread but did not do the part you just showed me with changing the name. I am attempting to do so in vcREG but it is not reading anything.
Would you mind telling me the steps to change the DeviceTargetInfo?
Click to expand...
Click to collapse
You can use interop tools / custompfd or vcreg to modify this :
HKLM\System\Platform\DeviceTargetingInfo
Change the PhoneManufacturer to NOKIA
ngame said:
You can use interop tools / custompfd or vcreg to modify this :
HKLM\System\Platform\DeviceTargetingInfo
Change the PhoneManufacturer to NOKIA
Click to expand...
Click to collapse
Perhaps I am doing it wrong in vcREG.
Is this correct:
Open vcReg
Click Hkey_local_machine
Type path: HKLM\System\Platform\DeviceTargetingInfo
Type key: PhoneManufacturer
Hitting Read does nothing.
What are the steps to changing the Manufacturer in vcREG? Sorry to bug, I am a long time Android user and just moved to Windows for the first time. I appreciate the help!
dfeldt91 said:
Perhaps I am doing it wrong in vcREG.
Is this correct:
Open vcReg
Click Hkey_local_machine
Type path: HKLM\System\Platform\DeviceTargetingInfo
Type key: PhoneManufacturer
Hitting Read does nothing.
What are the steps to changing the Manufacturer in vcREG? Sorry to bug, I am a long time Android user and just moved to Windows for the first time. I appreciate the help!
Click to expand...
Click to collapse
Click Hkey_local_machine
Type path: System\Platform\DeviceTargetingInfo
Type key: PhoneManufacturer
ngame said:
Click Hkey_local_machine
Type path: System\Platform\DeviceTargetingInfo
Type key: PhoneManufacturer
Click to expand...
Click to collapse
After doing exactly this, I hit read and nothing shows up. I have typed the path correctly. I'm not sure what is going on. I am going to try a complete reset and then do it again.
dfeldt91 said:
After doing exactly this, I hit read and nothing shows up. I have typed the path correctly. I'm not sure what is going on. I am going to try a complete reset and then do it again.
Click to expand...
Click to collapse
hm, so try to edit this with other registry app like custompfd .
I'm sure that works
ngame said:
hm, so try to edit this with other registry app like custompfd .
I'm sure that works
Click to expand...
Click to collapse
Thanks again for the help, I am currently restoring the phone using Windows Device Recovery Tool to start fresh. I will try CustomPFD and report back any progress.
I am trying to install CustomPFD and am getting error 0X81030120 now and it fails. This is on a fresh reset phone with no modifications other than enabling Developer Mode.
How do you install CustomPFD without getting the error?
I am using XAPdeployment to install.
@ngame Accessing normal registry still requires ndtksvc.dll in System32 running. @dfeldt91
Go to "Registry Editor for All Device".
http://forum.xda-developers.com/windows-10-mobile/jailbreak-interop-unlock-windows-10-t3178140
Or you can use alternate registry editor.
http://forum.xda-developers.com/windows-10-mobile/interop-tools-appx-windows-10-mobile-t3373675
djamol said:
@ngame Accessing normal registry still requires ndtksvc.dll in System32 running. @dfeldt91
Go to "Registry Editor for All Device".
http://forum.xda-developers.com/windows-10-mobile/jailbreak-interop-unlock-windows-10-t3178140
Or you can use alternate registry editor.
http://forum.xda-developers.com/windows-10-mobile/interop-tools-appx-windows-10-mobile-t3373675
Click to expand...
Click to collapse
I attempt to deploy the roottool.xap but it hangs and hangs and never installs.
I jsut noticed that in the Info section of the phone it now says ACERINC whch is one of the things I tried changing the phone registry to for manufacturer so......maybe I'm making progress here? I really don't know. Could not get either of the above to install.
Following it... only via W10 for desktop, no way for the remote registry editing via Windows 7 Professional?
djamol said:
Or you can use alternate registry editor.
http://forum.xda-developers.com/windows-10-mobile/interop-tools-appx-windows-10-mobile-t3373675
Click to expand...
Click to collapse
The proper thread would actually be: http://forum.xda-developers.com/win...app-interop-tools-versatile-registry-t3445271
The OP even includes instructions on how to unlock for other oem devices.
---------- Post added at 08:14 AM ---------- Previous post was at 08:09 AM ----------
dfeldt91 said:
Could not get either of the above to install.
Click to expand...
Click to collapse
Make sure you're reading the Interop Tools installation instructions carefully and that you're using the one from the official thread which is here: http://forum.xda-developers.com/win...app-interop-tools-versatile-registry-t3445271
It should install properly
gus33000 said:
Make sure you're reading the Interop Tools installation instructions carefully and that you're using the one from the official thread which is here: http://forum.xda-developers.com/win...app-interop-tools-versatile-registry-t3445271
It should install properly
Click to expand...
Click to collapse
When I install Interop tools on the X3 it does not show up anywhere, as an app or in the extras location.
Ok, link was posted. I downloaded the file and installed it. Now the problem I have is when installing interop tools. I copy to SD card, click the dependency files to install then install interop tools by clicking on it. It doesn't show up as an app and doesn't show up in extras.
dfeldt91 said:
When I install Interop tools on the X3 it does not show up anywhere, as an app or in the extras location.
also, that link has TBD written in the spot for the OEM files. So the files are unavailable.
Click to expand...
Click to collapse
I just updated the OP again. And where did you see it should be in extras? Don't follow or read the older thread that got posted, go to the storage settings, make sure interop tools isn't listed at all, if it is, uninstall it, then download the current pre-release 8 of beta 1.9, and read carefully the instructions. You are required to install using device portal. If it failed, device portal should give you a specific error code. Just make sure to follow the installation instructions from the official thread and everything should go alright.
Edit: reopen the thread and download the other missing ndtk spkgs zip too. Forgot to include it.
gus33000 said:
I just updated the OP again. And where did you see it should be in extras? Don't follow or read the older thread that got posted, go to the storage settings, make sure interop tools isn't listed at all, if it is, uninstall it, then download the current pre-release 8 of beta 1.9, and read carefully the instructions. You are required to install using device portal. If it failed, device portal should give you a specific error code. Just make sure to follow the installation instructions from the official thread and everything should go alright.
Click to expand...
Click to collapse
Ok, let me give this another shot! Thanks for the help, it is appreciated!
NDTK files
Ok, Got the NDTK files installed and it is restarting...
..OK.. Success. IT is installed, I can browse files from my PC and delete them. I deleted the system apps I don't use such as Xbox, Get Help, Continuum, etc. They immediately force close when clicked on in the start menu but do not disappear when the phone is restarted. I noticed the app files showed back up under Data\SYSTEMAPPS as well.
Does anyone know how to permanently remove these apps from the start menu?
Elite X3
hello just bought this baby and it seems a normal user can't do much **** with it.... Microsoft store askes for money even for word...lol
please be kind to help me how can I manage to install cracked apps if this is possible... I have read that normal win 10 exes don't work
also how can I root my device....
thanks
dfeldt91 said:
Ok, Got the NDTK files installed and it is restarting...
..OK.. Success. IT is installed, I can browse files from my PC and delete them. I deleted the system apps I don't use such as Xbox, Get Help, Continuum, etc. They immediately force close when clicked on in the start menu but do not disappear when the phone is restarted. I noticed the app files showed back up under Data\SYSTEMAPPS as well.
Does anyone know how to permanently remove these apps from the start menu?
Click to expand...
Click to collapse
Please help, my phone is dead and I need these files to recover it
please
http://www.lumiafirmware.com/ser/RM-1099
WojtasXda said:
http://www.lumiafirmware.com/ser/RM-1099
Click to expand...
Click to collapse
There was no ede file
To delete.
DilanChd said:
Maybe @gus33000
Click to expand...
Click to collapse
Sorry for the delay, paging @maruf8
Have fun!
gus33000 said:
Sorry for the delay, paging @maruf8
Have fun!
Click to expand...
Click to collapse
Wow thanks man!! :laugh: But where did you get it?? I also have a Lumia 540 (RM-1141). I want that's emergency files too.
maruf8 said:
Wow thanks man!! :laugh: But where did you get it?? I also have a Lumia 540 (RM-1141). I want that's emergency files too.
Click to expand...
Click to collapse
Here you go, RM-1141.
Hello! gus300,
I used the ede file for 540 for unlocking bootloader with wpi 2.3 but failed.
Hex mismatch!
(From wpi log)
ahsan547 said:
Hello! gus300,
I used the ede file for 540 for unlocking bootloader with wpi 2.3 but failed.
Hex mismatch!
(From wpi log)
Click to expand...
Click to collapse
The ede files have to match the device RM model number, you can't easily use one that doesn't have the same RKH
gus33000 said:
Here you go, RM-1141.
Click to expand...
Click to collapse
Thank you so much bro.. But where did you get these? I couldn't find it in lumia firmware website..
guss33000, Mine is RM-1141. But I am unable to unlock bootloader but wpi hard bricked my 540 (no display no vibration even it was not being detected by wdrt (it was not on the list after I clicked device not detected) ). But thank you very much your provided ede,edp file saved my lumia.
ahsan547 said:
guss33000, Mine is RM-1141. But I am unable to unlock bootloader but wpi hard bricked my 540 (no display no vibration even it was not being detected by wdrt (it was not on the list after I clicked device not detected) ). But thank you very much your provided ede,edp file saved my lumia.
Click to expand...
Click to collapse
Did WPI ask you to manually reset the phone? as emergency files aren't public it won't download them and you have to manually specify them for the phone to automatically reboot, when WPI doesn't have any it will ask you to manually reboot at times. If not then it's a brick I guess, you may want to post what you did and logs to the WPI thread for this issue to be fixed.
gus33000 said:
The ede files have to match the device RM model number, you can't easily use one that doesn't have the same RKH
Click to expand...
Click to collapse
gus33000 said:
Did WPI ask you to manually reset the phone? as emergency files aren't public it won't download them and you have to manually specify them for the phone to automatically reboot, when WPI doesn't have any it will ask you to manually reboot at times. If not then it's a brick I guess, you may want to post what you did and logs to the WPI thread for this issue to be fixed.
Click to expand...
Click to collapse
From wpi log I saw that the hex was mismatched and another thing is Lumia 540's ffu has only one version which 8.10.15137.148 and it's not supported by wpi so will I be able to unlock the boot loader of 540 using wpi2.3? If yes then how? I commented on wpi2.3 thread but got no reply.
Thank you
ahsan547 said:
From wpi log I saw that the hex was mismatched and another thing is Lumia 540's ffu has only one version which 8.10.15137.148 and it's not supported by wpi so will I be able to unlock the boot loader of 540 using wpi2.3? If yes then how? I commented on wpi2.3 thread but got no reply.
Thank you
Click to expand...
Click to collapse
You can unlock the bootloader with any OS version on your phone, as long as you have a supported ffu selected for boot files in the third field. By default when you use download all it's automatically selected for you.
If you're getting an issue with Qualcomm DLOAD, then try to not specify any emergency payload. WPI will work nonetheless, but it will ask you to manually reboot your phone from time to time.
gus33000 said:
You can unlock the bootloader with any OS version on your phone, as long as you have a supported ffu selected for boot files in the third field. By default when you use download all it's automatically selected for you.
If you're getting an issue with Qualcomm DLOAD, then try to not specify any emergency payload. WPI will work nonetheless, but it will ask you to manually reboot your phone from time to time.
Click to expand...
Click to collapse
Yes you are right but I downloaded Lumia 550's; it's version is 10.0.10586.107 and it's supported by wpi2.3 but wpi can't unlock boot loader. What should I do now??
I can't manually enable root access on images because wpi doesn't support 8.10.15137.148 and wpi crashes.
ahsan547 said:
Yes you are right but I downloaded Lumia 550's; it's version is 10.0.10586.107 and it's supported by wpi2.3 but wpi can't unlock boot loader. What should I do now??
I can't manually enable root access on images because wpi doesn't support 8.10.15137.148 and wpi crashes.
Click to expand...
Click to collapse
I unlocked the bootloader by 550's ffu bro.. It should work for you too ?
maruf8 said:
I unlocked the bootloader by 550's ffu bro.. It should work for you too
Click to expand...
Click to collapse
bro please please tell me the steps how did you do that. Please! IN 3 days I flashed my 540 about 45 times!
Are you from bangladesh?
ahsan547 said:
bro please please tell me the steps how did you do that. Please! IN 3 days I flashed my 540 about 45 times!
Are you from bangladesh?
Click to expand...
Click to collapse
I did it on a 430. I don't know about 540.
Yes i am
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.
Hello, so I am currently rooted on the January update and decided to update to June's update and reroot.
I downloaded the official full image and tried to flash it using the flash-all command. But I am getting this error I MOST be doing something working. Any ideas or a quick guide on how to update and root June's update !?
Thank you
jblanko6 said:
Hello, so I am currently rooted on the January update and decided to update to June's update and reroot.
I downloaded the official full image and tried to flash it using the flash-all command. But I am getting this error I MOST be doing something working. Any ideas or a quick guide on how to update and root June's update !?
Thank you
Click to expand...
Click to collapse
Did you extract the files first from the factory image and place them in your SDK/platform-tools folder?
Badger50 said:
Did you extract the files first from the factory image and place them in your SDK/platform-tools folder?
Click to expand...
Click to collapse
Yes sir
jblanko6 said:
Yes sir
Click to expand...
Click to collapse
Are you using minimal adb?
Badger50 said:
Are you using minimal adb?
Click to expand...
Click to collapse
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .
jblanko6 said:
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .
Click to expand...
Click to collapse
Looks like you are using sdk/platform-tools. Are you also using a Mac laptop?
Badger50 said:
Looks like you are using sdk/platform-tools. Are you also using a Mac laptop?
Click to expand...
Click to collapse
No , windows 10 .
I know the device is being detected in fastboot mood by the computer. It might be something to do with how I am currently rooted. Most "how to " instructions only talk about partitions _a and _b.
Put a space between bootloader and C:\
bradputt said:
Put a space between bootloader and C:\
Click to expand...
Click to collapse
I agree error in syntax
jblanko6 said:
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .
Click to expand...
Click to collapse
there's no such fastboot command "flash_other", you don't have to flash bootloader to both partition.
use googles release of sdk not the entire thing
fastboot flash-all
and bam
You can also go straight to your platform-tools folder and double click the flash-all.bat file to start the installation :good:
Badger50 said:
You can also go straight to your platform-tools folder and double click the flash-all.bat file to start the installation :good:
Click to expand...
Click to collapse
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command
jblanko6 said:
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command
Click to expand...
Click to collapse
Do you have all the files you extracted from the factory image inside the platform-tools folder?? Especially the large secondary zip that has all the images?
jblanko6 said:
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command
Click to expand...
Click to collapse
If still no luck, download this from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download another copy of June update in case first was corrupt.
Place all Tools files plus unzipped June update files into one folder. Make sure your usb cable is an oem Pixel cable.
Use Windows command prompt instead of Powershell. Type fastboot devices with phone connected in fastboot mode.
If you get a serial number, double click on flash-all.bat. It oughta run fine.
Okay so i have doing this fine but i can't seem to update as well
I use window latest platform tools all files in one directory where i open the cmd
Here is what it says @Badger50
Sent from my Google Pixel 2 XL using XDA Labs
michaelbsheldon said:
If still no luck, download this from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download another copy of June update in case first was corrupt.
Place all Tools files plus unzipped June update files into one folder. Make sure your usb cable is an oem Pixel cable.
Use Windows command prompt instead of Powershell. Type fastboot devices with phone connected in fastboot mode.
If you get a serial number, double click on flash-all.bat. It oughta run fine.
Click to expand...
Click to collapse
If you can look above post i am doing everything right i guess
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
If you can look above post i am doing everything right i guess
Click to expand...
Click to collapse
It sure looks right, and I know you've done this before. What happens when you shut the phone off and then enter bootloader manually. I know it shouldn't matter, but what the heck. That's exactly what I do every month, I never boot into fastboot from the OS and adb ?
Badger50 said:
It sure looks right, and I know you've done this before. What happens when you shut the phone off and then enter bootloader manually. I know it shouldn't matter, but what the heck. That's exactly what I do every month, I never boot into fastboot from the OS and adb ?
Click to expand...
Click to collapse
I'll try it out and let you know stay put ?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
I'll try it out and let you know stay put ?
Click to expand...
Click to collapse
I'll be here :good::good: