[CLOSED] Delete Thread. - Moto E4 Guides, News, & Discussion

Due to the disrespect of certain members on here I will no longer share the tutorials.

RE: How To Delete Bloatware On Metro PCS XT1765 "THANKS"
AWSOME! Thanks... I was finally able to remove every piece of bloatware that I couldn't before no matter uninstaller I used. Thanks a million for saving the day.
Using Virgin Mobile Qualcomm/Perry Moto E4.
Articul8Madness said:
Ok. I ran into an issue trying to delete the bloat stock apps off this model. Figured it out. It's tedious, but will help you out. As always, you are responsible for your own phone, I ascertain no responsibility if you mess up. Do this AT YOUR OWN RISK.
The Metro PCS variant has almost 7GB out of 16GB in use out the box, mostly with stock phone apps I never use. Deleting them has been a challenge, so here's a noob friendly guide to trying to get stuff out. ***NOTE*** I have not figured out a definitive it's safe to delete list on this phone, mostly because of how this phone hides the crap we want to get rid of in the OEM. I will be including a com list in this post for those interested trying to figure out what is the name of pesky files they want to get rid of.
Things you need:
1. Newest version of Titanium Backup arm compatible version (later versions may not work)
2. Newest version of Root Explorer arm compatible version (later versions DO NOT WORK)
3. Root (This is a must)
4. Minimal ADB and Fastboot
5. Moto E4 cable
Step One - Install apps.
Step Two - Open Titanium Backup. It'll give you a message root might not be rooty enough, ignore. Go and find an app you want to delete. Mine was FM Radio. When you go to try and delete it, the FM Radio.apk will delete, but the com.motorolablahblablah.fmradio file, which is the one that actually deletes it, won't. An error will come up and it will say "Cannot Remove System App, the apk cannot be found".
Step Three - Open Root Explorer. Make sure you're mounted to R/W. Find the app manually in system/app folder. Delete it there. Be careful and don't delete the wrong file. Go to your apps. You will still see it in the list of apps.
Step Four - Reboot the phone. When it reboots the app won't be listed. Open Titanium Backup, and check there for the file. I still saw the com.motorolafmradio file, so I deleted it there. This go round, it deleted.
Updates: Thanks to @ATTACK's suggestion in another thread, you can also use the Amazon Fire trick.
Now, when I did this method I ran into something odd. While I was able to delete some of the more stubborn apps, if I ran the commands over again the packages were still listed in the packages list even after deletion and phone rebooting. The com.facebook file was especially peculiar reinstalling itself and revealing itself, as it didn't even show up in my Titanium Backup list. Can't say it's fully delete yet.
Comprehensive list of ALL PACKAGES.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Code:
package:com.android.cts.priv.ctsshim
package:com.gd.mobicore.pa
package:com.google.android.youtube
package:com.google.android.ext.services
package:com.motorola.motocare
package:com.android.providers.telephony
package:com.google.android.gallery3d
package:com.android.sdm.plugins.connmo
package:com.google.android.googlequicksearchbox
package:com.nuance.nmc.sihome.metropcs
package:com.android.providers.calendar
package:com.itsmarta.martaapp
package:com.motorola.config.wifioverlay
package:com.android.providers.media
package:com.qti.service.colorservice
package:com.google.android.onetimeinitializer
package:com.google.android.ext.shared
package:com.motorola.bug2go
package:com.android.wallpapercropper
package:com.quicinc.cne.CNEService
package:com.motorola.ccc.devicemanagement
package:com.motorola.android.fmradio
package:com.soundcorset.client.android
package:com.privacystar.android.metro
package:com.android.documentsui
package:com.motorola.android.settings.modemdebug
package:com.android.externalstorage
package:com.android.htmlviewer
package:com.motorola.hotspotlauncher
package:com.android.mms.service
package:com.android.providers.downloads
package:com.motorola.coresettingsext
package:com.google.android.apps.messaging
package:com.motorola.android.settings.diag_mdlog
package:com.motorola.entitlement
package:com.motorola.att.phone.extensions
package:com.motorola.ccc.checkin
package:com.motorola.programmenu
package:com.motorola.ccc.mainplm
package:com.metropcs.metrozone
package:com.motorola.motgeofencesvc
package:com.google.android.configupdater
package:com.motorola.ccc.ota
package:com.motorola.ccc.notification
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.vending
package:com.android.pacprocessor
package:com.motorola.pgmsystem2
package:com.motorola.motodisplay.env
package:com.motorola.demo.env
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.google.android.marvin.talkback
package:com.behringer.android.control.app.xair
package:com.qti.qualcomm.datastatusnotification
package:android
package:com.android.contacts
package:com.motorola.android.provisioning
package:com.motorola.imagertuning_perry
package:me.lyft.android
package:com.android.egg
package:com.android.mtp
package:com.android.stk
package:com.android.backupconfirm
package:com.google.android.launcher
package:com.motorola.timeweatherwidget
package:com.google.android.deskclock
package:org.codeaurora.ims
package:com.android.statementservice
package:com.google.android.gm
package:com.google.android.apps.tachyon
package:com.motorola.motocit
package:com.android.sdm.plugins.sprintdm
package:com.motorola.carriersettingsextoverlay
package:com.google.android.instantapps.supervisor
package:com.google.android.setupwizard
package:com.qualcomm.qcrilmsgtunnel
package:com.android.providers.settings
package:com.android.sharedstoragebackup
package:com.google.android.music
package:com.android.printspooler
package:com.motorola.android.sepolicyupdate
package:com.motorola.colorprofiles
package:com.android.sdm.plugins.diagmon
package:com.android.dreams.basic
package:com.lenovo.lsf.user
package:com.android.inputdevices
package:com.motorola.android.nativedropboxagent
package:com.tmobile.pr.adapt
package:android.oem.overlay
package:com.android.systemuioverlay
package:com.motorola.android.jvtcmd
package:com.motorola.frameworks.singlehand
package:com.motorola.motosignature.app
package:com.google.android.apps.cloudprint
package:com.google.android.apps.docs
package:com.google.android.apps.maps
package:com.android.providers.partnerbookmarksoverlay
package:com.motorola.imsconfigtest
package:com.android.cellbroadcastreceiver
package:com.motorola.invisiblenet
package:com.google.android.webview
package:com.rovio.tnt
package:com.motorola.contacts.preloadcontacts
package:com.android.server.telecom
package:com.google.android.syncadapters.contacts
package:com.motorola.android.providers.settings
package:com.android.facelock
package:com.android.keychain
package:com.google.android.calculator
package:com.android.chrome
package:com.qualcomm.qti.rcsbootstraputil
package:com.android.dialer
package:com.google.android.packageinstaller
package:com.google.android.gms
package:com.google.android.gsf
package:com.google.android.ims
package:com.google.android.tts
package:com.verizon.omadm
package:com.android.calllogbackup
package:com.google.android.partnersetup
package:com.motorola.genie
package:com.motorola.setup
package:com.google.android.videos
package:com.motorola.lifetimedata
package:com.motorola.appdirectedsmsproxy
package:com.android.proxyhandler
package:com.motorola.carrierconfig
package:com.metro.simlock
package:com.motorola.messaging
package:com.google.android.feedback
package:com.google.android.printservice.recommendation
package:com.google.android.apps.photos
package:com.google.android.calendar
package:com.motorola.onetimeinitializer
package:com.android.managedprovisioning
package:com.motorola.launcherconfig
package:com.motorola.android.providers.chromehomepageoverlay
package:com.motorola.demo
package:com.motorola.hide
package:com.motorola.moto
package:com.android.sdm.plugins.dcmo
package:com.android.providers.partnerbookmarks
package:com.google.android.gsf.login
package:com.summit.nexos.sdk.app.service
package:com.android.wallpaper.livepicker
package:com.motorola.carriersettingsext
package:com.motorola.devicemanagement
package:com.motorola.motocare.internal
package:com.facebook.system
package:com.handmark.metro.launcher
package:com.motorola.storageoptimizer
package:com.google.android.inputmethod.korean
package:com.qualcomm.qti.rcsimsbootstraputil
package:com.motorola.fmplayer
package:com.google.android.backuptransport
package:com.motorola.audioeffects
package:com.android.storagemanager
package:com.android.bookmarkprovider
package:com.android.settings
package:com.google.android.inputmethod.pinyin
package:com.android.sprint.hiddenmenuapp
package:com.qualcomm.location
package:com.android.omadm.service
package:com.android.cts.ctsshim
package:com.motorola.launcher3
package:com.lmi.motorola.rescuesecurity
package:com.qualcomm.qti.tetherservice
package:com.motorola.actions
package:com.android.vpndialogs
package:com.google.android.apps.wallpaper
package:com.bonusxp.legend
package:com.motorola.bach.modemstats
package:com.android.phone
package:com.android.shell
package:com.android.wallpaperbackup
package:com.android.providers.blockednumber
package:com.android.providers.userdictionary
package:com.android.emergency
package:com.lookout
package:com.motorola.cameraone
package:com.android.location.fused
package:com.android.systemui
package:com.motorola.motodisplay
package:com.android.bluetoothmidiservice
package:com.facebook.appmanager
package:com.motorola.tmo.settingsext
package:com.google.android.play.games
package:com.android.bluetooth
package:com.qualcomm.timeservice
package:com.qualcomm.atfwd
package:com.motorola.config.wifi
package:com.android.providers.contacts
package:com.android.captiveportallogin
package:com.google.android.inputmethod.latin
package:com.motorola.android.providers.chromehomepage
EDIT: I still haven't figured out which ones are safe to delete fully and which ones are not. Working on a list after tinkering with mine.
Click to expand...
Click to collapse

Chamayo said:
AWSOME! Thanks... I was finally able to remove every piece of bloatware that I couldn't before no matter uninstaller I used. Thanks a million for saving the day.
Using Virgin Mobile Qualcomm/Perry Moto E4.
Click to expand...
Click to collapse
No problem Chamayo! But I have a question.
When you deleted all your bloat from that variant, how much space did it leave you with. I deleted every single piece of mine and I still have about 10GB in use on my model. Just curious.

Related

Windows Phone 7 Series Emulator ROM Unlocked

Windows Phone 7 Series Emulator ROM is Unlocked, now is it possible to make ROM for our pda ?
source http://www.mobiletechworld.com/ .
here is the link to download it http://www.neologics.eu/dan/WM70Full.zip
.............................. already posted
http://forum.xda-developers.com/showthread.php?t=647138&page=28 go to last page
kel16harris said:
.............................. already posted
http://forum.xda-developers.com/showthread.php?t=647138&page=28 go to last page
Click to expand...
Click to collapse
I agree but the last page won't always be the last page...
so this seems better..
and the original link is dead
best news about WP7 in the past few days... thanks
Anyone ot the unlocked ROM Dump ?
Can someone clarify something for me.
Isn't this the unlocked rom for the x86 emulator/? As in, its not compiled for an arm processor and therefore won't work to produce a Rom as yet?
Also, if anyone knows - is the new CE core similar enough that older drivers could be used for the HD2 (for example)?
unlocked ROM mirrors
hxxp://mediafire.com/?mjzkgmhnhmb
hxxp://narod.ru/disk/18905455000/WM70Full.bin.html
so i managed to build xnaframworkcore.dll into a rom, where is the silverlight packages? and do you think there is any way to test the framework in a winmo 6.5 rom?
How do I install the BIN?
New to all of this .. can anyone tell me what I do with the new unlocked BIN?
Thanks a lot for your help!
edyg023 said:
New to all of this .. can anyone tell me what I do with the new unlocked BIN?
Thanks a lot for your help!
Click to expand...
Click to collapse
Download the Windows Phone tools put the bin in C:\program files\microsoft xde\1.0 folder and start a command prompt run->cmd or type cmd in search box for Win 7
then type
cd C:\program files\microsoft xde\1.0
xde (Bin name).bin
Emulator will run
Does anyone know how to get accounts to setup after ROM?
Does anyone know how to get WP7 accounts to setup? Or does this just not work? I can get out with Internet Explorer ... but I can't get the accounts to setup correctly!
Yeah as far as we know integrating accounts doesn't work.
Seems like accounts do work in emulator...
Kloc said:
Yeah as far as we know integrating accounts doesn't work.
Click to expand...
Click to collapse
The guys at PocketNow did it:
pocketnow.com/software-1/windows-phone-7-series-walkthrough-messaging-calendar-email
Sorry, not allowed to post links...
Don't know how they did it...
Drats! I was really hoping to see some of the social networking, email and calendar features work!
Pouwel said:
The guys at PocketNow did it:
pocketnow.com/software-1/windows-phone-7-series-walkthrough-messaging-calendar-email
Sorry, not allowed to post links...
Don't know how they did it...
Click to expand...
Click to collapse
They didn't get facebook integrated. You can view calendar either war. I don't know about e-mail I didn't look at that.
I can't get any accounts to sync either - tried both google apps (via activesync) and facebook - no dice.

[WARNING] about safely debloat on SM -T705

Hello fellas,
This thread mainly only suggesting about Debloating Safely before even start it... it was only a small problem, but CAN SAVE YOU VERY WELL ON THE FUTURE.
Based on my experience after rooting my device, Tab S 8.4 Lollipop 5.1.1, using Kingroot, successfully fyi...
The problems arise after i was being greedy on free RAM. I looked on threads about debloating and which ones are safe to remove. And it is safe. But one thing, i deleted VpnDialogs.apk on priv-app folder on root..
So the main solution is to use Titanium Backup Pro (has to be pro to do this), to freeze the services/apps you consider as bloatwares.. so that, in case of errors, you can safely defrost them on the future.
Sincerely,
TOMMY
NB. If you have a Samsung Galaxy tab S 8.4 (Sm-T705), on lollipop 5.1.1, if you like, you may send the missing file to me (\system\priv-app\), the folder inside them, named "VpnDialogs", includes the one file inside it, VpnDialogs.apk... I will be so grateful to report here my experience in repairing misdebloated sm-t705... my email is [email protected]
The link below might help.
http://forum.xda-developers.com/galaxy-tab-s/help/list-bloated-apps-to-uninstall-sm-t700-t2861180
John

[Q] Disabling UUP on Mobile

I have an old Lumia 810 running on RS2 and haven't been able to update it directly since the UUP came out (I always get the error 0x80070273). The only way of uptading for me has been rolling back to WP8 and then all the way up to RS2. Is it prossible to dissable the new UUP on mobile? Thanks in regards.
Nightsteed said:
I have an old Lumia 810 running on RS2 and haven't been able to update it directly since the UUP came out (I always get the error 0x80070273). The only way of uptading for me has been rolling back to WP8 and then all the way up to RS2. Is it prossible to dissable the new UUP on mobile? Thanks in regards.
Click to expand...
Click to collapse
HKLM/software/Microsoft/WindowsUpdate/
there's supports UUP value change it to 0 but still I don't think it helps
karaki93 said:
HKLM/software/Microsoft/WindowsUpdate/
there's supports UUP value change it to 0 but still I don't think it helps
Click to expand...
Click to collapse
I have the same error on the Samsung ativ se. Now on the Assembly 15063.2 continue to be updated can not. Neither 15063.138 neither 15205... Maybe find a solution?
delasago said:
I have the same error on the Samsung ativ se. Now on the Assembly 15063.2 continue to be updated can not. Neither 15063.138 neither 15205... Maybe find a solution?
Click to expand...
Click to collapse
leave the insider program and wait for official release as a workaround it's just a matter of days
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate] "SupportsUUP"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator] "EnableUUPScan"=dword:00000000
now use InteropTools, enable full file access, delete all data from
Code:
C:\WINDOWS\SoftwareDistribution\Download\
, to clear all already downloaded files. Reboot and scan for new update.
Maybe this works for Mobile, too.
I'm still having the same error so i was wondering if someone that's going to upgrade to redstone 2 can upload what's in C:\WINDOWS\SoftwareDistribution\Download\ before restarting the phone to complete the update?
this is not working i tried but still getting error
Yash Agarwal windows said:
this is not working i tried but still getting error
Click to expand...
Click to collapse
http://www.lumiafirmware.com/info найди на этом сайте свою модель под свой регион и прошивай телефон согласно инструкции на сайте, бояться кирпича не стоит

W10M Windows Update Issue (Error: 0x80070273)

Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP
This is an issue with most of the x20 series phones. No one has been able to get it fixed so far.
извиняюсь что пишу на русском языке, нужно перепрошить ваш телефон под ваш регион и данная ошибка исчезнет.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
level143 said:
Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP
Click to expand...
Click to collapse
http://www.lumiafirmware.com/info найди на этом сайте свою модель под свой регион и прошивай телефон согласно инструкции на сайте, бояться кирпича не стоит
level143 said:
Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP
Click to expand...
Click to collapse
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 on my 1020 and another 925 which were stuck in the CU build .297 with success.
Keep in mind that the parameters that I will use are specific to these phone models and if you have a different model you need to find the requested 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 before a proper backup.
Let's start.
The problem appears because during update phase the oeminput.xml file becomes corrupted: as far as I know it happens only for some x20 model, 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 is oeminput.xml. Save it with notepad.
Now modify the file
<SOC>{PROCESSOR_NAME}</SOC>
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 unlocked also 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...
Let me know if you have problems or need more informations...
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:
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 on my 1020 and another 925 which were stuck in the CU build .297 with success.
Keep in mynd that the parameters that I will use are specific to these phone models and if you have a different model you need to find the requested 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 before a proper backup.
Let's start.
The problem appears because during update phase the oeminput.xml file becomes corrupted: as far as I know it happens only for some x20 model, 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 is oeminput.xml. Save it with notepad.
Now modify the file
<SOC>{PROCESSOR_NAME}</SOC>
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 unlocked also 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...
Let me know if you have problems or need more informations...
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
Click to expand...
Click to collapse
Nice guide! You should post it in a separate topic
Nightsteed said:
Nice guide! You should post it in a separate topic
Click to expand...
Click to collapse
good idea!! Done!
I have a similar problem I have Lumia 1020 10,0,15063,297 wanting to update me it pulls error 0x800f8003
I had the same error 0x80070273 on my Lumia 1520, RM-938. It was impossible to update its OS. It was stuck on the 10.0.15063.2 OS version.
I followed all the steps outlined here how to replace the corrupted OEMInput.xml file.
I am rocking 10.0.15063.674 OS version now.
Thanks a lot.
Dear all, have the same Error code: 0x80070273.
Because I am new to win10 mobile, I don't know how to manipulate the file OEMInput.xml inside my German Lumina 1520.
Is there someone arround who can write a detailed Manual what to do on PC and on the Phone?
Thanks a lot.
sigfrid696 said:
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...
Click to expand...
Click to collapse
Yay, this worked perfectly on my Lumia 1020. Now Windows Update thinks it's a 950XL, and I've got the latest 2018-01 Update for arm-based devices. Very cool. Thank you so much to you and Antonio!
- Do the 2 en-US below also have to be changed to the phone's language ? :
<BootUILanguage>en-US</BootUILanguage>
<BootLocale>en-US</BootLocale>
- My USB port is broken ... so i cannot connect the phone to the PC
Is it possible to go to phone\windows\imageupdate and overwrite it with a oeminput.xml file from the sd card ?
- "after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools"
Even uninstalling InteropTools, Full filesystem access remains ON ?? Does a factory reset desactivate full file system access ?
i have been trying for many days to fix this error problem Windows Phone Update Error 0x80070273 .. I understand all about the solution in this page but the problem is when I apply full access on interop it show system files of the phone but all are protected as read only . so I can't replace or modify any files .. what to do to remove this read only protection on phone system files ?
oemimput.xml backup
I'm just leaving it here as a backup because who knows, when MS will get rid of this code from their servers. Today i have noticed, that Windows Device Recovery Tool is no longer working. Thanks a LOT for helping me resolve the problem using oemimput.xml re-build.
<?xml version="1.0" encoding="utf-8" ?>
<OEMInput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
<Description>Test FFU generation for {SOC TYPE} with build number XXXXX</Description>
<SOC>{PROCESSOR_NAME}</SOC>
<SV>{SV_NAME}</SV>
<Device>{DEVICE_NAME}</Device>
<ReleaseType>Test</ReleaseType>
<BuildType>fre</BuildType>
<SupportedLanguages>
<UserInterface>
<Language>en-US</Language>
</UserInterface>
<Keyboard>
<Language>en-US</Language>
</Keyboard>
<Speech>
<Language>en-US</Language>
</Speech>
</SupportedLanguages>
<BootUILanguage>en-US</BootUILanguage>
<BootLocale>en-US</BootLocale>
<Resolutions>
<Resolution>480x800</Resolution>
</Resolutions>
<AdditionalFMs>
<AdditionalFM>%WPDKCONTENTROOT%\FMFiles\MSOptionalFeatures.xml</AdditionalFM>
<!-- Add OEM FM files here -->
</AdditionalFMs>
<Features>
<Microsoft>
<Feature>CODEINTEGRITY_TEST</Feature>
<Feature>PRODUCTION_CORE</Feature>
<Feature>BOOTKEYACTIONS_RETAIL</Feature>
</Microsoft>
<!-- Insert OEM\SOC features here
<OEM>
<Feature>xxx</Feature>
</OEM>
-->
</Features>
</OEMInput>
Nice guide works perfect on Lumia 925 spoofed to 950 XL.
I've made the changes to the oeminput.xml that are shown here, for my Lumia 1520. Now when I run Phone Update, it briefly shows that updates are available for Windows 1703 (the updates are dated 2019 04), then displays an error message code 0x80070002. This has only happened since I changed the oeminput file, so I think I may have some value or other within it set incorrectly. I've got my language and time locales set to my region. For the other variables I used:
<SOC>MSM8974</SOC>
<Resolution>1080x1920</Resolution>
Are these correct for the 1520? Is there something else I should be looking at to get the updates to work? Many thanks in advance for any help with this.
2019 and it still works
thank you
I have used Nokia 920 and sat 950xl name ...but when I download the update than server say Error code: 0x80070273...so How can I solve it please help me? How I solve
I get an error trying to copy oeminput.xml to the destination directory on the phone. Something I need to do to grant permissions? Or use some tool other than Windows Explorer on the PC? I can navigate to that directory and view contents.
[edit]: found solution, just needed to turn on a couple more switches in the Unlock portion of the Interop Tools app, then it worked.
bigomod said:
Nice guide works perfect on Lumia 925 spoofed to 950 XL.
Click to expand...
Click to collapse
Hi, are you on 1703 or 1709 or did you dump your nokia phone...
I have a Nokia 925 and I try this guide
I changed the OEMInput.xml and could replace it on the filesystem
I am already on 1703, but then i get this Windows Phone Update Error 0x80070273
I have set 4 Registry fake Keys.
PhoneManufacturerModelName RM-1085_11302
PhoneManufacturer MicrosoftMDG
PhoneModelName Lumia 950 XL
PhoneHardwareVariant RM-1085
ant0nwax said:
Hi, are you on 1703 or 1709 or did you dump your nokia phone...
I have a Nokia 925 and I try this guide
I changed the OEMInput.xml and could replace it on the filesystem
I am already on 1703, but then i get this Windows Phone Update Error 0x80070273
I have set 4 Registry fake Keys.
PhoneManufacturerModelName RM-1085_11302
PhoneManufacturer MicrosoftMDG
PhoneModelName Lumia 950 XL
PhoneHardwareVariant RM-1085
Click to expand...
Click to collapse
Resetted Phone:
Nokia Lumia 925
Windows 10 Mobile 1703
Update 2019-06B for 1703 arrives and still get 0x80070273
Planned steps:
- Interop Tools and Dependencies Installation
- changing Registry to Nokia Luima 950 etc.
- checking XML File maybe correct
- trying Update agian

WP backup file of cancelled prototypes made by Nokia/Microsoft

NOTIFICATION : DONT FLASH,RESTORE EMMC BACKUP FILE OF PROTOTYPE TO YOUR RETAIL DEVICE. IT VERY DAMAGE
Rx112: https://onedrive.live.com/?authkey=!AMMXWNS0CVaIx7A&id=9BEC8AA0062F7BD6!141944&cid=9BEC8AA0062F7BD6
Rx100 : https://forum.xda-developers.com/windows-10-mobile/wp8-0-rx100-t3954941
Rx130: https://mega.nz/#F!mGQ3kYCD!PYYx6Y8FtnRHDMzxX16SUw
win10mobie arm64bit: https://forum.xda-developers.com/windows-10-mobile/arm64-uefi-rx130-t3778025
converted to 950xl fw: https://drive.google.com/file/d/1oRwZvXYxAKiN9xCSdYG-69PPylM6GUt6/view?usp=sharing
920 b1 : https://drive.google.com/file/d/1peKXuSPcr9Hn8TdPkKxoP0RDd5AVedO-/view?usp=sharing
650xl : https://drive.google.com/open?id=1SThRj7QsX9KsjUUUUl0EECP4NKyARsY1
950 b1: https://mega.nz/#F!zCQGkawI!Iau0OKKY02HjXy2r56iW-Q
Goldfinger : not public
McLaren:
I cant share it without permission of guy have it
435/532
android:
435: https://mega.nz/#!zZlmTYgK!o8w3tGd3_OtiqNtX5A620Nleg8apPVqeYVGo6JliPPQ
532: https://mega.nz/#!WE9m3K5S!AnuCmmizOAhqB6JuEvGbmmyVj9bwpAybDQVPOZRtMBA
WP :
532 4gb : https://drive.google.com/file/d/15Gz6IfBPL1LiJcphQbEEVYIqX7uwl1Se/view
532 8gb: https://drive.google.com/open?id=1WvLnf3vkYo86bMsm_NQTF1nKWxvIoCfV
435 8gb: https://drive.google.com/file/d/1U0QyJH3cugct2D79wcHjmI_V-u9VDize/view?usp=sharing
Clippr will meltemi os: https://mega.nz/#F!Z55gGSiC!eBFE3nNLwcP62v2YIPHVrQ
...
If someone have prototype with incomplete system. Try found at here and flash it. Dont forget backup special partition via win32disk image,partition guru,winhex,etc.
dont try install win10mobi arm64 for rx130.very early, make damage for hardware
For ffu of goldfinger,i will upload tomorrow
updated ffu file for goldfinger
Updated full emmc backup of rx112 midas- first 3d touch prototype of nokia
I will update
Full backup + ffu of
Rock Alt 530 5 inch
Saimaa CDMA
Fame 4GB
Hi, I didn't know that you have an archive for prototype firmware here! Good Job!
Well, the McLaren though, it seems to be quite tricky. But we will see...
mivas said:
Hi, I didn't know that you have an archive for prototype firmware here! Good Job!
Well, the McLaren though, it seems to be quite tricky. But we will see...
Click to expand...
Click to collapse
Haha
For mclarne gdr2. I waiting another friend,guy installed it on his phone
But i busy
link for rx112 not work, can you reupload? thanks.
thinhx2 said:
Haha
For mclarne gdr2. I waiting another friend,guy installed it on his phone
But i busy
Click to expand...
Click to collapse
ok good! :good:
Today i got news from my friend:
That person likes to display information with various models
At the same time, it also provides high paid flashing and upgrading services.
So i will remove gild finger firmware
thinhx2 said:
Today i got news from my friend:
That person likes to display information with various models
At the same time, it also provides high paid flashing and upgrading services.
So i will remove gild finger firmware
Click to expand...
Click to collapse
Hi, I just saw this post... (I don't get email notifications although I choose to be informed immediately...)
So, this is the same for the McLaren as well? ffu conversion is not available?
mivas said:
Hi, I just saw this post... (I don't get email notifications although I choose to be informed immediately...)
So, this is the same for the McLaren as well? ffu conversion is not available?
Click to expand...
Click to collapse
sorry, i cant make ffu for it, it have journal bug when convert to ffu, i dont know why
thinhx2 said:
sorry, i cant make ffu for it, it have journal bug when convert to ffu, i dont know why
Click to expand...
Click to collapse
ok... Still, the aim is to push it to W10M, so if you manage to get an image with W10M, even without touch, I would be interested in that image instead.
Then, maybe we find a way to get the standard touch back, perhaps with newer W10M updates (eg tricking it as a different device, thus restoring the "normal", non-3Dtouch updated files) or in the worst case, we could perhaps find a workaround with the drivers...

Categories

Resources