I know that Acer pulled today's update, but will it be possible to switch when it is released again?
Leaked 3.1 to official 3.1
Yes it is, just a little confusing though. You have to know which region your tablet is from http://secure3.tx.acer.com/FindSystem/FindSystem.aspx?title=Information About Your System. And then go about flashing a couple of ROMs to get you ready for the update. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1155664
I am a total noob and wasted my whole day yesterday trying to figure this out. In the end texonex helped me out. Starting with the leaked 3.1 update here's what I did (courtesy texonex):
1. Root the device (http://forum.xda-developers.com/showthread.php?t=1138228). Download Acer Recovery Installer from the market, and from there install the clockwork recovery image. Choose no for a backup of the current recovery.
2. Download the backup file for 1.104.02 here, thanks to camelot1972
dl.dropbox.com/u/34113636/2011-06-24.12.20.13.zip, I guess you could also use the file from here: http://forum.xda-developers.com/showthread.php?t=1113878. This is for the US version.
If your tablet is from another region you would have to find the appropriate "default" version number in the how-to (what firmware is right for my country).
3. Extract the contents from the zip file and put them in the backup folder for clockwork mod on your SD card (take your SD card out of the tablet and connect directly for all the steps), if you do not see the backup folder, I suppose you can make one,e.g. [micro sd]\clockworkmod\backup\2011-06-25.22.14.07. I guess this exact string will still show up in clockwork recovery. I made a backup of the leaked 3.1 and that gave me the folder, and I just replaced the files. The date part is obvious in the name however I wouldn't venture a guess what are the other digits in the folder name.
If you downloaded the file from [OTA] Full Package and Update page, you'll need first to decrypt the file using the decrypter and then extract the contents of the decrypted file. One of the extracted files is update.zip which goes on to the SD card no subfolder in this case.
4. Restore the firmware using CMW using full restore for the US version, or update from the sd card zip if using a full package zip file.
At this point I think you need to save the recovery image for the non-US versions. Follow the instructions in the how-to or just use acer recovery installer to flash the clockword recovery again and this time choose yes to backup the current image.
5. Download 1.104.02 to 1.141.07 update and flash it with CMW.
Or the appropriate latest update file from your region(highest version number).
6. Flash recovery image to 1.141.07, this is option 4 in Acer recovery installer.
For non-us versions restore the recovery image, unroot and restore factory defaults.
7. I stopped here and now am waiting for the OTA. According to the how-to, you roll back to the full defualt package by using the standard ACER recovery (Power + -Vol) after copying the zip file on to the SD card, delete the zip file copied before.
8. Go to settings and trigger update manually. OTA will prompt you the new 3.1 update. I suppose you do not need to unroot.
You can also install the stock ROM from here:
http://forum.xda-developers.com/showthread.php?t=1159443
Thanks to Bec07 (how-to), vache (stock roms) and sc2k (un-rooting) for their contributions or I would have been totally lost in trying to downgrade my tablet from the leaked 3.1. Hope this is helpful, and goes smoothly because if it does not I wouldn't have clue how to fix it.
Sorry for this off-topic post, but you said that acer pulled the update: And I still have it (haven't updated and cant anyway). Is this not right?
What I meant was its not being pushed to more users for now.
Hello All,
hoping your tolerance for newbs to the K1 world hasn't been exhausted yet. I am so much more familiar with doing this on my HP Touchpad side.
I am currently running on my dad's K1:
Build date Thu Aug 9 15:13:28 EDT 2012
Build # cm_k1-userdebug 4.0.4 IMM76L eng.administrator.20120809.151251 test-keys
(from cm-9-20120809-UNOFFICIAL-k1.zip)
I haven't had any luck using ADB from the computer, but I can NVFLASH and I can get into recovery via Rom Manager.
I downloaded CWM_K1_ICS_AOSP_Rooted_R2.zip with the intent of flashing it, but it does not show up as a flashable rom from recovery. It is in the exact same directory as the cm-9-20120809-UNOFFICIAL-k1.zip file which does show up so it isn't a matter of being in the wrong directory anything like that.
I'm not sure why the file is not showing up.
When I go to Rom Manager to "Flash ClockworkMod Recovery" - I get prompted with "Confirm Phone Model" and Asus:Transformer is listed. I thought this build already had CMW installed so not quite sure why the prompt. Do I want to confirm the model # even though it is wrong? I'm not really sure what steps to take here.
Another option is "Check for Rom Updates" which shows 9-20120809-UNOFFICIAL-k1" as my current rom. Selecting this results in a dialogue box - Flash ClockworkMod Recovery You must have ClockworkMod Recovery installed before continuing install the recovery through ROM Manager first. Cancel/Install options are listed and I've been just hitting cancel. Do I want to Install? I've been hesitant because I thought CWM was already installed based on being able to boot into recovery.
When I boot to recovery via Rom Manager (ADB won't recognize the tablet still from PC), I see CWM - based Recovery v6.0.1.0 - which again confuses me as to why Rom Manager would tell me I need CWM installed before it can flash roms since this once again suggests to me that I was right initially and that CWM is installed already (though that begs the question - why doesn't Rom Manager recognize CWM as already being installed?).
So in a nutshell - any ideas what I need to do or am doing wrong to install the R2 release non-destructively? I'd prefer to get it working through CWM, but if I download the NVFLASH version and do it from AXP mode and the PC - will that be non-destructive or does it perform a tablet wipe?
thanks again for assistance.
UPDATED INFO - figured part of the problem...
So I downloaded the R2 image and it went to my dad's Download directory - didn't realize that he has 2 directories with same name - one being internal and other being external. When I moved the download from the internal default download directory to the external one with the same name to comply with "1. Download one of the CWM_K1_*.zip versions and move to external sdcard" - recovery CWM was able to see the zip file now and let me flash the CWM_K1_ICS_AOSP_Rooted_R2.zip.
Seems to have flashed fine - but question (lol don't answers always result in more questions) - is after flashing I'm not sure if this is a downgrade or upgrade. I see the Build # is now K1-userdebug.4.0.4.IMM76L.eng.administrator.20120731.061506 test-keys which is earlier than the 9-20120809-UNOFFICIAL-k1. I also noticed it went back to the old logo on bootup instead of the Android good/bad robot graphics.
Neil
Thread Moved​
This can not be considered development, please post in the correct section​
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
Hi. I installed ROM Manager from the Play store and also paid for ClockworkMod Touch mode inside the app. Within the app I installed ClockworkMod Recovery which seemed to be confirmed however upon recovery reboot I had no option to backup and no indication that it was not the standard recovery reboot interface. I tired that several times. I then flashed the CWM_6.0.4.7_Touch_GT-I9505 tar file (from the official ClockworkMod website) using Odin. Now, I do have the proper recovery reboot with all the options and ClockworkMod branding /touch capability.
Within the app now however I have the status 'current recovery: ClockworkMod 5.X.X.X. and i am notified upon opening the app that a newer version is available. This is despite the fact that when I review 'Recovery already installed' I get the status 'ROM Manager has been set up to use your existing recovery installation'. This happens when I click 'jflte' as my phone model - the only one listed (which I'm not sure it is), or, 'device not listed above'.
The second backup I have made has been timestamped 31 December 1979 23:00 (not the name of the file which is 1970-10-15.14.68). I'm pretty sure the first backup which I deleted was actually timestamped 1970.
I am a noob and have sort of accidentally got into this and spent time I don't have however I would be very grateful to learn:
1/Do I need the ClockworkMod app? Is the flash I did with Odin enough? How do the two relate? Co-exist? and is the imprecision within the app about the version in use a problem?
2/What's up with the incorrect timestamping? How can I fix this?
3/ General question - could anyone summarise the difference between /mnt/sdcard or extSdCard and /storage/sdcard or exSdCard which is a distinction I have broadly come across since rooting?
Thanks for reading. If I have posted in the wrong section please advise/moderate. I've looked within the app and on the Play Store /web for ROM Manager specific support however I can't find an obvious forum/contact. Again, please point out if I am missing it and direct me.
Best wishes.
In order to get on with my life I simply flashed the latest TWRP recovery using Odin. I have successfully made a backup from recovery reboot.
- Is there anything I can do to check I don't have problems given I did nothing to remove CWM and assumed TWRP would flash 'over' it?
- Does anyone actually vouch for the TWRP Manager app? Play reviews are mixed...
^^^^
You will have No problem with flashing TWRP over CWM.
I have never used an app for twrp or cwm in 3 years of android. I guess you dont need them.
Gesendet von meinem GT-I9505 mit Tapatalk
I was able to create a TWRP backup of the ota after I installed it on my Moto X XT1095. I was able to flash this using TWRP from kitkat.
After flashing this, you will have the new ota, however it will not have the new baseband (you will retain the original baseband from your previous installation, in other words this does not include the modem). I believe that you should be able to flash this to any one of the XT variants as long as you are able to flash a custom recovery (in this case TWRP, I used 2.8.1.0 if that matters)
I had to create new folders on the internal storage due to the fact that I was unable to create a backup of kitkat. All I did was create a new folder on the internal storage called TWRP, inside that folder I created a folder called BACKUPS within that folder I created a folder that has the unique alpha-numeric name to each device, and finally in that folder I placed this backup file. TWRP/BACKUPS/unique alpha-numeric name/2014-11-09--11-34-04 LXE22.39-5. Then I booted to my TWRP recovery performed a factory data reset along with wiping cache and dalvik, then performed the restore.
If you don't know what your unique alpha-numeric folder name is, you can find this by booting to twrp and try to perform a backup (this is how I found out what my folders name was). I got an error, within that error was the path (it is verbatim and case sensitive).
If anyone wants to try this, here is the link.
Unzip and place in the folder I described.
22.39-5 OTA
https://mega.co.nz/#!3QNmBJZD!6wRby9lwl2gWI0Lxtwq1sKZ7DGGYAs7vtP44GmZZwBQ
MD5-63a4a2eb969c1d37b543f17dec3a64e1
22.39-6 OTA
https://mega.co.nz/#!rdEVmKIR!9wt03nACOf_Gbwt1FzXwnmKkg9lcrCcQqBtlqBZMCTI
MD5-1288b96e0b90d02273ed4f2f4235273d
Let me know how it goes. I won't be able to offer much help other than what is provided here, if I have the time I will try. I hope I didn't make this to confusing. If it works for you, hit the "thanks".
Moderators, If this is not in the correct category please feel free to move it. Thanks
i appreciate you sharing this... question for u (or to make sure i understand how you tested the 5.0 Nandroid): after flashing the OTA, did you restore your 4.4.4 Nandroid (confirm it works: calls, data, etc.), factory reset and wipe and then restore your Lollipop 5.0 Nandroid (boot and confirm it works: calls, data, etc.)? thanks in advance for your reply.
cortez.i said:
i appreciate you sharing this... question for u (or to make sure i understand how you tested the 5.0 Nandroid): after flashing the OTA, did you restore your 4.4.4 Nandroid (confirm it works: calls, data, etc.), factory reset and wipe and then restore your Lollipop 5.0 Nandroid (boot and confirm it works: calls, data, etc.)? thanks in advance for your reply.
Click to expand...
Click to collapse
After the inital OTA, I wanted to see if I could get back to 4.4.4 stock unrooted. I accomplished this by running the tool created by bhp090808. After that, I unrooted through supersu, I flashed the att modem found on graffixnyc site. I then flashed "MotoX(2014)_stock_install-recovery_sh" (with twrp) that 0.0 provided in post number 124 from the "[OTA ZIP] Pure Edition Lollipop 5.0" thread. Finally I flashed stock recovery to achieve a stock 4.4.4 system. Everything worked. After I confirmed that everything worked I did the ota again just to see if it would flash. It did, from there I was able to flash twrp, but after you reboot from twrp on the new ota you lose the twrp recovery....there is a new feature in the latest twrp recovery that allows you to move a file from pc to phone internal storage, that is how I was able to create the nand.
Funny thing is, you cannot create a backup from twrp with 4.4.4 but you can from the new 5.0 ota.
Hope this answered your question.
BTW, this nand is of the 5.0 just to clarify, like I said I was unable to make a nand of the 4.4.4
That's funny. I can do a TWRP backup just fine in 4.4.4.
Did you advanced->fix pemissions in TWRP?
not working
rsa 329 said:
After the inital OTA, I wanted to see if I could get back to 4.4.4 stock unrooted. I accomplished this by running the tool created by bhp090808. After that, I unrooted through supersu, I flashed the att modem found on graffixnyc site. I then flashed "MotoX(2014)_stock_install-recovery_sh" (with twrp) that 0.0 provided in post number 124 from the "[OTA ZIP] Pure Edition Lollipop 5.0" thread. Finally I flashed stock recovery to achieve a stock 4.4.4 system. Everything worked. After I confirmed that everything worked I did the ota again just to see if it would flash. It did, from there I was able to flash twrp, but after you reboot from twrp on the new ota you lose the twrp recovery....there is a new feature in the latest twrp recovery that allows you to move a file from pc to phone internal storage, that is how I was able to create the nand.
Funny thing is, you cannot create a backup from twrp with 4.4.4 but you can from the new 5.0 ota.
Hope this answered your question.
BTW, this nand is of the 5.0 just to clarify, like I said I was unable to make a nand of the 4.4.4
Click to expand...
Click to collapse
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Edit: got it ! Adb pushed it.
holtenc said:
That's funny. I can do a TWRP backup just fine in 4.4.4.
Did you advanced->fix pemissions in TWRP?
Click to expand...
Click to collapse
No, i did not. I will try that next time i downgrade. That would make things a lot easier for a person to put this in their backups.
Were you able to make a backup of your stock unrooted 4.4.4?
nineismine said:
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Click to expand...
Click to collapse
follow along with the way i accomplished unrooting. i can confirm this works, I have done it several times now with consistent success.
BTW, this is not to be flashed, rather done through the "restore" feature of the twrp recovery. By placing this folder in the backups you will be able to access it through restore.
rsa 329 said:
No, i did not. I will try that next time i downgrade. That would make things a lot easier for a person to put this in their backups.
Were you able to make a backup of your stock unrooted 4.4.4?
Click to expand...
Click to collapse
I wish... I didn't even try. I rooted and then put on custom recovery.. didn't think things through very well I suppose.
holtenc said:
I wish... I didn't even try. I rooted and then put on custom recovery.. didn't think things through very well I suppose.
Click to expand...
Click to collapse
follow along with how I unrooted, it works!
You will be able to take the ota, modem and all. I'm just guessing you have the XT1095.
rsa 329 said:
I was able to create a TWRP backup of the ota after I installed it on my Moto X XT1095. I was able to flash this using TWRP from kitkat.
After flashing this, you will have the new ota, however it will not have the new baseband (you will retain the original baseband from your previous installation, in other words this does not include the modem). I believe that you should be able to flash this to any one of the XT variants as long as you are able to flash a custom recovery (in this case TWRP, I used 2.8.1.0 if that matters)
I had to create new folders on the internal storage due to the fact that I was unable to create a backup of kitkat. All I did was create a new folder on the internal storage called TWRP, inside that folder I created a folder called BACKUPS within that folder I created a folder that has the unique alpha-numeric name to each device, and finally in that folder I placed this backup file. TWRP/BACKUP/unique alpha-numeric name/2014-11-09--11-34-04 LXE22.39-5. Then I booted to my TWRP recovery performed a factory data reset along with wiping cache and dalvik, then performed the restore.
If you don't know what your unique alpha-numeric folder name is, you can find this by booting to twrp and try to perform a backup (this is how I found out what my folders name was). I got an error, within that error was the path (it is verbatim and case sensitive).
If anyone wants to try this, here is the link.
Unzip and place in the folder I described.
https://mega.co.nz/#!3QNmBJZD!6wRby9lwl2gWI0Lxtwq1sKZ7DGGYAs7vtP44GmZZwBQ
MD5-63a4a2eb969c1d37b543f17dec3a64e1
Let me know how it goes. I won't be able to offer much help other than what is provided here, if I have the time I will try. I hope I didn't make this to confusing. If it works for you, hit the "thanks".
Moderators, If this is not in the correct category please feel free to move it. Thanks
Click to expand...
Click to collapse
You're my MF'N hero! You have no idea how much BS I was having trying to flash that OTA:
Flash OTA? Nope, some BS about unexpected this and that in modem.
Flash modem? Nope, permission denied.
Restore from Custom Recovery?? YES. Thanks man. If i could spank your thanks button 100000 times i would.
holtenc said:
You're my MF'N hero! You have no idea how much BS I was having trying to flash that OTA:
Flash OTA? Nope, some BS about unexpected this and that in modem.
Flash modem? Nope, permission denied.
Restore from Custom Recovery?? YES. Thanks man. If i could spank your thanks button 100000 times i would.
Click to expand...
Click to collapse
LOL. This message brought a smile on my Monday morning face.
I can't copy the folder to my phone. It says it's too large. How can I do it?
Make room by deleting stuff? If that's not the problem then I don't know.
Maybe try pushing the folder with adb.
Did anyone try this on the XT1092?
Thanks in advance.
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)
Unfortunately, I keep getting "invalid crc file for system.ext4.win000" when trying to copy the backup to the final destination folder. Been using Solid Explorer. I'll try another just in case.
Edit: ES File Manager worked. Also, for me, TWRP 2.8.1.0 will not backup, but 2.8.0.1 will. For what's it's worth.
holtenc said:
Make room by deleting stuff? If that's not the problem then I don't know.
Maybe try pushing the folder with adb.
Click to expand...
Click to collapse
There is plenty of space left on the SD card to copy this but it still says the file is too large. What command do I use on adb? Can you help me? Thank you.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
nineismine said:
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Edit: got it ! Adb pushed it.
Click to expand...
Click to collapse
I am having the same problem, can you help me? What adb command do I use for this?
@MaKTaiL which model of the moto x do you have?
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)
Vineet Upadhyaya said:
@MaKTaiL which model of the moto x do you have?
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)
Click to expand...
Click to collapse
XT1097, but it doesn't really matter for the problem I'm having.
adb push <file> /storage/emulated/0/
Try that.
I have found it to be a problem with twrp try copying it to a different folder and then use twrp file explorer to move it to the backup folder. That worked for