So, here's the error I get (per the phone screen): "E:\Update package is older than the current build, expected a build newer than timestamp 15107775026, but package has a timestamp 1510540413 and downgrade not allowed."
I think their QC department is a local elementary school. How can the timestamp on a file released today be older than a timestamp on a file released a month ago?
dafuq? I'm getting exactly the same error. idiots!
flash the whole image
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
IINexusII said:
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
Click to expand...
Click to collapse
anyone has the OTA for those on DP2?
I'm not on DP2 and mine won't sideload either.
c:\android-sdk\platform-tools>adb sideload taimen-ota-opm1.171019.011.zip
serving: 'taimen-ota-opm1.171019.011.zip' (~0%) adb: failed to read command: No error
Click to expand...
Click to collapse
IINexusII said:
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
Click to expand...
Click to collapse
if you edit the flash-all script it will not wipe anything
The issue is that the build that they used is older. Look at the numbers. .11 is the final and .12 is the beta. My guess is there was an issue in the beta build so they rolled it back .
Sent from my Pixel 2 XL using Tapatalk
Mikulec said:
if you edit the flash-all script it will not wipe anything
Click to expand...
Click to collapse
This is a stupid question, but I've never edited the flash-all file before. Do you just edit out the -w in notepad and save it? Or do I need something else to edit it?
Thanks!
EMcTx said:
This is a stupid question, but I've never edited the flash-all file before. Do you just edit out the -w in notepad and save it? Or do I need something else to edit it?
Thanks!
Click to expand...
Click to collapse
thats all you need to do.
just make sure the flash-all you run is the version you edited.
Flash all.bat is the easiest way
Mikulec said:
if you edit the flash-all script it will not wipe anything
Click to expand...
Click to collapse
True, but if you have to unlock the bootloader to flash then it will wipe regardless.
If bootloader is already unlocked then this will work.
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
you can do it now if you want to, flash the factory images.
else, wait for the OTA to come from Google.
Ops sorry I wrote unlocked but meant LOCKED!!!!
Can I flash factory images with locked bootloader without wiping data?
thegios said:
Ops sorry I wrote unlocked but meant LOCKED!!!!
Can I flash factory images with locked bootloader without wiping data?
Click to expand...
Click to collapse
No.
uicnren said:
No.
Click to expand...
Click to collapse
So I need to wait a specific ota from Google for those on DP2?
thegios said:
So I need to wait a specific ota from Google for those on DP2?
Click to expand...
Click to collapse
yes.
Thanks.
I thought that those on DP2 would get ota before the others...
thegios said:
Thanks.
I thought that those on DP2 would get ota before the others...
Click to expand...
Click to collapse
That's what I thought myself.
Anywho, what's the difference between DP2 and Final? Want to know if it's worth the time and effort.
Related
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
I need to return my pixel, so i need stock recovery, and to remove twrp. i searched and searched for an answer, but I can't find anything. Any advice would be very much appreciated. thanks!
Abbieru said:
I need to return my pixel, so i need stock recovery, and to remove twrp. i searched and searched for an answer, but I can't find anything. Any advice would be very much appreciated. thanks!
Click to expand...
Click to collapse
Download the factory image from Google and either fastboot flash the boot image, or use the flash_all script.
cam30era said:
Download the factory image from Google and either fastboot flash the boot image, or use the flash_all script.
Click to expand...
Click to collapse
thanks sooo much. do i just extract the boot image from it? and do i wipe the boot image first? what commands do i use?
Abbieru said:
thanks sooo much. do i just extract the boot image from it? and do i wipe the boot image first? what commands do i use?
Click to expand...
Click to collapse
Follow the directions in this thread > https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
cam30era said:
Follow the directions in this thread > https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
for the factory image, do i need one with certain letter combo? none of them match mine..
Abbieru said:
for the factory image, do i need one with certain letter combo? none of them match mine..
Click to expand...
Click to collapse
I'd suggest flashing the full factory image, using the flash-all script. Make sure your ADB and fastboot are up to date. Download the latest, NOF26V.
cam30era said:
I'd suggest flashing the full factory image, using the flash-all script. Make sure your ADB and fastboot are up to date. Download the latest, NOF26V.
Click to expand...
Click to collapse
i just did it. there is no recovery.img it in the archive it said.. what do i do now? :c
Abbieru said:
i just did it. there is no recovery.img it in the archive it said.. what do i do now? :c
Click to expand...
Click to collapse
Stock recovery is part of the boot image.
cam30era said:
Stock recovery is part of the boot image.
Click to expand...
Click to collapse
it said parition b doesnt exist and failed. i hope i didnt brick it im a newbie at this so this feels tedious..
Abbieru said:
it said parition b doesnt exist and failed. i hope i didnt brick it im a newbie at this so this feels tedious..
Click to expand...
Click to collapse
Were you using the flash-all script?
cam30era said:
Were you using the flash-all script?
Click to expand...
Click to collapse
yes. i tried booting, my phone is bricked. i dont know what i did wrong.. i need to return this so i dont know what to do
Abbieru said:
yes. i tried booting, my phone is bricked. i dont know what i did wrong.. i need to return this so i dont know what to do
Click to expand...
Click to collapse
I don't understand your answer. Did you use the flash-all script, or try to flash only the boot image?
Abbieru said:
yes. i tried booting, my phone is bricked. i dont know what i did wrong.. i need to return this so i dont know what to do
Click to expand...
Click to collapse
Why do you think you're phone is bricked. Did you run the flash all as you were instructed. Those errors you mentioned are normal.
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Solved: Always unlock_critical when unlocking your bootloader! Some say it's optional but it can/will lead to problems!
rank78 said:
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Click to expand...
Click to collapse
Did you extract the factory image? And then place all those files in the platform-tools folder?
Badger50 said:
Did you extract the factory image? And then place all those files in the platform-tools folder?
Click to expand...
Click to collapse
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
Shouldn't all those files be in the platform tools folder?
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
I agree as well. Isn't those files suppose to be in the root folder of platforms tools folder
Put those files in that folder and do the commands again. Should work
Badger50 said:
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
Click to expand...
Click to collapse
Dirty. I'll try doing that in the morning.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
Yes but kept them in a folder so you guys can see.
TonikJDK said:
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
Click to expand...
Click to collapse
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Nevermind, wrong thread. Sorry
rank78 said:
Dirty. I'll try doing that in the morning.
It won't matter, if you haven't done the command...fastboot flashing unlock_critical
Your not going to be upgrading everything with the factory image unless you try to flash them individually. Which probably still won't work without the updated bootloader.
Yes but kept them in a folder so you guys can see.
Yep, they'll need to go in the platform-tools folder.
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Click to expand...
Click to collapse
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Badger50 said:
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Click to expand...
Click to collapse
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
Amen to that bro! ????
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
This. When I first unlocked my bootloader I didn't see to unlock critical, and when I saw afterward it was said to be unnecessary. I'll start from scratch and report back. Sigh.
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
rank78 said:
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
Click to expand...
Click to collapse
I still use TiBu to restore the data on all my user apps. Google just doesn't quite do all of that just yet
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
dd66 said:
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
Click to expand...
Click to collapse
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Badger50 said:
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Click to expand...
Click to collapse
Solved. (ran fastboot oem-info)
Thanks anyway
I haven't rooted my device since like 3 devices ago. i'm looking into it for this one, but i'm afraid that i'll have to uninstall magisk to perform an OTA. is this the case? or will OTAs go through with magisk in there? and if it does't prevent it, will i have to re-root after OTA?
It will stop OTAs, last time I tried.
reinaldistic said:
I haven't rooted my device since like 3 devices ago. i'm looking into it for this one, but i'm afraid that i'll have to uninstall magisk to perform an OTA. is this the case? or will OTAs go through with magisk in there? and if it does't prevent it, will i have to re-root after OTA?
Click to expand...
Click to collapse
Flashing anything other than official flash alls in bootloader or twrp will make OTAs fail. There are mixed success stories with people flashing all back to stock with an official flash all from Motorola to get OTAs.
Unseeablething said:
It will stop OTAs, last time I tried.
Click to expand...
Click to collapse
Uzephi said:
Flashing anything other than official flash alls in bootloader or twrp will make OTAs fail. There are mixed success stories with people flashing all back to stock with an official flash all from Motorola to get OTAs.
Click to expand...
Click to collapse
how do you update then?
Uzephi said:
Flashing anything other than official flash alls in bootloader or twrp will make OTAs fail. There are mixed success stories with people flashing all back to stock with an official flash all from Motorola to get OTAs.
Click to expand...
Click to collapse
reinaldistic said:
how do you update then?
Click to expand...
Click to collapse
"There are mixed success stories with people flashing all back to stock *snip* to get OTAs"
Uzephi said:
"There are mixed success stories with people flashing all back to stock *snip* to get OTAs"
Click to expand...
Click to collapse
you already said that lol, is there any guaranteed update path?
reinaldistic said:
you already said that lol, is there any guaranteed update path?
Click to expand...
Click to collapse
Yes, in theory, an official flash all and following the flashfile.xml instructions should put you back to a state where OTAs will go through. Some people have said it didn't work for them. It always has for me, so YMMV.
Uzephi said:
Yes, in theory, an official flash all and following the flashfile.xml instructions should put you back to a state where OTAs will go through. Some people have said it didn't work for them. It always has for me, so YMMV.
Click to expand...
Click to collapse
Where can one find the OFFICIAL MOTOROLA flashall????
blake .l said:
Where can one find the OFFICIAL MOTOROLA flashall????
Click to expand...
Click to collapse
Android file host user "Motorola firmware team" releases official flash all files for us variants
Uzephi said:
Android file host user "Motorola firmware team" releases official flash all files for us variants
Click to expand...
Click to collapse
I found the Z2 Play but not the Z2 Force, is the play compatible??
blake .l said:
I found the Z2 Play but not the Z2 Force, is the play compatible??
Click to expand...
Click to collapse
Go into the Z2 play folder. Download the correct NASH file you need. MFT was too lazy to make our own folder.
Uzephi said:
Go into the Z2 play folder. Download the correct NASH file you need. MFT was too lazy to make our own folder.
Click to expand...
Click to collapse
I notice no flashall is provided, do I use your flashall to flash??
blake .l said:
I notice no flashall is provided, do I use your flashall to flash??
Click to expand...
Click to collapse
Just open the flashfile XML and run those commands if you're trying to go back to stock for ota
Uzephi said:
Just open the flashfile XML and run those commands if you're trying to go back to stock for ota
Click to expand...
Click to collapse
Do I need a certain program to open the XML file? I believe its opening with windows explorer now, Also what commands do I run? all I see is just a bunch of writing, never messed with an XML file before. any tutorials for flashing this way?
downloaded NASH_TMO_C_OCXS27.109-51-4_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml and the tmo flashall, still downloads the update file but fails at some point when installing it, if i can figure out how to run the flashfile XML commands maybe that will fix the problem.... Advice on how to run those commands will be very appreciated...