Here's the OTA zip extracted from 5.1 XT1527. Fully unmodified.
It patches a lot of system apps, modem and gpt.
https://mega.nz/#!ixpQyRYI!OSIzlz8OOp3VChQGSkOW-f9gdy87g6cGQZiE4MeaUrI
PsyClip-R said:
Here's the OTA zip extracted from 5.1 XT1527. Fully unmodified.
It patches a lot of system apps, modem and gpt.
https://mega.nz/#!ixpQyRYI!OSIzlz8OOp3VChQGSkOW-f9gdy87g6cGQZiE4MeaUrI
Click to expand...
Click to collapse
asks encryption key ... it is impossible to download without introducing
---------- Post added at 12:04 ---------- Previous post was at 12:02 ----------
ENRIQUEMM said:
asks encryption key ... it is impossible to download without introducing
Click to expand...
Click to collapse
Now if, after modifying the link.
Thank you
ENRIQUEMM said:
Now if, after modifying the link.
Thank you
Click to expand...
Click to collapse
Yep, I've fixed that.
Let me know if you will install it.
You patch this update yourself ?
I am leery about running it.. it patches everything you can imagine.
xpmule said:
You patch this update yourself ?
I am leery about running it.. it patches everything you can imagine.
Click to expand...
Click to collapse
Nope. Cuz I'm usin' XT1527 firmware on XT1524. So my recovery and modem are different. Thus I can't install this update.
It's untouched. Factory package, extracted from /cache partition.
ahh ok thanks
i seen it downloaded OTA to that folder on my XT1527 device too.
what about Bootloader concerns guys ?
people are talking about that on the stock firmware topic
and they linked to this topic..
and i guess just open TWRP and flash it then right ?
xpmule said:
ahh ok thanks
i seen it downloaded OTA to that folder on my XT1527 device too.
what about Bootloader concerns guys ?
people are talking about that on the stock firmware topic
and they linked to this topic..
and i guess just open TWRP and flash it then right ?
Click to expand...
Click to collapse
Actually You need fully untouched (factory origin) partitions, ie. recovery, firmware, radio, boot etc.
There shouldn't be any problem with unlocked bootloader.
if you need a stock phone then you have to use the ADB-Side Load method then right ?
and the release notes are vague from Moto
EDIT:
i can confirm the file posted on Mega is the same as the OTA update from Moto.
I got both just now and hex compared them.. using BeyondCompare (HEX)
xpmule said:
i can confirm the file posted on Mega is the same as the OTA update from Moto.
I got both just now and hex compared them.. using BeyondCompare (HEX)
Click to expand...
Click to collapse
Thanks for help. So now guys may download and flash without worries.
ya i guess i am running a different modem too.
hmm this is getting complicated hahah
at first i thought you could do a flash like i seen guys doing on a Moto G tutorial..
they backed up all with TWRP then installed stock recovery + stock firmware etc.
then connected to PC with adb fasttools and flashed it that way (have not used that method yet)
that means you put phone into fastboot connection mode and connect with stock recovery.
then the update is flashed over usb while the update is on your PC.
and in the tutorial the guy then re-flashed TWRP and restored back his data.
BUT !
This update patches every single stock apk and pretty much every aspect of the system.
including the modem !
so if you did restore your old modem then it's not patched.
and some of us have a 5.0.2 modem so hmmm
maybe it would be ok (security wise) if the 5.0.2 modem was stage fright patched too ?
When I Trying to INtall the update From TWRP got this error:
Processing OpenRecoveryScript file...
I:command is: 'install'
I:value is: '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/data/media/0'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/external_sd'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/bootdevice/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
E:Error installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Done processing script file
read what i said before.about "test-keys"
your phone was flagged.
the update knows you have custom content and refused the install
it seen you have root/super su or have a custom kernel or rom etc.
How to apply the update manually?
Hi,
I have the xt1524 bought from retail in Europe (Germany). I managed to upgrade it to stock xt1527 retus 5.1, but the stagefright update keeps on failling to install. I have the motorola drivers and adb and fastboot, also unlocked the bootloader. How can I apply this update manually?
Thanks in advance!
tomoff said:
Hi,
I have the xt1524 bought from retail in Europe (Germany). I managed to upgrade it to stock xt1527 retus 5.1, but the stagefright update keeps on failling to install. I have the motorola drivers and adb and fastboot, also unlocked the bootloader. How can I apply this update manually?
Thanks in advance!
Click to expand...
Click to collapse
You simply can't install this OTA on 1524 hardware.
I suppose you use 1524 modem and other partitions. The script updates every of these partitions.
At first it asserts partitions software, and of course it fails.
If only smb wills to modify the script.
jgomez-m said:
When I Trying to INtall the update From TWRP got this error:
Processing OpenRecoveryScript file...
I:command is: 'install'
I:value is: '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/data/media/0'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/external_sd'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/bootdevice/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
E:Error installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Done processing script file
Click to expand...
Click to collapse
Who said OTA might be installed in TWRP?
AFAIK stock recovery required.
PsyClip-R said:
Who said OTA might be installed in TWRP?
AFAIK stock recovery required.
Click to expand...
Click to collapse
I could solve it, after all, I just reinstall a stock ROM and delete: cache, davilk cache, and Internal (user data)
then I had to install TWRP again
I guess we need to remove the modem patches from the update to allow installation on XT1524 ?
Interrested too : the update did download to my phone.
Got the .zip from /cache and waiting to update the script
napo7 said:
I guess we need to remove the modem patches from the update to allow installation on XT1524 ?
Interrested too : the update did download to my phone.
Got the .zip from /cache and waiting to update the script
Click to expand...
Click to collapse
Not sure if the script will pass the signature validation.
Though there's another way to update. Apply patches to files one by one, including boot.img, gpt.mbn and flash these patched versions on top of current fw. Excluding modem.
But this might be dangerous due to gpt.mbn flashing.
So guys I recently applied OTA patch to boot.img (i.e. kernel). It's relatively safe to boot it, but there's no 100% guarantee it will work as expected. Who knows what did Moto changed in there.
https://mega.nz/#!bsowHYTa!4sOxRwngUHLFyi8gAb1ZxVpitqCN24DkyMRnF3aZa58
If You have bootloader unlocked, TWRP and XT1527 firmware on Your XT1524 (or Regular 1527 without Stagefright patch), try to load it without flashing.
fastboot boot boot.img
Don't forget about the full backup.
Warning! I'm not responsible for damages you might made to your device. You're doing it by youself, and to your own responsibility
I have xt1527 android 6.0 stock and bootloader loock and stock recovery
i cant' install this update.zip?
Hi, I'm trying to follow this guide: http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132
However, when I try to access my efs files from cyanogenmod, my phone immediately reboots when I open the file.
I've tried making a backup of my efs file and extracting efs1.emmc.win, but in ext2explore, the file shows up as 0 bytes and in ext4unpacker, I get an error that says 'Error: List out of bounds' when I try to open the file. Can someone please help me access my efs files from cm so I can follow all the steps in the guide above?
Thanks
bumperino.
....
I'm taking my first stab at developing and have successfully built AOSP from source (aosp_angler-userdebug). The boot.img and system.img flash fine over fastboot, however, the .zip created from:
Code:
$ make updatepackage
passes an error in TWRP when I try to flash it. Something to the effect of:
Code:
Installing zip from '/path/to/file.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file formHey guys, I've looked around the forum and have done much Google-ing to try and resolve this.
at!
Updating partition details...
...done
After doing some Google-ing and re-reading the AOSP instructions many times, I guessed that my META-INF folder was missing since I couldn't find it anywhere in my source tree nor output directory. So, I tried:
Code:
$ make dist
then
$ ./build/tools/releasetools/ota_from_target_files output_path/target_files.zip
That did produce an ota_update.zip, but when I tried to flash in TWPR it yielded the same error. This is with N4F260 vendor and android-7.1.1_r14 source branch. Any suggestions would be greatly appreciated!
Can someone with liniux edit the cust.img by removing from app folder AsphaltNitro, DragonMania, Facebook, NewsRepublic, SpidermanUltimatePower adn Twitter? I don`t have a liniux pc and i don`t know how to work with siltaz....
I am on beta nougat and when i try to format or install lineage os i get the same error ever and ever "failed to mount /cust (invalid argument)", tried to flash cust with fastboot but it fails (remote size too large), if i go to backup and try to do a backup to cust.img i`m not able to do it cuz it got 0 MB so i need this cust modifiet to a smaller size.
it can be downloaded from here https://drive.google.com/open?id=0B2970_jcyuHXcS01SU00RG1QVTg
Hello everyone,
Please Help me to fix this issue
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
I have twrp v2.5
Actually, I am trying many solutions but nothing change
Hi, pal. I have the exactly same problem these days. On my opinion, when you have made wipe and wipe dalvik cache, you just deleted the system folder and data. I did same thing, now I'm stuck! :Д When you are trying to change the firmware, is the logo pictures changing for you every time you flash any other .zip file? We' are now complete lost man. Is your USB working like mine where PCs not detecting it? I think they've launched this kind of firmware only to destroy our device, so we can buy a new one. That's the idea. Go to the service and repair center of Lenovo and ask them for help! I wrote them down before a while, now I'm waiting for the response. We have left only two or three possibilities to flash the Rom with the Terminal in the Recovery. But if your PC recognizing the drivers, you will manage to flash the Stock 4.2.2 Rom with Flash tool , otherwise you are stuck too! I have no idea how to flash it. I can give you the terminal commands for you, which are hard to find, but you and me, we need the proper .img files for the flashing procedure. Go to the 4pda forum and ask for help, if you find any solution, come back here telling it and for me. There's a possibility, but it is difficult to create a proper .zip archive, because I only know that we need those folders and files: meta folder- updater-script, logo. bin, lk.bin, boot.img and system.img.
But when I insert the commands there, I don't know how the whole process must be working, something is happening there. The problem is that one of those lines did not work for me. Those are the commands for flashing any Rom with the terminal in the recovery. But first you must see if the PC is installing your drivers properly, open device manager and look for the drivers on the internet and try to install them. May be you have a working USB port, so there's no problem, just flash the stock rom with the Flash tool. But if it is not working as it is here, no other possibilities left, my boy! The only one left or two of them : Flashing the device either through fast boot mode or adb sideload, but you must install those drivers so PC can find the device. Well, you can always do this at your own risk from the terminal.
Oh, I forgot, those problem came when we deleted fstab file for our device.
Flashing firmware through the TWRP terminal commands:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6 (for the memory ROW+ ) or
dd if=/external_sd/system.img of=/dev/block/mmcblk0p5 (for CN+ memory)
dd if=/external_sd/boot.img of=/dev/bootimg
dd if=/external_sd/lk.bin of=/dev/uboot
dd if=/external_sd/logo.bin of=/dev/logo
First, system.img must be converted to systemEXT4.img, then flashing it and you need to have a systemEXT4 in the .zip archive. But I think my system folder is deleted. :Д
simg2img /external_sd/system.img /external_sd/systemEXT4.img
Good luck to you! According to me there is a space after the dot and it must be like this: system. img, boot. img. But not sure!
Hi again. Tooday It occurred to me where our problem may be came with the tablets. When we flashed a custom Rom, we put it for the wrong MTK processor. Ours is MT8389, not 6589. The stock roms are too for the MT8389 according to me. We flashed a wrong Rom. Now the tab must be formatted somehow either through some commands from the terminal, or USB port and path to the USB must be repaired. Then, flashing with the Flash tools is our only option left! Sorry! );
They killed our device on purpose with the Custom rom. Do not flash them any more with such Roms.