Database Users

[Q] OTA ICS on SC failed

I'm trying to update over OTA to ICS on my 39_0089_SC device.
The update.zip will be downloaded completed.
If a start the update installation (CWR -> install zip from sdcard) I get the following failure message:
assert failed: getprop("ro.product.device") =="Indigo" || getprop("ro.build.product")== "Indigo"
E:Error in /sdcard/update.zip (status 7)
What wrong? I have only tried to flash a ROW image... no success.:crying:
device config:
CWR 5.0.2.7 installed and rooted
original SC image

Pls read the other threads on the forum. This was solved yesterday. Anyway the error is because you have Cwm instead of the normal android recovery. The solve this, comment out the lines of the updater-script that check for "indigo".

another Problem...
now I have comment out the "indigo" lines at the updater-script and made a signed update.zip (fokke.org/site/content/howto-create-android-updatezip-package).
If a try to install the upater.zip from SD card, i get a new failure message:
Installing update...
E:Error in /sdcard/updater.zip (Status 6).....
Have Imade somthing wrong?? Problems with system apps or OTA Rootkeeper?

http://www.thinkpadtabletforums.com...lopment/guide-to-installing-ota-3-(ics-4-03)/
Go here, this is a guide to upgrading to ICS.

solved - ICS Update is working now!
Below the steps what a have done:
1) Download OTA over wifi
2) modified update.zip (indigo update failure messages)
Error 6 was coming from updater-script -> not use notepad to edit!!!
3) generate new update.zip (fokke.org/site/content/howto-create-android-updatezip-package)
4) install OTA RootKeeper (protect root)
5) update "busybox" file from lenovo image (website, system/xbin/busybox)
6) install update.zip over CWR
that's it! now I'm rocking on ICS.....
(CWR is overwritten by the ICS update )
Thanks you guys for help!!!

Good to hear you sorted out your problem. And also thanks for posting the solution that worked for you. That will help the rest of us.

[Q] I9505G OTA Upgrade Fails

I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.

Yes you'll need to flash original FireWire with Odin but before proceeding with the flash run triangle away it should be ok then
Sent from my GT-I9505 using Tapatalk

FireWire? What's that? I don't think I flashed anything like that.

ruidh said:
FireWire? What's that? I don't think I flashed anything like that.
Click to expand...
Click to collapse
I think he means "Firmware" :highfive:
ruidh said:
I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.
Click to expand...
Click to collapse
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE

Thanks. I'll give that a try.

Joku1981 said:
I think he means "Firmware" :highfive:
Click to expand...
Click to collapse
I'm not sure about Odin here. I never altered the stock recovery.
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE
Click to expand...
Click to collapse
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4

ruidh said:
I'm not sure about Odin here. I never altered the stock recovery.
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4
Click to expand...
Click to collapse
It's not my problem if you don't know read.

I followed Method 2. I see what you're saying now.

None of these upgrade methods worked. I still had assert failures. I removed SuperSU after restoring all changes I made to /etc.
Somehow this morning the phone failed to connect to data services. Several apps failed when they tried to access the network.
I eventually reflashed a 4.4.3 rooted image from here http://forum.xda-developers.com/showthread.php?t=2772043 and restored my Titanium Backup.

OTA upgrade to 4.4.4 succeeded after turning of SuperSU and reverting my change to \etc\permissions

Jflte vrs jfltecan vrs jfltexx

I thought after reading a few things that it would be possible to install cm12 jfltexx to my jfltecan b/c of the similar architecture and unification of cm12 for S4. It seems as if they re-branched the releases to separate variants and twrp wont allow me to flash an jfltexx rom. So am I doing something that I shouldn't be. Unfortunately there is still no rls for the jflte or jfltecan which is why I thought I would try the international.

dasbooter said:
I thought after reading a few things that it would be possible to install cm12 jfltexx to my jfltecan b/c of the similar architecture and unification of cm12 for S4. It seems as if they re-branched the releases to separate variants and twrp wont allow me to flash an jfltexx rom. So am I doing something that I shouldn't be. Unfortunately there is still no rls for the jflte or jfltecan which is why I thought I would try the international.
Click to expand...
Click to collapse
You can always try it. It won't brick your device but you might have to Odin the stock firmware. You'll have to edit the updater-script in the the rom to allow you to flash it (assert line)
Sent from my Nexus 5 using XDA Free mobile app

Yes thanks reading a little more and saw some threads where someone flashed jflteatt to there Canadian s4 And had to alter the updater script. I looked briefly through the zip file but couldn't locate it. Now in terms of Odin and flashing back to stock, do you mean if i soft brick flashing the international cm12 rom or do u mean something else.

dasbooter said:
Yes thanks reading a little more and saw some threads where someone flashed jflteatt to there Canadian s4 And had to alter the updater script. I looked briefly through the zip file but couldn't locate it. Now in terms of Odin and flashing back to stock, do you mean if i soft brick flashing the international cm12 rom or do u mean something else.
Click to expand...
Click to collapse
In the zip goto META-INF, com , Google, android. There you'll find the updater-script. There should be a line that starts with "assert". You'll have to delete or edit that line for your device.
If things go wrong, that's where you might have to odin back to stock.
Sent from my Nexus 9 using XDA Free mobile app

Thanks for clarifying and answering my noobish questions. Maybe I'll have a crack at it. Any thoughts on when we will c cm12 for my i337m. Interesting how they forked the ROMs again

Well I was able to install cm12 from jfltexx to I337m variant. I had to delete the assert line as changing the line to jflte didn't work and errored in twrp. Everything seems to work but I'm guessing otas wouldn't work till you changed the updater-script.

Nothing to c here weird repost happened while moving back in the browser

You just removed it?!
dasbooter said:
Well I was able to install cm12 from jfltexx to I337m variant. I had to delete the assert line as changing the line to jflte didn't work and errored in twrp. Everything seems to work but I'm guessing otas wouldn't work till you changed the updater-script.
Click to expand...
Click to collapse
You didn't do anything special to it? Just wanna be sure because I'm new to this as well

No you definitely have to go in and change the updater-script than rezip the ROM. The international rom did install and run fine tho

FYI, I just flashed my i337m with jfltexx and everything is fine except that mobile data does not work.

Are you using the latest modem and bootloader?

audit13 said:
Are you using the latest modem and bootloader?
Click to expand...
Click to collapse
I thought I was because I had applied the stock BMC 5.0.1 ROM before going the custom rom route. So I flashed modem.bin using Odin/CSC and indeed data works now. As for the bootloader I'm using TWRP (latest.)

cythraul said:
I thought I was because I had applied the stock BMC 5.0.1 ROM before going the custom rom route. So I flashed modem.bin using Odin/CSC and indeed data works now. As for the bootloader I'm using TWRP (latest.)
Click to expand...
Click to collapse
Hi,
I'm going to do pretty much the same as you did on my S4 SGH-I337M, but with most recent CM13 found HERE.
I was also wondering if you could point out where I should find the modem files if ever I experience data issues after the flashing.
Thanks & Regards,
chatdeau

EDIT: I made the mistake of re-zipping the ROM folder instead of it's content.
Flashing right now ...
---------- Post added at 11:46 AM ---------- Previous post was at 11:29 AM ----------
chatdeau said:
EDIT: I made the mistake of re-zipping the ROM folder instead of it's content.
Flashing right now ...
Click to expand...
Click to collapse
Alright, I'm now booting CM13 on my Samsung Galaxy S4 SGH-I337M jfltecan !
Testing ... will report back and I might start a new thread (for intermediate users, but relatively CM noobs like me) to explain the whole rooting / cm13 rom mod / flashing procedure I went through to get to this point.
---------- Post added at 12:12 PM ---------- Previous post was at 12:00 PM ----------
Everything seems to be working fine for now. And it's pretty fast!

With the i337m, installing a custom ROM is pretty easy.
download and install the latest stock ROM from sammobile.com to ensure the phone is running the latest bootloader and modem: http://www.sammobile.com/firmwares/database/SGH-I337M/ (this step is not necessary if the phone is running the latest modem and bootloader);
download Odin 3.07 from here: https://www.google.ca/url?;sa=t&rct...QWImOPDJboTA_V3D5S9eA&bvm=bv.112064104,d.amc;
download the latest TWRP from here: https://dl.twrp.me/jflteatt/;
use Cygwin to convert the img file to a tar file for flashing in Odin: http://cygwin.com/install.html;
boot phone into download mode by holding volume down, home, and power button. Release the power button when the phone starts to boot;
open Odin, uncheck everything except f.reset time and connect the phone in download mode;
click on PDA and select the TWRP file that has been converted from an img file to a tar file and flash it;
when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, use button combination to boot into TWRP (hold volume up, home, power button and release power button when phone starts to boot).
Once TWRP is installed, copy the custom ROM to be installed to the phone's internal memory or a micro SD card and install the ROM from TWRP. The Gapps version should match the ROM version.

Help!
So I'm trying to do this same thing for my SGH-i337m. But every time I try to flash it in TWRP it just says installation aborted. I'm thinking I'm just deleting the wrong portion of the assert line. Could someone please point me in the right direction? Below is the top portion of the script. Could someone please highlight which portion I should delete? Thanks!
assert(getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" || getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" || getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" || getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" || getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" || getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G" || getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("This package is for device: jfltexx,i9505,GT-I9505,jgedlte,i9505g,GT-I9505G,jflte; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHPF4:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");

cmjdjm1 said:
So I'm trying to do this same thing for my SGH-i337m. But every time I try to flash it in TWRP it just says installation aborted. I'm thinking I'm just deleting the wrong portion of the assert line. Could someone please point me in the right direction? Below is the top portion of the script. Could someone please highlight which portion I should delete? Thanks!
assert(getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" || getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" || getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" || getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" || getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" || getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G" || getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("This package is for device: jfltexx,i9505,GT-I9505,jgedlte,i9505g,GT-I9505G,jflte; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHPF4:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
Click to expand...
Click to collapse
Personally, I just flashed the TWRP for the i9505 and can flash any ROM I want from the 9505 board on my Canadian SGH-1337M. Obviously not responsible for any issues that may come up - but so far so good
Sent from my Transformer TF101 using Tapatalk

bill_in_mtl said:
Personally, I just flashed the TWRP for the i9505 and can flash any ROM I want from the 9505 board on my Canadian SGH-1337M. Obviously not responsible for any issues that may come up - but so far so good
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
thanks! that worked beautifully! up and running now with no issues that I'm finding at all on the Sept 1st nightly

This may not be the best place to post this, but anybody looking to run cm13 on the Galaxy s4 Canadian (I337M) might notice that the jfltexx recovery and cm13 roms "almost" work flawlessly. The only problem I had was a serious WiFi disconnect/reconnect problem. If you also have this problem, do this:
1. Install TWRP for jfltexx
2. Install cm13 for jfltexx (and gapps etc)
3. Flash modem.bin from the modem files found on this thread: Here
--- For jfltecan download the 11/26/2013 (Canada) file (modemmk6.zip -> modem.bin)
--- Can flash this file with Odin or Heimdall
4. Wipe Cache/Dalvik
5. Reboot
[Edits - Some Notes]
I personally prefer to use Heimdall for flashing TWRP on the s4 as it's very simple. I found Odin can sometimes be tedious and most useful for flashing stock roms... but it's up to preference.
For Heimdall:
1. Boot into download mode (Power down, Hold Power + Vol Dwn + Home until the phone vibrates and release) OR using adb type: "adb reboot download"
2. open terminal in heimdall directory and use command:
"heimdall flash --RECOVERY recovery-img.img --no-reboot"
3. Power down and reboot into recovery immediately or bootloader will overwrite the new recovery image. (Power + Vol Up + Home until it vibrates).
to use heimdall to flash the modem use:
"heimdall flash --MDM modem.bin" optionally use --no-reboot to reboot to recovery manually and wipe cache
[/Edits]
Enjoy cm13 nightly on jfltecan without any wifi problems!

I'm trying to install CM13 for i337m (from Latin-America) and have no luck. The phone is rooted, on stock 5.0.1 UMUGOH3, and I've tried all recoveries TWRP 3.0.2-0 for jflteatt, jfltecan, lfltexx, and CM13 for jflteatt, and other, deleted the FIRST assert line... no results, always error: 7

Has anyone tried yo install russian flyme Roms with integrated TWRP?

Has anyone tried russian flyme twrp roms? There are 3 Roms in their link, but i don't know how to install it.

any link please ?

I can't put links because i have less than 10 post.
I'm sorry.

Write emmaus.pro in google. There are twrp for mx4 and custom roms, flyme and cm12.

I have Flyme 4.5.7i on my MX4 flashed by TWRP recovery.
(original my mx4 was A edition, and I was unlock bootloader and flash custom recovery with instructions found on xda forum)
Instructions How To Edit Official Flyme Rom to be flashed with TWRP:
---------------------------------------------------------------------------------------
1. Unzip update.zip in empty folder
2. Go in folder with unpacking files and delete uboot.img and logo.img
3. Go in META-INF folder and from here delete imei.dat and machine_match
4. Go in COM/GOOGLE/ANDROID folder and edit updater.script
Remove this :
getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "M460A" || abort("This package is for "mx4" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("META-INF/machine_match", "/tmp/machine_match");
set_perm(0, 0, 0755, "/tmp/machine_match");
package_extract_file("META-INF/imei.dat", "/tmp/imei.dat");
if (run_program("/tmp/machine_match", "/tmp/imei.dat") != "0") then
ui_print("machine not match");
delete(/tmp/imei.dat);
abort();
endif;
delete(/tmp/imei.dat);
And remove this :
assert(package_extract_file("logo.img", "/tmp/logo.img"),
write_raw_image("/tmp/logo.img", "logo"),
delete("/tmp/logo.img"));
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
Save edited file.
5. Pack again files in .zip arhive (any name except update.zip)
6. Remove or rename any update.zip original file from root sd card
Now you can flash rom with twrp recovery and now you have latest Flyme rom but still have unlocked bootloader and twrp recovery.
I find this instructions on russian forums, and I try it and everything works fine.
You can try it on your responsibility.

Ok, thanks. Where have you downloaded twrp recovery?
Now i have philz 6 recovery, if i flash modded flyme ROM, can i flash it with philz?

I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file

TWRP (uncompiled and recompiled by myself to change splash screen (it now fit the screen) http://www.mediafire.com/download/26b963db1k489db/new-recovery.img

Can i flash it trough flashify app?

I was flash twrp with fastboot

You can via flashify but fastboot is safer

PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"

Are the russian flyme roms modded to can flash it vía twrp?

yes you can flash them Russians have ported this TWRP and are making some good stuff on flyme rom

Ok, i will try those Roms. Thankyou so much.

furious.builder said:
I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file
Click to expand...
Click to collapse
I can't understand you. If is already tried that you can flash modded flyme Roma from twrp, why you say that flyme will reinstall stock recovery?
Are you sure?

I'm talking about stock Flyme not modded Flyme Stock flyme contains scripts like recovery-from-boot.p and install-recovery.sh in system.new.dat which reinstall stock recovery, it's what it does to my MX4, but modded flyme certainly don't have these scripts

Understood. Thanks!

furious.builder said:
PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"
Click to expand...
Click to collapse
Is there any risk of brick flashing twrp vía fastboot?
I have seen many mx4 bricked flashing custom recovery with flashify.

Via fastboot there is nearly no risks because if it's flashed it will boot, and if there is something wrong during unlock fastboot has not been unlock so it will not flash, but don't use the one from my link, there is a newer from emmaus.pro

[Official ROM] Desire 816 dual-sim (A5_DUG) - Marshmallow + First OTA Update

Hello, I'm bringing the Official Marshmallow ROM for desire 816 (dual sim) a5_dug and it's pre-rooted and (all credits goes to (xXminiWHOOPERxX)) and how to intall the OTA updates after flashing the ROM
Rom Information:
Code:
Android OS : 6.0
Kernel : Stock
Sense Version : 7.0
Release Keys : 3.12.401.2 release-keys
Download Link: Mega.nz
How to Install the flashable zip using TWRP recovery:
1. place the flashable zip (Sense7-MarshMallow.3.12.401.2_DualDesire816.zip) on the sd card.
2. wipe the cache, dalvik cache, system, data and internal storage (if you don't have any data on your phone).
3. install Sense7-MarshMallow.3.12.401.2_DualDesire816.zip through the install option in TWRP Recovery.
4. reboot the phone when the installer finishes and everything should be fine.
Now you can't install the OTA update with the custom recovery, and even if you reverted back to stock recovery it won't work, so you have to follow the following instructions to install the OTA update on your custom recovery.
How to Install the OTA update
1. download the OTA update from your phone from
Code:
Settings > About > Software Update
, after it finishes the flashable zip of the update should be located in
Code:
data/data/com.htc.updater/cache/
or
Code:
data/data/com.htc.updater/files/
2. it should be something similar to
Code:
OTA_A5_DUG_M60_DESIRE_SENSE70_MR_HTC_Region_3.21.xxx.x_R-3.12.401.2_release_479056hu4q3r1wkhz4b5n3
3. copy it to your pc and extract the zip file.
4. navigate to
Code:
/META-INF/com/google/android
5. you should find a file named
Code:
update-script
, open it with notepad or sublime text or any code editor you use.
6. from line 4 to 9 you should see the following code
Code:
getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys" ||
getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys" ||
abort("Package expects build fingerprint of htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys or htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "htc_a5dug" || abort("This package is for \"htc_a5dug\" devices; this is a \"" + getprop("ro.product.device") + "\".");
replace it with the following:
Code:
#getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys" ||
# getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys" ||
# abort("Package expects build fingerprint of htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys or htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "a5" || abort("This package is for \"a5\" devices; this is a \"" + getprop("ro.product.device") + "\".");
7. save the file with no extension as it is and re-zip the archive using winzip or whatever tool you use to compress as (zip).
8. flash the OTA zip file you made using TWRP or any custom recovery.
Click to expand...
Click to collapse
I've uploaded the modified update-script file just in case you couldn't do this steps so you just have to replace the modified update-script with the original one in the OTA zip file.
Download: update-script

thank you sooo much !!!
but what is ota update and what it use for ?!

Echtar said:
thank you sooo much !!!
but what is ota update and what it use for ?!
Click to expand...
Click to collapse
OTA updates are the software updates you recieve from the phone manufacturer, typically you can't install an OTA update while your phone is rooted so this is the only way to install it.

can you upload OTA + script here?

file get error
i m getting error to flash the ota update file... ?
"/system/bin/app_procss32" has unexpected contents.

the ota wont install. it's still reporting expected device error.
i mean "this is meant for ....."
thanks

guys pelase help my htc 816 dug
wifi not working it on off and i can get it on !!

Echtar said:
guys pelase help my htc 816 dug
wifi not working it on off and i can get it on !!
Click to expand...
Click to collapse
We are on the same boat bro! Did u update to MM from Kitkat? This update is for lollipop users apparently. We are having driver issues..

rohinraj said:
We are on the same boat bro! Did u update to MM from Kitkat? This update is for lollipop users apparently. We are having driver issues..
Click to expand...
Click to collapse
I went back to kitkat 4.4.2. Try this https://forum.xda-developers.com/desire-816/development/26-nov-svhd-v1-0-0-t2953661
this ROM worked for me. And its great!! Wifi works and everything is back to normal.

omartek0 said:
Hello, I'm bringing the Official Marshmallow ROM for desire 816 (dual sim) a5_dug and it's pre-rooted and (all credits goes to (xXminiWHOOPERxX)) and how to intall the OTA updates after flashing the ROM
Rom Information:
Code:
Android OS : 6.0
Kernel : Stock
Sense Version : 7.0
Release Keys : 3.12.401.2 release-keys
Download Link: Mega.nz
I've uploaded the modified update-script file just in case you couldn't do this steps so you just have to replace the modified update-script with the original one in the OTA zip file.
Download: update-script
Click to expand...
Click to collapse
i have made all steps but when i replace update-script and rezip ota folder and put it back on sdcard to flash it
and when i click install zip on cwm it says installation aborted
i tried with TWRP but also not working !!

i am on cm13 can i flash this rom ? from twrp like normal ?

me too on cm13 how can i install this rom pls help

Hi
First thank you
I did all what you said but when i chose to flash Rom zip file from sd
Its stars checking and its begins then gives me install
aborted i dont know why??, can you help me with it to go to the next level to update ota??

I have a question
I bought a cell phone in the US a few years ago, it was blocked by the SPRINT operator, I stayed a long time without using it, and now I decided that I would pack it to use it. I unlocked the bootloader and also the root, put a custom rom but the device is still blocked.
Is there any way to unlock this?
(I'm in Brazil)

.....................

after install cant update ota say mound read-only
what must do?