when I am going to apply update from recovery, It is said,
" please upgrade to newest 4.3 image first...
assert failed : getprop("ro.build.version.release")=="4.4.2"
return code 8E:Error in \tmp\update.zip
would anyone provide me signed 4.3 firmwire zip?
thanks
Download Zenodex, it's 4.4.2 Custom rom stock based, and I didn't experience any freezes with it
Related
I am requesting stock recovery for kitkat 4.4.2 build G8. And JB 4.3.
my purpose is that, if we want to update our device via OTA we just need to flash the stock recovery instead of flashing the whole stock firmware via Odin, to avoid the "system modified status"when updating via OTA.
Hey people.
After going back to Lollipop stock, I tried re-rooting and reinstalling recovery.
I tried to use both OneClickRootRecovery and the SRK tool - and in both I get the same problem.
Root seems to be fine and recovery does appear, but with one little thing - I can't flash ANYTHING.
Getting the "Error executing updater binary in zip" when flashing anything.
I tried a ROM, and even the latest TWRP zip. Always the same error.
Any idea how to solve this?
Updating "updater-script"
I am having the same issue on my lg d802. I read in few threads to edit "updater-script" file. I downloaded roms meant for d802 and replaced all "d800" appearing in updater-script with "d802" (not sure that this is what was to be done).
Tried flashing the rom with updated updater-script but still getting the same error message.
Someone kindly help.
Attaching screenshot related to previous post
aryansingh163 said:
I am having the same issue on my lg d802. I read in few threads to edit "updater-script" file. I downloaded roms meant for d802 and replaced all "d800" appearing in updater-script with "d802" (not sure that this is what was to be done).
Tried flashing the rom with updated updater-script but still getting the same error message.
Someone kindly help.
Click to expand...
Click to collapse
Attaching the screenshot of my error:
UPDATE: After extensive reading threads I found the solution. Need to flash jellybean bootloader using "bootloader changer" and then flash AOSP based roms. To restore the stock lollipop one should flash kitkat bootloader back.
The easiest for you who are installing aosp/cm roms is:
1. flash kk stock
2. root and use autorec for kk
3. flash the roms you desire
jelly bean
aryansingh163 said:
Attaching the screenshot of my error:
UPDATE: After extensive reading threads I found the solution. Need to flash jellybean bootloader using "bootloader changer" and then flash AOSP based roms. To restore the stock lollipop one should flash kitkat bootloader back.
Click to expand...
Click to collapse
Does 4.2.2 contain jellybean bootloader? i tried to flash cm12 from 4.2.2 on g2 d800 and nasty error executing update ... appears, what now?
hello everyone , few weeks ago my phone got infected with malwares and bcoz of that i rooted my phone and installed cm12.1 but when i tried to revert back to kitkat am not able to do it and i have tried every way but m not able to succed.
I tried to install stock lolipop recovery , stock kitkat recovery , twrp but none of them working and i always get this error
" no md5 fle found
failed to mount /dev/block/bootdevice/by-name/userdata
E:error executing updater binary in zip"
and this happens only when i try to install stock rom and whenever i install stock lolipop roms and it always succeds
plzz help me to install stock kitkat rom
Flash the kitkat firmware before flashing the rom.. U can find kitkat firmware in Cm 12.1 by Ed300 thread.
I hope that helps!!
malwayzwithu said:
hello everyone , few weeks ago my phone got infected with malwares and bcoz of that i rooted my phone and installed cm12.1 but when i tried to revert back to kitkat am not able to do it and i have tried every way but m not able to succed.
I tried to install stock lolipop recovery , stock kitkat recovery , twrp but none of them working and i always get this error
" no md5 fle found
failed to mount /dev/block/bootdevice/by-name/userdata
E:error executing updater binary in zip"
and this happens only when i try to install stock rom and whenever i install stock lolipop roms and it always succeds
plzz help me to install stock kitkat rom
Click to expand...
Click to collapse
Wipe all system,data,cache and dalvik caches and then flash stock kitkat
Can you Guys Please Tell Me How To Change Software Status From Modified to Official
I Had Rooted My Device, Unlocked Bootloader and Custom Recovery But Never Installed Ant Custom ROM's
So, When The Official Nougat Update Came, I unrooted my device and installed stock recovery
What else do i need to do? Please Help
U need to flash whole firmware, then software status will change to official.
Flashing a stock firmware didnt change mine from modified to ofiicial... but what i found is that you have to flash a stock rom and then update the rom via OTA... here you have to flash a stock rom which already has an ota update... for example the stock rom is "1" and already has an ota update ie "2", then you have to flash "1" first through fastboot/rsd and then update to "2" via ota... it should change from modified to official...
Hi Gurus,
I am dusting off my old AT&T branded S4 (SGH-I337/jflteatt) which still runs KitKat (4.4.2) to Lineage (I think 14.x images are available). The BaseBand version is: I337UCUFNI1. It is out of contract, so no worry about getting any official updates.
The thread here about TWRP for this phone made it look easy to install with the official app from the PlayStore. But after installing TWRP, I get an error 'System software not authorised by AT&T has been found" when I boot either to recovery or to ROM. I am guessing Secure Boot is still actively preventing custom images from booting.
So, how do I bypass this and go about successfully installing Lineage? Will Loki help me do it? Once I install TWRP, is it just a matter of installing official Lineage, or should I make other considerations?
Thanks in advance.
You have to be on the jelly bean MDL bootloader in order to install any custom recovery or ROM. Once you have upgraded to kit kat, you cannot go back. Only the MDL bootloader can take advantage of loki, all other bootloaders (including yours) can't as the exploit was patched in the MK3 firmware I think.