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
I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I am trying to flash an image onto a zenfone 5 using the recovery. I have tried sideloading and also pushing the zip to the SD card. It just seems to hand randomly.
I then tried checking the uploaded zip file (to /sdcard) by running md5um on it and the value changes each time I run md5sum. I have tried a few versions of the TWRP recovery and the all seem to have the same problem. Is there one that works?
I just rooted my friend's Zenfone 5 with an auto installer. Here's the link on google drive LINK . Just extract the zip and follow instructions in the "help file.txt". It's a script that automates all the commands. I don't remember where I got this from, but if someone else knows, please link the original for credits.
So it's been a while since discussion about this specific model, but I was wondering if it would be at all possible to root this with Magisk?
Since Magisk can apply root by patching boot image file, I figured it could technically be possible since in this thread:
https://forum.xda-developers.com/galaxy-j3-2016/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049
There is a link to a flashable ZIP to "access GSM" with this model phone, found here:
https://mega.nz/#!mtNEibLa!NmVJ7RM0fSDwXdD3CTKi0fVQgYdIMP6m8THRQLyJQRw
The interesting thing about it is that ZIP contains a boot.img file, so what I was wondering, would that the stock boot image file needed for Magisk?
There isn't much information about what's supplied in that ZIP nor have people mentioned it's use or anything, but I was wondering if it could at all be tested to possibly work. Or if whatever is in that ZIP is even the stock firmware.
I can't necessarily test it myself since I need my phone however, can anyone verify the contents of the ZIP or boot.img? It would be a pretty convenient if this was all it takes.
Without root I doubt you will be able to flash anything that isn't an official Samsung firmware update. And depending on which branding your device has,you may not even be able to flash firmware of any type whether it be an update or full firmware. Some carriers insist that Samsung fully lock down the bootloader thus completely crippling the device. U.S. carriers doing this are various. Especially if it is pre-paid. Best advice is to research any device before you purchase it. See if root has been achieved. If not and that device has been out for some time. Avoid it. Pick a device you know has gained root from among the choices offered by any carrier. It would seem you have one of the many locked bootloader turd phones put out by Verizon,Sprint,TRACTURD and so forth. Locked bootloader that won't recognize any flash that isn't signed. Odin or not the flash will fail. Time to flush that turd and find a better alternative.
Fivavoa said:
So it's been a while since discussion about this specific model, but I was wondering if it would be at all possible to root this with Magisk?
Since Magisk can apply root by patching boot image file, I figured it could technically be possible since in this thread:
https://forum.xda-developers.com/galaxy-j3-2016/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049
There is a link to a flashable ZIP to "access GSM" with this model phone, found here:
https://mega.nz/#!mtNEibLa!NmVJ7RM0fSDwXdD3CTKi0fVQgYdIMP6m8THRQLyJQRw
The interesting thing about it is that ZIP contains a boot.img file, so what I was wondering, would that the stock boot image file needed for Magisk?
There isn't much information about what's supplied in that ZIP nor have people mentioned it's use or anything, but I was wondering if it could at all be tested to possibly work. Or if whatever is in that ZIP is even the stock firmware.
I can't necessarily test it myself since I need my phone however, can anyone verify the contents of the ZIP or boot.img? It would be a pretty convenient if this was all it takes.
Click to expand...
Click to collapse