Related
Hello,
I present to you very shortly and quickly the new Official ROM for OnePlus One : ROM MIUI 4.9.26 (V5). It is the official version !
Warning : this ROM replaces your custom recevery by that of the MIUI ROM (CM)
To download and try this address :
http://en.miui.com/download-249.html (languages : English / Chinese)
Mirror : https://mega.co.nz/#!TdMhxYrZ!BjBLlhuscJb6eFBuB6N7Gis68xGapdCcWFocuXu9sq8
The complete modified ROM 4.9.26 with "update-script_bacon" : https://mega.co.nz/#!fME3nAhD!LHOLv15Ngyb4bHzHFdEoBvoVTYNPBGOBEi0_-9kdH14
Difficulties or delays to download the new ROM ??? The solution : download the update !
Go to the official site : http://en.miui.com/download-249.html (Incremental ROM pack)
Mirrors : Update 4.9.12->4.9.26 https://mega.co.nz/#!vV9AmIZS!Xtu_F5CMvf16ljL-adZtP7XETTRk0SvllT50r8eflTI
The update modified ROM 4.9.12->4.9.26 with "update-script_bacon" : https://mega.co.nz/#!TNtHhSaT!2nnMliV5KITaTXj170ttwul-zVYKAe6vPHSLOmJC5yI
Old [v4.9.5]
Be careful there is a problem in the file of the official ROM : the "updater-script" file keeps flashing properly. It is necessary to change the first line [getprop("ro.build.product") == "A0001"] with [getprop("ro.build.product") == "bacon"] or replace "updater-script" (\META-INF\com\google\android\) with the attached file. (Thanks to Saythis for the solution and lontu for the file).
ROM [v4.9.5] modified with proper updater-script .
https://mega.co.nz/#!DR1ARB4b!wjZUpzuxDt-KWOdyLdX0BTxvext3rQyLOTrfqOx-7Lk
Installation MIUI (or other ROM flashable with custom recovery) :
I remind you that neither I nor the forum we take responsibility for anything, everyone is aware of that is going to do.
Let's go :
1. Download the MIUI ROM and put it in your phone storage
2. Make sure your phone is properly detected by your PC
3. Boot phone in Bootloader Mode (Volume Up and Power) and flash a custom recovery like CWM Advanced Edition Philz Touch (http://forum.xda-developers.com/showthread.php?t=2201860)
4. Reboot in Recovery Mode (Volume Down and Power) and choose :
- Wipe and Format Options -> Clean to Install a New ROM (wipe datas, cache & dalvik-cache)
- or with other custom recovery : wipe data/factory reset -> wipe cache partition
5. After install the ROM, choose :
- Install Zip -> Choose zip from /sdcard -> select your ROM MIUI -> Reboot System Now
- or with other custom recovery : apply update -> choose from internal storage -> 0/ -> MIUI rom -> reboot system now
6. Enjoy MIUI v5 for OPO !
PS : For the GAPPS, install Google Installer from Market, or you can not use the Updater.
Notes:
If 4G is not enabled, use this procedure with the phone keypad *#*#4636#*#* then "phone information" -> "Set preferred network type" -> "TD-SCDMA, GSM/WCDMA and LTE" (or LTE/gsm auto)
Good flash
PS : You can "Thanks" if you want .
Sources : http://en.miui.com/
Any other mirror?
Flashing instructions?
Thanks
Does it wipe everything or not? Does it change the partitions? How do we have to flash?
malcho said:
Any other mirror?
Flashing instructions?
Thanks
Click to expand...
Click to collapse
No, this is the official website and the official server to download.
principino1984 said:
Does it wipe everything or not? Does it change the partitions? How do we have to flash?
Click to expand...
Click to collapse
Yes, wipe everything (custom recovery : datas, cache and dalvik-cache).
Do we need to install Gapps and are there any install notes since unable to see on the download page?
Doesn't flash, gives error: This package is for "A0001" devices; this is a "bacon". Error executing binary in zip
jlevy73 said:
Doesn't flash, gives error: This package is for "A0001" devices; this is a "bacon". Error executing binary in zip
Click to expand...
Click to collapse
Going to have to modify the updater-script and swap out the A0001 for bacon
jlevy73 said:
Doesn't flash, gives error: This package is for "A0001" devices; this is a "bacon". Error executing binary in zip
Click to expand...
Click to collapse
Try to fastboot the kernel first. Or modify the updater-script.
What do you normally do when you flash a new rom... do a FULL wipe...
Can't flash it, i've already miui v4.85 but it says "error updater script"..
Is attached the stock recovery too?
mittimus said:
Can't flash it, i've already miui v4.85 but it says "error updater script"..
Is attached the stock recovery too?
Click to expand...
Click to collapse
Without the exact error we can't help you, it probably says something more ?
If not, try to grab last recovery log, by saving it in sdcard within the recovery or with adb, after a try : adb pull /tmp/recovery.log
And add it in attachement in next post.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Updater-Script
PFA the updated updater-script....need to replace file under META-INF\com\google\android...
Thanks
Which kernel is compatible with this version? Ak doesn't boot
lontu said:
PFA the updated updater-script....need to replace file under META-INF\com\google\android...
Thanks
Click to expand...
Click to collapse
Hello,
Can I use your file "updater-script" to change the ROM and offer for download ?
Thank
mittimus said:
Which kernel is compatible with this version? Ak doesn't boot
Click to expand...
Click to collapse
CM11S version of the AK kernel do work.
malcho said:
Any other mirror?
Flashing instructions?
Thanks
Click to expand...
Click to collapse
I've posted a installation guide and a mirror.
klncdc said:
I've posted a installation guide and a mirror.
Click to expand...
Click to collapse
Where is it posted.? Also is this the new version that was released "official version". If not where can I download that.
In the first post... Yes, official ROM : see in the first post, again.
Envoyé de mon OnePlus One en utilisant Tapatalk
Hi,
Soon (I hope), Flyme 5 will be available for our MX4. So I'd like to know before, how to reinstall flyme without loosing my Philz touch and unlocked BL.
Can I do something like that :
- Download an update.zip
- Convert system.new.dat to system.img
- Copy it to the root of the phone
- Via ADB, flash it with "dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system"
Can this be a good solution to keep Philz touch and unlocked BL ?
Thank you,
Clément
What I have done:
-downloaded MX4 4.2.8.2A (my MX4 is the Chinese version) ZIP, unpacked it in a folder and replaced the stock uboot.img file with the patched one;
-afterwards I have rebuilt the update.zip file with the new folder contents; then I have copied the modified update.zip file to the MX4 internal storage;
-flashed patched MX4 recovery file via FastBoot; got into recovery and flashed the modified update.zip by ticking both boxes (clear data);
My MX4 has booted afterwards just file and I was also able to keep my bootloader unlocked. You should follow these steps when you want to get back to Flyme when you have installed CM12.1 .
I know this method but Flyme 5 come with Android 5.1, patched uboot.img may be incorrect for this firmware no ?
furious.builder said:
Hi,
Soon (I hope), Flyme 5 will be available for our MX4. So I'd like to know before, how to reinstall flyme without loosing my Philz touch and unlocked BL.
Can I do something like that :
- Download an update.zip
- Convert system.new.dat to system.img
- Copy it to the root of the phone
- Via ADB, flash it with "dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system"
Can this be a good solution to keep Philz touch and unlocked BL ?
Thank you,
Clément
Click to expand...
Click to collapse
This probably wont work, I own a mx5 and when you try to go from flyme 5 to flyme 4.5 flashing system partition, it gets stuck at flyme recovery. Probably Flyme 5 requires new Flyme 5 kernel to boot, and it is not compatible with flyme 4.5.
You can also try to put patched uboot to flyme 5 update.zip and flash it, as said before
iicc said:
This probably wont work, I own a mx5 and when you try to go from flyme 5 to flyme 4.5 flashing system partition, it gets stuck at flyme recovery. Probably Flyme 5 requires new Flyme 5 kernel to boot, and it is not compatible with flyme 4.5.
You can also try to put patched uboot to flyme 5 update.zip and flash it, as said before
Click to expand...
Click to collapse
But with patched uboot.img from 4.2.8.2A while flashing Flyme 5 can it cause brick ? :/
furious.builder said:
But with patched uboot.img from 4.2.8.2A while flashing Flyme 5 can it cause brick ? :/
Click to expand...
Click to collapse
I think that it shouldnt cause brick, but maybe Meizu had developed other way to avoid users to unlock bootloader so it causes a brick.. I dont know
I do not think we will ever have a Flyme 5 + unlocked bootloader situation since the only combination right now is 4.2.8.2 + patched bootloader for the same version (patching newer bootloader won't work with current software). So when going to CM I guess it would be always the safest to downgrade to 4.2.8.2.
I think is real, because uboot.img responsible for the initial boot , all as Android is responsible boot.img.
But boot.img on Meizu with closed source.
So the only way will be to flash patched recovery then install official update.zip which will relock BL ? :/
It is the safest option. But you can downgrade to 4.2.8.2 and unlock bootloader to flash roms.
In the case that Meizu locks the downgrade to lower firmwares as they do with the M1 Note, maybe you can flash a lower flyme recovery and flash 4.2.8.2. This is the method to downgrade in M1 Note
Okay I understand But if BL is locked then it's not possible to flash an older stock recovery no ?
Yes, It is possible only if the recovery is from the same version. For example, you can flash chinese flyme recovery but not an international flyme recovery.
But only if boot (kernel) partition have not changed, if not maybe your phone will not boot and you will only can enter to fastboot..
So I dont know what would happen if flashing a Flyme 4.5 chinese recovery in Flyme 5 to downgrade in the case meizu locks the downgrade
Sent from my MX5 using Tapatalk
Okay thank you iicc so we need to wait for Flyme 5
Meizu has said they will not support multilanguaje on chinese roms in Flyme 5, so I think they would not lock the downgrade to Flyme 4.5.
Yeah I know, I'm very disappointed about that... I recommanded Meizu phones to many guys, including my father who doesn't speak English at all, so he bought a MX5 directly from China :/ Very bad choice from Meizu
I got an idea ! Can something like this work ? http://forum.xda-developers.com/showthread.php?t=2387941
furious.builder said:
I got an idea ! Can something like this work ? http://forum.xda-developers.com/showthread.php?t=2387941
Click to expand...
Click to collapse
Mmm probably yes, is a good idea.
Other way to do faster is flashing Flyme 5 system.img using "dd", turn down the phone, boot into the fastboot mode, flash boot.img from Flyme 5 and reboot.
Sent from my MX5 using Tapatalk
I'll try with 4.5.7A
I also read that at every boot Flyme wanted to flash stock recovery, it's not due to system.img nor boot.img ?
Got a problem.... system.img that I extracted from system.new.dat isn't correct so Android Kitchen don't packed it
(It said : NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM)
EDIT : I bypassed the problem I'm uploading the flashable zip for testers
Uploaded : https://mega.nz/#!DR9h0KAQ!ZfWMCbeZrxH7SyxlCeOMA8HT6Ilte51o2z9WbLkauW8
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
Here is what I did to downgrade from 6.0 to 5.0:
1- Download and Install all the required drivers
https://mega.nz/#!tENxTCYI!U_2KD352HgqqsK2qkY7g4xsUIVMhHwOol9aiiDMIs28
2- Download the asus flash tool 1.14
https://mega.nz/#!JF91lazI!lQSdQcN5YXIFsaCWtTVHfsvGK1u82NKvy8-X9XIfR0g
3- Download the Latest WW_ZE551ML_2.20.40.194_20160713.raw firmware [Mega Mirror]
https://mega.nz/#!MRtTCCzZ!c2qoqIX8drgNRy2KxPV_iiBVKHoW2ppFdwRUsLjIWq4
4- Use the ASUS flash tool to flash the raw image
-Double click the ASUS flash tool Icon to launch it
-reboot your phone on bootloader mode and connect it to your PC
-Choose your device from the list which is in ASUS flash tool
-Locate the raw image
-Click on the serial number which appears on the screen within ASUS flash tool
-Select wipe data
-Click the start button to start flashing
-Wait until you see the message successfully flashed
Note that the whole flashing process takes about 6 minutes.
Enjoy!
Reserved
Ended in error, with wrong image format or error 1
ended in "error: permission denied"
This tutorial won't work, already tried this before when i'm thinking of reverting from MM Beta back to LP Stock, somewhere i've found a post that worked for me, all credits to @BlackForward
BlackForward said:
Hi, I do not speak English very well, but I'll try.
First go to the website of Asus, and download the firmware .. 184 or this link (http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.147549438.850793534.1463019251) and put the external SD Card!!!
NOTE: If your bootloader is similar to the image (with the blue letters ..), you just need to step 3 of this my turorial
ht*tp://www*androidheadlines*com/wp-content/uploads/2015/05/asus-zenfone-2-google-howto-1.jpg (remove "*" again^^)
1. Go to this page (https://www.techmesto.com/root-zenfone-2/) and follow the steps of the second method..
1.1 Download Z00A_WW_2.20.40.184 version (https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw)
1.2 Download and extract FlashTools (http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927)
1.3 Extract Z00A_WW_2.20.40.184_system_w_root.zip (for step 1.1) and put the "system.img" in the folder of FlashTools together with "boot.img", "droidboot.img" and "recovery.img"
2. Now follow the steps of the second method (https://www.techmesto.com/root-zenfone-2/), from step 7 to 11;
3. Also I was stuck in the bootloader after this procedure... BUT, you need to download this file (the first method): http://www.mediafire.com/download/v6m7n9j0gqins9b/CWM_Zenfone_2_Intel.zip;
3.1 And follow the steps from 1 to 9 (the first method): https://www.techmesto.com/root-zenfone-2/... EXCEPT: The steps include the root (you do not need the root ..)
3.2 When you are already in CWM recovery, only install the firmware 184 (of start.. of Asus) which is in the external SD Card ... and end ^^.
3.3 I recommend wipe data / factory after starting the device first time...
I have helped
Click to expand...
Click to collapse
If you end up bricked
.and you didn't do any crazy cmds in fastboot mode.
Check my signature
I had been running the MM beta up until this point. I just flashed the .184 RAW file. What made me go back you ask? I figured out that Google Opinion Rewards was not working. I can't live without that.
I can confirm that this method works for ZE550ML on mm beta .69 firmware. I downloaded AFT and flash RAW (Lollipop .149 firmware). Successfully downgraded bootloader unlocked and flashed CM13.
P.S. My status before downgrade was unrooted and bootloader locked and was on .69 mm beta build.
Raiden01 said:
I can confirm that this method works for ZE550ML on mm beta .69 firmware. I downloaded AFT and flash RAW (Lollipop .149 firmware). Successfully downgraded bootloader unlocked and flashed CM13.
P.S. My status before downgrade was unrooted and bootloader unlocked and was on .69 mm beta build.
Click to expand...
Click to collapse
How did you unlock on .69 build?
HungNgocPhat said:
How did you unlock on .69 build?
Click to expand...
Click to collapse
I found a one click bootloader unlock from xda. I downgraded to lollipop .149 firmware and the unlocked bootloader.
Here's the link for unlocking bootloader on lollipop
http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
Also there's a method by shakalaca to unlock bootloader in mm beta. I haven't tried it personally because many report that their phones got bricked and most of them could be recovered by xFSTK method.
http://image.prntscr.com/image/734e565caff14053b6a9a0a394b3cddc.png
Error while flashing it, then "permission denied"
Yousvel said:
3- Download the latest raw image WW_ZE551ML_2.20.40.184_20160504.raw
https://yadi.sk/d/4cuw246vryaZA
Click to expand...
Click to collapse
The link for the raw file is dead. Here's another. Same version.
https://www.yadi.sk/d/sw4DS-n3sZtcr
returned4good said:
The link for the raw file is dead. Here's another. Same version.
https://www.yadi.sk/d/sw4DS-n3sZtcr
Click to expand...
Click to collapse
Thanks bro! OP is updated with this new link.
Yousvel said:
Thanks bro! OP is updated with this new link.
Click to expand...
Click to collapse
No problem. It was actually a difficult search. Maybe a mod can add it to the Resources thread.
returned4good said:
No problem. It was actually a difficult search. Maybe a mod can add it to the Resources thread.
Click to expand...
Click to collapse
I will upload the latest raw image version .94 soon
Work for me. OTA works to.
Thx!!!
rafaelcremm said:
Work for me. OTA works to.
Thx!!!
Click to expand...
Click to collapse
Thanks for your feedbacks.
OP updated with the latest WW_ZE551ML_2.20.40.194_20160713.raw firmware [Mega Mirror]
Will this work if I unlocked my phone using this? http://forum.xda-developers.com/zenfone2/general/unlock-zenfone2-android-6-0-beta-unlock-t3411264
Yousvel said:
OP updated with the latest WW_ZE551ML_2.20.40.194_20160713.raw firmware [Mega Mirror]
Click to expand...
Click to collapse
Please, remember to press the thanks button if this is helpful to you.
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?