As we know, Cyanogenmod has released official nightlies for the Samsung Galaxy S5 Sprint (or kltespr in their words). I tried to flash the latest nightly and it fails with the statement "This is for kltespr devices. This device is a klte." So I am wondering... if the nightlies are for the Sprint Galaxy S5, what is the difference between the klte and kltespr? Also, how can I flash this "safely" if I can at all?
Delete the top section of the updater script so that the first line starts withe the word mount
vinman12 said:
Delete the top section of the updater script so that the first line starts withe the word mount
Click to expand...
Click to collapse
Sorry, I'm not on that level yet. How would you do that?
Still Doesn't Work
ethomas94 said:
Sorry, I'm not on that level yet. How would you do that?
Click to expand...
Click to collapse
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.
hastack97 said:
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.
Click to expand...
Click to collapse
weinerwad3000 said:
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.
Click to expand...
Click to collapse
MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.
ethomas94 said:
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.
Click to expand...
Click to collapse
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.
MorningStarGG said:
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.
Click to expand...
Click to collapse
I'll try that and get back to you. I was extracting the entire zip and altering it, then re-zipping the whole thing.
I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.
Also, a lot of people were saying that the edited updater-script file would not stay saved and would just revert as soon as you left the editor no matter what. I've got around this by using Gedit (for linux or mac, I don't know about pc) and hitting "save as...", keeping the original name, then simply replacing the original file with the edited one.
It would be nice if one of these sharp guys would post them already altered.
ethomas94 said:
I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.
Click to expand...
Click to collapse
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.
mempho69 said:
It would be nice if one of these sharp guys would post them already altered.
Click to expand...
Click to collapse
weinerwad3000 said:
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.
Click to expand...
Click to collapse
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
KT Recovery is a modded TWRP, just so you know. It works!
ethomas94 said:
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
Click to expand...
Click to collapse
Thank you. I installed the recovery and the file worked. I tried downloading the recovery a few days ago but I got a 404 error from the link. I couldn't stand the stock os so you helped me out tremendously. Thanks again.
No problem!
Sent from my SM-G900P using XDA Free mobile app
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
AuGmENTor said:
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
Click to expand...
Click to collapse
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
http://forum.xda-developers.com/showthread.php?p=52260413
miked63017 said:
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
Click to expand...
Click to collapse
I flashed PacMan ROM, which for some reason worked. So for now I'm stable. But I will be looking to go back to my first true love.... Cyanogenmod!
Related
i seem to have fubar'ed my nexus s (uk version) i updated to ics, didnt like it so tried to restore to a backup i made earlier today...
at the moment when i turn on my phone it shows
fastboot mode- No Boot or Recovery img
lock state - unlocked
I can enter recovery. but cannot restore.
tried wiping cache,dalvik etc.
When hitting restore it returns with:
... system.img not found. skipping restore of /system/
also does the same with
data.img
cache.img
sd-ext.img
i have no idea what to do... if you could help it would be greatly appreciated.
Try flashing a rom. U can mount SD card within recovery.
Sent from my Nexus S 4G using xda premium
yeah tried flashing ...
gets stuck on google screen
Do you have a One Click return to stock available for your model? It wouldn't hurt to start fresh. I did that on my NS4G last week. Does your PC recognize the phone?
Sent from my SPH-D710 using Tapatalk
looking into the unbrickable mod atm... my phone seems to have no .img files.
tried restoring to stock and still the same issue... it says it cant find .img so skips them then when i try to re boot it sticks on the google screen
After trying to apply from zip (cm7, that i have used numerous times before)
i get this ---
Installing update...
assert failed: getprop("ro.product.device") =="crespo" ll getprop("ro.build.Product") == "crespo" ll getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
i havent the faintest idea what to do...
Tried re-flashing CWM recovery?
yup tried re flash,
i think i need to replace the .img files... i just dont know how
it says that
system.img not found
data.img not found
cache.img not found
sd-ext.img not found.
it skips the restore of these say restore complete. yet there is obviously nothing to restore.
there must be a way of fixing this???
Do you have the latest version of CWM flashed? (5.0.2.0)
yeah re installed/reflashed (5.0.2.0)
it seems to be working
*~~~~~~*
Facepalm
*~~~~~~*
Such a noob
I have had a similar problem before, and even advised on that exact thing.
lesson learned.
KEEP RECOVERY.IMG UP TO DATE
Thank you for pointing out the obvious.
I'm such a ****
No problem flex59, best way to learn is the long and hard way . I had a similar status 7 problem on my move up to ICS. Figured the latest recovery will save me wasted hours down the track eventually, and hopefully someone elses.
To downgrade from ICS, you need to flash the full GB 2.3.6 ROM first...
I downgraded from OTA ICS 4.0.3 due to battery, Wifi & lag issues as well. A NANDroid backup does NOT contain the bootloader and radio AFAIK. Here's what I did.
Find the appropriate FULL ROM here and download and copy to your SD card.
Download this flashable Superuser here and copy to your SD card.
Make sure you are familiar with and set up for fastboot and have the latest CWM recovery img file. You will have to reinstall CWM. These instructions are assuming that CWM recovery is already installed on your device.
1. Make sure the full ROM and SU zip are on the root your SD card.
2. I did a full wipe of data, cache, dalvik.
3. Go into CWM recovery and flash the full ROM. Now flash the SU zip.
4. At this point, the full ROM flashed GB2.3.6, stock recovery, bootloader and radio back. But you should be rooted due to step 3.
5. Boot into Android. I installed ES File Explorer from the market. In ES File Explorer settings, select both root settings “Root Explorer” and “Mount File System” to navigate and modify root files. Allow permissions in SuperUser.
6. Navigate to /system/etc and rename (tap&hold on file) install-recovery.sh to install-recovery.sh.bak (this file reinstalls the stock recovery at every boot)
7. Using fastboot on your computer, flash CWM recovery again.
8. NOW using CWM, restore your GB 2.3.6 NANDroid backup.
Like nothing ever changed.
Hello everyone,
I saw a lot of people facing errors in CWM recovery while installing ROMs, themes, etc. So I decided to make a simple, short and clean thread to post some solutions which might help you in overcoming the errors.
Status 0 Error:
This error occurs due to some error in updater-binary. Replace the updater-binary from some other same type of zip you are flashing and it will work.
Click to expand...
Click to collapse
Status 1 Error:
Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you dont have correct permissions set. Use correct perms in updater-script and done
Click to expand...
Click to collapse
Status 6 Error:
The status 6 error mostly occurs when we edit an updater-script in windows text editor. This is because the windows text editor at the end of the updater-script creates a windows styled end of line which causes the error. The easiest solution is to write the updater-script in such a way that this error doesn't occurs. Try notepad++, change the end of line to unix style, unix style eol and this error won't occur
Click to expand...
Click to collapse
Status 7 Error:
The most common error that most of the people face is this one.
Following are the reasons for it:
1. Something wrong in updater-script.
2. Corrupt zip.
3. Zip not made for device or couldn't recognize the device.
To overcome the first error, the only solution is to manually edit the updater-script and search for error or post your updater-script to some forum or thread or make new thread specifying your complete error.
To overcome the second error, the only solution is to re-download the whole zip.
To overcome the third error, just delete the first three lines from your updater-script stating something related to your device. Here's the lines related to my device, i.e., Sony Ericsson Xperia Mini Pro, SK17i/a :
Code:
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
Similar kind would be for your device too. And if not then the zip is simply not meant for your device.
Click to expand...
Click to collapse
Great thread,
Btw in status 6, we have to select eol as unix in npp, not just use it right
Added about status 1 error also
Cheers,
AJ
When there's 0,1 and then 6 and 7. Logic tells that there is 2-5, anybody ever heard of it?
Regards
N
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
DarthRecca said:
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
Click to expand...
Click to collapse
Make sure you zipped all the folders with meta-inf and not zipped the parent fodder
Cheers,
AJ
To whom got status 1 error
I had this problem(cwm status 1 error) while flashing my xxxxxx.zip ,so i got a twrp ,in its advanced options ,got to the file manager ,head to the / directory (all of the thing where there) ,tapped on select button,and chmod 755. Then with cwm i could flash my zip.
don't mount my ext sd card
I'm install cwm recovery in galaxy s dous 2 s7582 but cwm cannot mount my SD card for selecting any update from storage.................
Hi Guys,
I've never had this problem before but I can't seem to get any zip files I create to flash through TWRP.
I've compressed them with STORE method in 7zip.
I've double checked everything I put in the update-script file.
and I've tried signing them
My directory tree for the zip is as follows:
Code:
-META-INF
CERT.RSA
CERT.SF
MANIFEST.MF
-com
-google
-android
update-binary
updater-script
-system
-priv-app
SystemUI.apk
My updater-script only has a few lines because I'm still trying to just get it successfully run but it is as follows:
Code:
ui_print("Testing if system can be mounted");
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
with of course an extra empty line at the end.
This is a screenshot of my failed flash:
http://www.mediafire.com/convkey/bba3/r0eidwl8ito77uhfg.jpg
I noticed it says "updater-binary" rather than "update-binary" so I tried changing the name and signing the zip again.
After attempting to flash the unsigned and the signed zip this is the message I get:
http://www.mediafire.com/convkey/ed01/5oh5mqyt6lv8lwffg.jpg
No longer says updater-binary but still getting MD5 error and flash is failing everytime.
I was able to flash the Omni rom I even switched my signed SystemUI.apk with the one in the rom and flashed it fine.
I have downloaded update.zip(s) and flashed them fine. But whenever I edit the update-script my self it doesn't do anything .. I've even tried a simple
Code:
ui_print("message");
and it failed.
Not sure what I am doing wrong never had this problem when i was theming for my Lg Revolution way back when .
Also I'm using Notepad++ and eol conversion is set to unix.
Thanks to anyone with answers.
hackn101 said:
Hi Guys,
I've never had this problem before but I can't seem to get any zip files I create to flash through TWRP.
I've compressed them with STORE method in 7zip.
I've double checked everything I put in the update-script file.
and I've tried signing them
My directory tree for the zip is as follows:
Code:
-META-INF
CERT.RSA
CERT.SF
MANIFEST.MF
-com
-google
-android
update-binary
updater-script
-system
-priv-app
SystemUI.apk
My updater-script only has a few lines because I'm still trying to just get it successfully run but it is as follows:
Code:
ui_print("Testing if system can be mounted");
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
with of course an extra empty line at the end.
This is a screenshot of my failed flash:
http://www.mediafire.com/convkey/bba3/r0eidwl8ito77uhfg.jpg
I noticed it says "updater-binary" rather than "update-binary" so I tried changing the name and signing the zip again.
After attempting to flash the unsigned and the signed zip this is the message I get:
http://www.mediafire.com/convkey/ed01/5oh5mqyt6lv8lwffg.jpg
No longer says updater-binary but still getting MD5 error and flash is failing everytime.
I was able to flash the Omni rom I even switched my signed SystemUI.apk with the one in the rom and flashed it fine.
I have downloaded update.zip(s) and flashed them fine. But whenever I edit the update-script my self it doesn't do anything .. I've even tried a simple
Code:
ui_print("message");
and it failed.
Not sure what I am doing wrong never had this problem when i was theming for my Lg Revolution way back when .
Also I'm using Notepad++ and eol conversion is set to unix.
Thanks to anyone with answers.
Click to expand...
Click to collapse
It's update-binary. Try this one: https://db.tt/MdWU1rZ8
You can mount /system with this: run_program("/sbin/busybox","mount","/system");
You do not need the signature files in /META-INF
Aerowinder said:
It's update-binary. Try this one: https://db.tt/MdWU1rZ8
You can mount /system with this: run_program("/sbin/busybox","mount","/system");
You do not need the signature files in /META-INF
Click to expand...
Click to collapse
Thanks I renamed it back to update-binary I'm not sure what I did differently but I have one working now.
However I noticed in my post I didn't forget any semi colons, But that will keep the whole file from installing so maybe I had the right setup before and just missed a semi colon.
Thanks again
Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk
Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.
Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!
Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.