Related
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!
Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol
Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...
Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip
If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE
sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.
With the stock rom, can I just flash it using a custom recovery?
yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.
Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download
I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
Thanks for the info. Will give it a try.
bumping this up b/c 5.1 is coming soon!!!!
JulesJam said:
bumping this up b/c 5.1 is coming soon!!!!
Click to expand...
Click to collapse
Any link that says so?
Sent from my XT1095
Hopefully there's some Verizon love
AGISCI said:
Any link that says so?
Click to expand...
Click to collapse
http://www.droid-life.com/2015/05/0...droid-5-1-updates-here-are-the-release-notes/
Why? What is wrong with ota?
lobango said:
Why? What is wrong with ota?
Click to expand...
Click to collapse
Nothing is wrong with it. The point in getting the fxz is that it will be a full image that we can share.[emoji2]
Sent from my XT1095
i saw this on gsm arena.
http://www.gsmarena.com/motorola_posts_android_51_release_notes_for_1st_and_2nd_gen_moto_x-news-12165.php
nevermind
bump!
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
jcracken said:
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
Click to expand...
Click to collapse
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
JulesJam said:
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
Click to expand...
Click to collapse
But that shouldn't preclude the second option of manually flashing the img files, right? Can someone post the FXZ? I'd like to try this.
jcracken said:
But that shouldn't preclude the second option of manually flashing the img files, right?
Click to expand...
Click to collapse
Correct.
jcracken said:
Can someone post the FXZ? I'd like to try this.
Click to expand...
Click to collapse
Nobody has that yet. That is the whole point of this thread - to get people to use MDM so that we will have the fxz for all of the devices.
MDM won't update the devices until the OTA is pushed. But if your phone has started to download the OTA, MDM will say an update is in progress so it won't download the files.
What I am saying is that people should not take the OTA - disable MotorolaOTA - and use MDM to update to get the fxz.
bump
JulesJam said:
bump
Click to expand...
Click to collapse
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Steve-x said:
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Click to expand...
Click to collapse
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
JulesJam said:
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
Click to expand...
Click to collapse
Very cool, and very useful.
bump!
DO NOT RESTORE BACK TO 4.4. THIS WILL BRICK YOUR PHONE.
--UPDATE--
JUST FLASH THIS! (In stock recovery) https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view
--
(if the above doesn't work, or if you are not on totally stock, use the following method)
Here is how to upgrade from 23.11.14 to 23.16.3
What you need: https://yadi.sk/d/cBaKACE7hQH9Y (upgrade from stock 5.0 to 23.16.3)
http://www.graffixnyc.com/motox.php (stock 5.0 image. You need to use this one. The one found in Motorola's site WILL NOT WORK WITH THIS METHOD)
Unzip the stock 5.0 image
Boot into fastboot
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Boot into recovery
adb sideload Blur_Version.22.21.11.victara_tmo.tmo.en.US.zip
reboot!
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Grzesiek1010 said:
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Click to expand...
Click to collapse
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
bongostl said:
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
Click to expand...
Click to collapse
ok but what with all apps data setting ?
Grzesiek1010 said:
ok but what with all apps data setting ?
Click to expand...
Click to collapse
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
bongostl said:
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
Click to expand...
Click to collapse
better wait for official update too much risk lost data ...
I successfully downgraded to 5.0, and I've attempted the sideload method twice and failed. Each time it says there is an error in the package, status 7. I get the same result when I apply update from sd card. Any ideas?
---------- Post added at 12:25 PM ---------- Previous post was at 11:43 AM ----------
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Use the files I posted.... That's what I used
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
leffer said:
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
Click to expand...
Click to collapse
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
sivarticus85 said:
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
Click to expand...
Click to collapse
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
leffer said:
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
Click to expand...
Click to collapse
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Success!
Stanleywinthrop said:
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Click to expand...
Click to collapse
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
thenestor said:
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
thanks for your help. I tried to download from your link and for some reason the file will not extract. However, I noticed that your image file is named exactly as the image file linked in the OP to this thread. Are they one in the same?
sivarticus85 said:
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Click to expand...
Click to collapse
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
thenestor said:
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
Good catch! I have fixed the original post
Stanleywinthrop said:
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
Click to expand...
Click to collapse
I've updated the original post to make this clearer.
anyone able to root this new OTA?
CF auto root was working on every previous OTA from 4.4 to 5.0 and 5.1 but now causes boot loops. I am able to TWRP back to the unrooted build to get me out of the bootloops.
leffer said:
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
Click to expand...
Click to collapse
Thanks! And no, the name is normal. The OTA filename always states the version you need to be on to install it, not the version that it contains.
Is up on Google developer website. MMB29V
https://dl.google.com/dl/android/aosp/shamu-mmb29v-factory-0b4a53f0.tgz
Edit: No change in bootloader or radio.
Thank you for upload. my work blocks google dl but not drive for some reason XD
Has anyone been able to get the checksum to verify? the MD5 for me doesn't match from the link provided or the Google image page.
just tried as well off the Google image page..MD5 does not match :|
I just downloaded from the stock images page also and the MD5 matches for me.
They just changed the MD5 code to match the factory image I downloaded. The new one matches my image.
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
murtaza02 said:
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
Click to expand...
Click to collapse
What build are you on now?
holeindalip said:
What build are you on now?
Click to expand...
Click to collapse
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
murtaza02 said:
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
Click to expand...
Click to collapse
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
Will do and report back.
Stupid question, but does Google post changelogs?
Other than the security patch, could anything else have changed?
Sent from my Nexus 6
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
cam30era said:
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
That's some pretty detailed stuff!
Thanks man.
The factory image just finished downloading, I will report back in about 10 minutes.
Sent from my Nexus 6
---------- Post added at 07:17 PM ---------- Previous post was at 07:02 PM ----------
@cam30era
Thanks so much!
It worked. I flashed it and wiped cache in stock recovery. It's Optimizing apps now, and should be done soon!
cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
That's what I was getting too just wanted to make sure he was at least on 6.0
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
murtaza02 said:
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
Click to expand...
Click to collapse
Kernel is included in boot.IMG with other files.
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
wrydgj said:
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
Click to expand...
Click to collapse
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
harpin14789 said:
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
Click to expand...
Click to collapse
I asked about recovery.img, I know that boot.img has to be flashed. Nevermind, I flashed both of them, just in case, and twrp after all flashes[emoji6]
Sent from my shamu using Tapatalk
What I find funny is that some of the patches are not even included in the update but in the updated binaries.
Also there were changes to the kernel. A few of the issues were kernel issues.
I currently have the 1.16.40.763 stock firmware on my ZE550KL laser zenfone 2. Before I update the firmware or root it, I want to ensure that I can go back to this version of stock firmware. To do that i need the 1.16.40.763 stock recovery.img file.
Can someone/anyone please tell me how to find it on my phone or how to extract it from the firmware file on asus.com (I can't find it on the official update file on asus.com).
Thanks
I really need it too, so if someone knows where I could find it ! Thank you in advance
I finally found the stock recovery .img / it was posted on an another thread here : https://github.com/sabpprook/android_device_asus_ze500kl/releases
sorry it is for the ze500kl, my bad
Anyone know how to find or create the stock recovery.img for a Zenfone 2 Laser ZE550KL?
heywheelie said:
Anyone know how to find or create the stock recovery.img for a Zenfone 2 Laser ZE550KL?
Click to expand...
Click to collapse
Here you go.
https://drive.google.com/file/d/0B8346PsUO8X8VFVPUXVjMFlwWms/view?usp=drivesdk
In any case, if you encounter any errors, such as that the build date of the software on your device is newer than the one you are trying to flash when attempting to downgrade, you have to delete the system partition first to get rid of the build.prop
To do this, simply head over to FASTBOOT mode, and type the command,
fastboot erase system
Rizzed said:
Here you go.
https://drive.google.com/file/d/0B8346PsUO8X8VFVPUXVjMFlwWms/view?usp=drivesdk
In any case, if you encounter any errors, such as that the build date of the software on your device is newer than the one you are trying to flash when attempting to downgrade, you have to delete the system partition first to get rid of the build.prop
To do this, simply head over to FASTBOOT mode, and type the command,
fastboot erase system
Click to expand...
Click to collapse
Thanks but I should have mentioned that I was after the recovery.img from the 1.16.40.763 firmware.
heywheelie said:
Thanks but I should have mentioned that I was after the recovery.img from the 1.16.40.763 firmware.
Click to expand...
Click to collapse
Yeah, I noticed it too. I had already updated it. Do check it out though.
Rizzed said:
Yeah, I noticed it too. I had already updated it. Do check it out though.
Click to expand...
Click to collapse
So that recovery.img is actually the stock recovery for the 1.16.40.63 firmware?
heywheelie said:
So that recovery.img is actually the stock recovery for the 1.16.40.63 firmware?
Click to expand...
Click to collapse
Yeah.
Rizzed said:
Yeah.
Click to expand...
Click to collapse
Great thanks
Plz help me to find stock recovery image of asus ze550kl of 1.17.40.1531.xx
Rizzed said:
Here you go.
https://drive.google.com/file/d/0B8346PsUO8X8VFVPUXVjMFlwWms/view?usp=drivesdk
In any case, if you encounter any errors, such as that the build date of the software on your device is newer than the one you are trying to flash when attempting to downgrade, you have to delete the system partition first to get rid of the build.prop
To do this, simply head over to FASTBOOT mode, and type the command,
fastboot erase system
Click to expand...
Click to collapse
Hey, Can you re-upload it again please? Thank you so much..