Related
BETA~
"Before you download please read 2nd post"
This is the first stage of flash-patch development, this will be used to get AOSP/Vanilla builds onto our INC's in an easy suitable way that fits us all. No more rebuilding or packing a whole new zip
I will be updating the patch as we get more fixes. v0.1 is released and you can grab them below.
Download AOSP FlashPatch v0.2:
http://ziggy471.com/incredibledoes/AOSP-FP-v0.2-signed.zip
Click to expand...
Click to collapse
What the patch does:
- flashes INC's necessary system files
- flashes INC's boot.img
What to come:
- Sense ROM support
Click to expand...
Click to collapse
How to install:
- download flash-patch (posted above)
- download an AOSP/Vanilla rom
- full wipe required
- flash the AOSP/Vanilla ROM but DO NOT REBOOT after install
- flash the patch over the AOSP/Vanilla ROM
- now reboot
That's pretty much it for now, later I will clean up the install and add more fixes to it... Please report back the ROM tested and/or if it failed.
ID
Click to expand...
Click to collapse
OKAY, this is a beta form flash-patch. This Patch will flash over any AOSP/Vanilla build "IF" the update/r-script is not asked to read the board of your device...?!
EXAMPLE:
- CyanogenMod builds have a getprop in the script which will not let you flash. If the script has something like this:
Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
then the installation will fail because the board does not match.. you can simply edit these your selves by editing the update/r-script...
BEFORE:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
AFTER:
assert(getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc" || getprop("ro.product.board") == "inc");
Click to expand...
Click to collapse
You can test out AOSP/Vanilla ROMS from any device like Droid, Desire, EVO, Nexus etc... as long as the script does not require the 'getprop' then you should be fine.
PLEASE NOTE: No telling on which roms are supported, only way to find out is to look around the forums and give it a flash... If tested and worked please post ROM/Developer so I can update OP.
"HOW TO EDIT update/r-script" 2 different ways~
NOTE: There is 2 different scripts "update-script" and "updater-script" you will see that I write "update/r-script" because there of the two different scripts. Updater-script comes with an "updater-binary" I never edit the binary so you can leave it alone... just edit the update or updater-script.
Click to expand...
Click to collapse
1- unzip the downloaded ROM
2- open folder META-INF >> com >> google >> android >> update/r-script
3- Open the update/r-script using an xml reader (For WINDOWS use notepad++) (For LINUX use gedit) or something similar...
4- Change the getprop "<device>" to getprop "inc"
5- save and replace the old update/r-script with the one you just saved
6- sign .zip and flash (If I remember correctly Clockwork recovery does not need a signed update.zip so signing the .zip is not required)
Click to expand...
Click to collapse
1 easy step:
This is the easiest way to edit the update/r-script... Completely remove the "assert getprop"
~EXAMPLE from CyanogenMod for N1~
Before:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012" ||
getprop("ro.bootloader") == "0.35.2017" ||
getprop("ro.bootloader") == "0.35.0017");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
After:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you want to learn how to sign .zips follow this thread>>> http://forum.xda-developers.com/showthread.php?t=537937
0.2:
- fixed data
- cleaned install
- audio fixed
- build.prop edits
- tethering now works
0.1:
- initial release
you know, I just started using ShadowROM and am loving it! I finally found a great AOSP rom that works wonderfully for me exactly how I want it. I really thought that I was going to stop flashing roms every day finally because I found an AOSP that I love! And then BAM, I read this thread and my choices of roms to try and test just grew 10 times larger....Thank You ID, really...Thanks >0.
Haha, no just kidding. This patch is awesome, I can't wait to start finding and testing out ROMS for other devices. Way to go ID!
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
khanam said:
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
Click to expand...
Click to collapse
clockworkmod recovery.img Im pretty sure it does not need a signed.zip but if you use amon_ra then you need to sign the .zip
Q2: Nandroid will restore as normal, no need to re-apply the patch.
well, i thought i edited my getprop stuff but cyanogen 6.1 from nexusone failed due to getprop bootloader =0.33.2012 and a few others...
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
dx has that ninjablur BS
this is only for aosp roms.
touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
Apparently I have stayed in the Inc area too much as I was just wondering if there are kitchens like their used to be for WinMo...
es0tericcha0s said:
dx has that ninjablur BS
this is only for aosp roms.
Click to expand...
Click to collapse
Ok, I'll just add the files needed to port it then. Thanks!
es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
Thanks!
So, obviously, Cyanogenmod for the Nexus works. Just removed the assert from the update/r script for both the bootloader and the device. Once that was fixed
1. install rom
2. run Inc's zip
3. ziggy kernel
4. Gapps
rebooted and running.
Not sure why, but wifi isn't working with it and I've tried the Kernels recommended in the Inc Cyanogen thread.
I got lithium mod to work using patch. Thank you.
Sent from my ADR6300 using XDA App
es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
oh wow! thanks man!
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
papi92 said:
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Just leave the binary alone...
ID
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
updated 2nd post with two ways to edit the script...
papi92 said:
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
reboot recovery
Hello, I just got a Rooted Verizon Galaxy Tab and I don't know how to flash clockworkmod recovery? I found what looks to be a great ICS rom at rootzwiki. However it need Clockworkmod recovery. Any ideas? All the links I find are dead, or no longer recommended. If you could point me in the right direction I would appreciate it. Thanks.
P.S. I looked at Verizon Tab Bootstrapper on the market but there are lots of people who experienced serious problems because of it. I'm not sure if they did it wrong or not. There is this one reviewer that says you need to be running the Original stock rom, maybe he means froyo? I can't seem to locate the original Froyo rom. Thanks.
you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.
priyana said:
you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.
Click to expand...
Click to collapse
That thread is for the Sprint version, would it work for the Verizon?
Also, I have a rooted stock rom installed. (or so I was told by the guy I got it from) But root checker basic says I don't have proper root access. Is that normal? Should I flash the absolute stock rom with Heimdall and do a superoneclick, rooting it myself?
Thanks.
I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0
priyana said:
I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0
Click to expand...
Click to collapse
Edit: I JUST DID IT!!! THANK YOU!!! I chanced it and used the ODIN I mention below to flash the custom kernel/custom recovery. I'm now doing a backup of the system! Next I'll flash the ICS Rom I found. THANKS!!! Also, I just realized I passed my 10th post! So Now I can post in the development threads! Thanks for that to!
Okay, also I can't seem to find ODIN for the Verizon version. I found ODIN3 v1.7 for the GT-P1000. Would that work for the Verizon version?
And he says to flash the Kernel with any EF17 installation? I don't understand. Thanks for your help.
Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
priyana said:
Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
Click to expand...
Click to collapse
Well, I flashed the custom kernel in odin and my System is still working. Although for some reason the computer wouldn't recognise the MicroSD so I had to use a reader. I rebooted into recovery and made a backup, then I wiped EVERYTHING (except SD card) and tried installing this: http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/ And its giving me:
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab7c" | | getprop("ro.build.product") ==
"galaxytab7c" | | getprop("ro.product.device") == "plc" | | getprop("ro.build.product") ==
"plc" | | getprop("ro.product.device") == "SCH-I800" | | getprop("ro.build.product") == "
SCH-I800" | | getprop("ro.product.device") == "SPH-P100" | | getprop("ro.build.product") =
= "SPH-P100" | | getprop("ro.product.device") == "vzwtab" | | getprop("ro.build.product")
== "vzwtab
E:Error in /sdcard/(name of file).zip
(Status 7)
Installation aborted.
Any ideas? I'm doing a system restore now until I can figure it out. Someone on the thread did say we should be using CWM 5.3. I'm using 4. Where can I get 5.3?
common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10
priyana said:
common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10
Click to expand...
Click to collapse
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!
Electriccars said:
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!
Click to expand...
Click to collapse
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app
priyana said:
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah it did. DOH! lol. Funny because I looked into the updater script of CM9.1 and didn't see the asserts lines. but I missed them. I am rezipping the file with the edited script and lets see what happens!
My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app
priyana said:
My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...
Electriccars said:
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...
Click to expand...
Click to collapse
Shoot, now it says:
E:Error in /sdcard/cm-9.1.0p1c.zip
(Status 6)
Installation aborted.
Any ideas?
Edit: Just found: http://forum.xda-developers.com/showthread.php?t=1585619
It says how to flash CWM 5. and flash ICS let me try that.
Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app
priyana said:
Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No I used wordpad. But no matter. I now have CM9.1 stable installed!!! With CWM 6! woohoo! Thank SO much for your help!
Hi,
I want root my S3 I9305 4.1.2 I9305 JZO54K.I9305XXBMB5
Can I use ToolKit V7.0 ?
Which select International LTE (GT-I9305)
15. Android 4.1.2 (Build JZO54K BLL3)
or
16. Android 4.1.2 (Build JZO54K BLL5)
How I can root it please help me step bay step?
1. Download and copy zipfile (avatar-3.0-arion-1361-20130629-i9305.zip ROM version choice) to internal or external SD card. Check MD5.
2. Boot to recovery.
3. Wipe cache, dalvic cache, wipe data
4. Install zip from SD Card > choose zip
5. select avatar-3.0-arion-1361-20130629-i9305.zip install
6. GET ERROR
Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.build.product.device")== "m3xx"||getprop("ro.build.product") =="m3xx"||getprop("ro.product.device")=="i9305"||getprop("ro.build.product") =="i9305"|| getprop("ro.build.product.device")== "GT-I9305"
E: Error in sdcard/roms/avatar-3.0-arion-1361-20130629-i9305.zip
(Status 7)
Installation aborted.
What I did wrong ?
I should ask in that roms thread .
jje
Use framaroot app to root, search my thread.
Sent from my GT-I9305 using xda premium
If you want to root your device, I suggest you use CF-Auto Root.This method is a high success rate.Before I used this method root in I9305ZHBMD1.
Sorry for my bad English :banghead:
I've sucessfully flashed several ROMs to my htc One m7ul, I've followed the convert your device to a google plus edition changing my model name and I've been able to install other m7ul based roms on my device (AOKP for example) but when i download the pacman roms from the official Pacman site under their Other and Stable section for the m7ul and try to install it (after making a wipe) i get the following in my log:
+------------------------------------------------------------------------------------------------+
Installing '/sdcard/Download/pac_m7ul_4.3-build(rest cut off?)
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == (rest cut off?)
getprop("ro.product.device") == "m7ul" | (rest cut off?)
E: Error excuting updater binary in zip '/sdcar (rest cut off?)
Error flashing zip '/sdcard/Download/pac_m7ul_4 (rest cut off?)
Updating partition details . . .
+------------------------------------------------------------------------------------------------+
the "(rest cut off)" being where i think theres more text to the error but due to the screen formatting it looks like its being cut, I'm using TWRP recovery, have an unlocked bootloader and have s-off, Can anyone help me?
I've been able to install the ROM by using AndroidKitchen to extract the updater-script and edit it. The homescreen is very buggy, no wallpaper display, bootloop issues. I'm Changin the kernels to try and help but im not sure if this is a rom issue or a kernel issue. Does anyone have this ROM installed? and if so what kernel are you using?
I checked my logs after a bunch of things failed and my SKU is coming up blank!
"
script aborted: Please use the right SKU for updating...
Device image SKU:
OTA image SKU: WW
Please use the right SKU for updating...
"
How can I make it WW again... this is causing me an impressive amount of problems.
Is this happening when you try to install stock from a custom ROM?
FruitlessPotato said:
Is this happening when you try to install stock from a custom ROM?
Click to expand...
Click to collapse
Happened then as well. However currently it is happening with the stock ROM that I restored after getting rid of the custom ROM
Let me also give a background. I was on CM13, went to go update got an error saying I needed to update my firmware in order to install. So I tried a crap ton to get stock roms to install, didnt work (SKU was blank). So I restored my original/stock rom which would not restore the data.
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
FruitlessPotato said:
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
Click to expand...
Click to collapse
Okay so a guy on Reddit told me that errors dont mean anything, you need to look at the logs and see what caused them which is done by the recovery log.
And if you have TWRP recovery on there try to flash CM12 for the zenfone. CM13 flashes for me but randomly/constantly reboots
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.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.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
FruitlessPotato said:
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.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.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
Click to expand...
Click to collapse
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
**** that looks like you are doing CM13 and it is telling you your firmware is out of date.
So it wants you to flash the latest stock firmware.... but you and I are in the boat were our phones wont let us do that. Dude I do not know
me either, tried updating the updater-script and all but to no avail
Is your phone on Android 5.0.2?
I was trying to find ROMs that fit that version. There are definitely other custom roms then just CM
Fruitless! Download the CM13 nightly from june 14th!
Dont do the most recent.
Edit: I know this sounds sketchy and or stupid but I have a cm13 rom from june 14th that I downloaded then, it works. The CM13 from then that I downloaded today did not. I can see about uploading the one that did work if the one you download doesnt work.