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
Related
I've been trying to install the April 7th Nightly of CM 10 on my L7, but the installation aborts on the product check.
Code:
assert failed: getprop("ro.product.device") == "p700" || getprop ("ro.build.product") == "p700"
The phone is a P700, not a 705 or 708 and is currently running the pre-rooted V20a with CWM v6.0.2.8.
Any advice?
Sorry, found out in the meantime that this seems to be a bug in the touch-based CWM.
Eismagier said:
Sorry, found out in the meantime that this seems to be a bug in the touch-based CWM.
Click to expand...
Click to collapse
Had this problem too, just edit the updater-script and remove that specific line.
Download ROM Manager and install the official CWM recovery and then flash CM. Then you won't get any error.
Sent from my GT-I9070 using xda premium
Thanks, I'll keep that in mind for next time. For now, I'm using the non-touch CWM.
New build is available to download.
Download link http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.0_community_build/
for those who stuck in boot, flash this recovery through fastboot . https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img Credits: pwseo
For getting to fastboot menu, 1) press power button untill phone has been powered off.
2) first press volume up button then power button until fastboot mode is shown.
3)Use the following command to flash the recovery. (Note:adb and fastboot should be installed first. get it here:http://forum.xda-developers.com/showthread.php?t=2317790)
fastboot flash recovery opx_oos3_recovery.img
Click to expand...
Click to collapse
source https://forums.oneplus.net/threads/oxygenos-3-1-0-marshmallow-community-build-for-oneplus-x.460857/
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
I read the thread, i think need to flash stock Recovery before flashing
motherninja said:
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
Click to expand...
Click to collapse
You can flash it thorough official twrp or stock recovery
You can also keep your recovery, but you have to slightly modify your package.
1. Unzip package.
2. Go to META-INF\com\google\android\
3. Edit updater-script with notepad++, or just with any text editor.
You should see "getprop("ro.build.product") == "OnePlus" || abort("This package is for \"OnePlus\" devices; this is a \"" + getprop("ro.build.product") + "\".");"
4. You can delete this line or change getprop("ro.build.product") == "OnePlus" to getprop("ro.build.product") == "One". In my case I had to change it into getprop("ro.build.product") == "onyx".
5. Save it and zip whole package.
6. Flash it and enjoy
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Still waiting for a solution. :/
Waiting for opinions before flash hehe
motherninja said:
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Click to expand...
Click to collapse
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
hotlinksxz said:
Waiting for opinions before flash hehe
Click to expand...
Click to collapse
Same here ...till some one compile the ROM which can be flash through TWRP
maybe i will wait for bug fix before flash..this is the first oos 3 for opx so it will be buggy
Sent from my ONE E1003 using XDA-Developers mobile app
kethsawant said:
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Same here ...till some one compile the ROM which can be flash through TWRP
Click to expand...
Click to collapse
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Any update on VOLTE?
Root
With Kingroot YouTube can get root, maybe with flashfire you can install twrp?
Edit: Can't install twrp but can install xposed.
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Danish66 said:
Any update on VOLTE?
Click to expand...
Click to collapse
+1
Yes Guys..Can someone share any info here on this topic in the latest Oxygen OS build ??
motherninja said:
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Click to expand...
Click to collapse
hmm same here,cant get into recovery,twrp needs to be updated by the devs i think
also directly booting into twrp fails too,"dtb " not found
gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
How u did it?
Mind sharing step by step?
Thanks in advance.
gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
With twrp? How?
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
gahehe said:
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
Click to expand...
Click to collapse
But you won't be able to boot back into twrp, so it's kinda useless. Better to have stock recovery than not being able to boot back into twrp=p
Unless you were able to flash supersu with twrp before booting the rom and not being able to boot back into twrp. Was that the case?
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?
ok so i have switched from system mode root to systemless rooting in hopes to do ota updates without flashing that 1.5gb install every week.
now i see my phone downloads the small ota file.
obviously when i tried to just simply update that failed.
fiy: i have the following installed
MagiskSU
systemless xposed
automagisk
TWRP recovery
so i tried to use flashfire and flash the ota (system still unmodified)
and the ota "appeared" to be installed and did the whole loading bar on boot. But when that finished i checked in the settings and i wasnt updated.
then i tried flashing back stock recovery for a sec then try ota again. this time i saw a text flash fast this time saying
"Boot has unexpected contents"
does that mean i have to somehow flash stock boot? i thought flashfire is supposed to do that automatically.
anyone have know the way im supposed to install it?
Did you have the ota file? Please post here
http://en.miui.com/extra.php?mod=rom/download&r=303&mobile=no
Sent from my Redmi 3S using Tapatalk
If you rooted, install exposed, or anything which modified boot.img, you will fail to update ota.
Flash new original boot.img (you can get this on your earlier zip rom), and then update ota.
In short way, updater will calculate old boot.img's checksum. If it mismatch, updater stop to work
SILF0X said:
If you rooted, install exposed, or anything which modified boot.img, you will fail to update ota.
Flash new original boot.img (you can get this on your earlier zip rom), and then update ota.
In short way, updater will calculate old boot.img's checksum. If it mismatch, updater stop to work
Click to expand...
Click to collapse
Are you sure? I tried to install OTA in stock rom with TWRP installed. It checks the Recovery too. OTAs won't install if any single partition is modified.
esarve said:
Are you sure? I tried to install OTA in stock rom with TWRP installed. It checks the Recovery too. OTAs won't install if any single partition is modified.
Click to expand...
Click to collapse
Maybe.
Try to remove this line :
Code:
if (range_sha1("/dev/block/bootdevice/by-name/system", "...") == "2f76590739094f44c4606ec916f33ba31bea0630" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
And then this one :
Code:
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "...") == "5bde53bfa9f927284e1adabf81fe42b7740a7210" then
if range_sha1("/dev/block/bootdevice/by-name/system", "...") == "fcbc37abfcd8b47199c1236416a106c104cf3cc2" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
SILF0X said:
Maybe.
Try to remove this line :
Code:
if (range_sha1("/dev/block/bootdevice/by-name/system", "...") == "2f76590739094f44c4606ec916f33ba31bea0630" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
And then this one :
Code:
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "...") == "5bde53bfa9f927284e1adabf81fe42b7740a7210" then
if range_sha1("/dev/block/bootdevice/by-name/system", "...") == "fcbc37abfcd8b47199c1236416a106c104cf3cc2" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
Click to expand...
Click to collapse
This is a block based OTA I don't think you can edit that part.
Sent from my Redmi 3S using Tapatalk
xdarkmario said:
This is a block based OTA I don't think you can edit that part.
Sent from my Redmi 3S using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/xi...or-how-to-flash-miui-ota-incremental-t3570049
Hi there,
I was wondering if there are any plans to develop a ROM for the J500Y model, because so far I couldn't find one.
Best,
andreas301
Flash the J500F-M-G version, see if it boots, report on forum thread
I'm currently running ResurrectionRemix v5.8.3 (7.1.2) on my J500Y. First I downloaded the ROM for "J500F-M-G" on my PC and then extracted it using WinRAR, then I opened the file > META-INF > com > google > android, then I opened the updater-script using Notepad++, I then removed the assert line (looks like this, can be a bit longer on certain ROMs:
Code:
assert(getprop("ro.product.device") == "j5lte" || getprop("ro.build.product") == "j5lte" || abort("E3004: This package is for device: j5lte; this device is " + getprop("ro.product.device") + "."););
) then I rezipped it and moved it onto my phone then flashed it using TWRP (MAKE SURE YOU ARE ON A LOLLIPOP ROM/BOOTLOADER BEFORE FLASHING, I used the J500F version of TWRP just to make sure it flashed, not sure if it was a necessary step, but if flashing it using the J500Y TWRP after removing the assert lines doesn't work, then try again after flashing the J500F TWRP using Odin) this should work with almost every nougat ROM that can run on the J500F variant, so far I haven't even needed to remove the assert line when flashing a marshmallow custom ROM so there is always that if you still can't get nougat working for you for some reason.