Database Develop

on frf85b yet still getting update notification

Is there a reason why? It says its a 909kb install. I'm rooted with a custom recovery SO I know it wont work, I didn't dismiss the notification either... is there a way I can see it its the same version? I'm sure its not a higher one but just curious as to why I still got a update...

Logcat and get the URL

http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
It's for FRF91, "security update".
Also, http://forum.xda-developers.com/showthread.php?t=715691

Apparently FRF91 :O

Installing.....I hope this fixes exchange.

cybik said:
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
It's for FRF91, "security update".
Also, http://forum.xda-developers.com/showthread.php?t=715691
Click to expand...
Click to collapse
What is security update?

Dunno and I can't install it since I have AmonRA's recovery.
snlu178 said:
Installing.....I hope this fixes exchange.
Click to expand...
Click to collapse
Quoted for personal hope.

Well....that did nothing that I can see. My exchange still does not work right.

from the other thread:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I downloaded the FRF91 build manually from Google, and tried applying it. Interestingly, got an "installation aborted." This is on a stock, AT&T Nexus one.
So anyway, that's one Nexus One it doesn't like!
Edit: Reading through the error (and assuming I'm reading it right) I'm thinking you have to have FRF85B first before FRF91 will apply. It says:
-- Install from sdcard...
finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimah:2.2/FRF85B/42745:user/release-keys" || file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
I guess I'll have to see about tracking down FRF85, but Google pulled it!

coldwave007 said:
I downloaded the FRF91 build manually from Google, and tried applying it. Interestingly, got an "installation aborted." This is on a stock, AT&T Nexus one.
So anyway, that's one Nexus One it doesn't like!
Click to expand...
Click to collapse
A stock FRF85B? It will only upgrade from that.

Update 2.2
I have tried auto update and manual update here... both fail. I'm on FRF85 stock. My annoyance is I can't get the UPDATE notification away from the task bar. Anyone got any tips?
Oh, that and the phone STILL reboots itself. Can't watch long video content on flash without it happening :S
BANE

any bright ideas for us rooted folks on FRF85b with this update notification?

How do i keep the update from showing up at the top the ( security update ) that is. Still on pauls Rom FRF50 and just don't want to update yet I'm happy with the setup i have for a while.

temperbad said:
Is there a reason why? It says its a 909kb install. I'm rooted with a custom recovery SO I know it wont work, I didn't dismiss the notification either... is there a way I can see it its the same version? I'm sure its not a higher one but just curious as to why I still got a update...
Click to expand...
Click to collapse
I am having the same problem as of this morning.

hommiedaklown said:
any bright ideas for us rooted folks on FRF85b with this update notification?
Click to expand...
Click to collapse
Just flash the newest update and you will be golden

http://forum.xda-developers.com/showthread.php?t=715799

Wish people would stop point us to other threads which DON'T HELP.
I'm running Pauls R20. I will install R21 when a pre-bake is available, however I constantly have the "System update available" in the notification bar, and get the pop-up at least once an hour.
There must be a way to stop that from appearing whilst I wait to get a custom ROM of my choice.

i've been updated to Froyo 2.2 on 2nd July...and the build is FRF91! I've got no clue what's the difference as that's where i'm directly upgraded...

[ROM] [BETA] [MIUI] **One Step Closer** [UPDATED 5/27/2011]

just did a small very simple port from nexus s miui to the cmda version.
what works
everything what what i have seen
To Do List
Wimax
Need to fix permissions for mms to work correctly
Need to finish incorporating Sprint menu's into Settings
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How-to:
wipe data
wipe cache
format /system (just in case cause it always helps)
flash and enjoy
Language Pack 1b
Download link for ROM
Full credits for Translation goes to MarkHuk (the man is a genius with translating soo ****ing fast)
follow me on twitter if u want to @jface21
If you feel so inclined, buy me coke (the soda)

Seems like all gsm roms made for 4g say "Roaming indicator off". Hmmm
Uncle Jimmy says hello

snandlal said:
Seems like all gsm roms made for 4g say "Roaming indicator off". Hmmm
Uncle Jimmy says hello
Click to expand...
Click to collapse
yeah a couple things need to be changed/removed thats all. no biggie tho..miui doesnt have carrier label in lockscreen anyways...
edit:
nevermind...i searched

Great work! Is it translated?

derekwilkinson said:
Great work! Is it translated?
Click to expand...
Click to collapse
i havent taken the time to translate it...on the other website there is a link for english translation pack. download that...ill post a link i guess

This is awesome
Sent from my SPH-D700 using XDA App

jumaaneface said:
i havent taken the time to translate it...on the other website there is a link for english translation pack. download that...ill post a link i guess
Click to expand...
Click to collapse
hey no problem i'm just excited for all these roms coming out.. miui and cm7 neither have 4g at the moment but I'm sure since it is merged in aosp it should come soon

snandlal said:
Seems like all gsm roms made for 4g say "Roaming indicator off". Hmmm
Uncle Jimmy says hello
Click to expand...
Click to collapse
Im pretty sure pete knows the fix for the roaming indicator thing. Someone should ask in his vendor thread

CM7 and now MIUI in the same night? Sploosh.
Sent from my Nexus S 4G using XDA Premium App

For some reason this won't flash on my phone. this is the same error i get flashing cm7 as well
assert failed: getprop("ro.product.device") == "crespo4g" || get prop ("ro.build.product") == "crespo4g" || getprop("ro.product.board") == "crespo4g"
E:Error in /sdcard/miui.zip
(Status 7)
running latest cwm recovery
in bootloader, it says product name: herring. is that normal? should it be crespo4g?

mikeyinid said:
Im pretty sure pete knows the fix for the roaming indicator thing. Someone should ask in his vendor thread
Click to expand...
Click to collapse
yeah i saw the fix and i will include it tomorrow when i fix wifi (which i broke)

Just wiped everything and flashed this and WiFi is borked. Anyone else having this issue?
Sent from my Nexus S 4G using XDA Premium App

couraage said:
Just wiped everything and flashed this and WiFi is borked. Anyone else having this issue?
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
I think you could probably flash a kernel and fix it...Grab one of netarchys universals.

****ty ass cdma stuf
Click to expand...
Click to collapse
hahaha aha

derekwilkinson said:
hey no problem i'm just excited for all these roms coming out.. miui and cm7 neither have 4g at the moment but I'm sure since it is merged in aosp it should come soon
Click to expand...
Click to collapse
CM7 for the Evo does have 4G (wimax) working, if that's what you meant.

Flashing Netarchy's Universal fixes wifi but after restoring apps from TB, I get fcs anytime I try to open the launcher settings.
Sent from my Nexus S 4G using XDA Premium App

derekwilkinson said:
For some reason this won't flash on my phone. this is the same error i get flashing cm7 as well
assert failed: getprop("ro.product.device") == "crespo4g" || get prop ("ro.build.product") == "crespo4g" || getprop("ro.product.board") == "crespo4g"
E:Error in /sdcard/miui.zip
(Status 7)
running latest cwm recovery
in bootloader, it says product name: herring. is that normal? should it be crespo4g?
Click to expand...
Click to collapse
You need to be on CW 3.1 which I bet your not. Upgrade and try again. I did via ROM manager.

Flashed it and had a few problems.
As stated before wifi wasn't working.
Tried getting into any of the settings only to have it FC every time after applying themes.
Overall it was about 98% effective for daily use but I ended up flashing over CM7.
Waiting on a full MIUI port though

Authentik said:
Flashed it and had a few problems.
As stated before wifi wasn't working.
Tried getting into any of the settings only to have it FC every time after applying themes.
Overall it was about 98% effective for daily use but I ended up flashing over CM7.
Waiting on a full MIUI port though
Click to expand...
Click to collapse
Same issues. Can't wait until its 100%.
Sent from my Nexus S 4G using XDA Premium App

Thank you!!!
Your doing great work and loving the too cool for school atitude!!! AMERICAAA [email protected]# YEAH!!!!

[DEV]CM9/ICS Work-In-Progress

Only for developers!
IT CAN KILL YOUR PHONE!​​​​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 9.0 COOPER KANG ALPHA Android 4.0.3 ICS by TeamHackAce
TEAM:
axel2033 (I am)
Grif07
lagloose
EmoBoiix3
slaid480
djsky2011
wayland_ace
FIRST ALPHA VERSION!!!
configs on github
ALPHA 10
download
Changelog:
Alpha 1-first release
Alpha 2-use kernel by Wayland_ACE, only software acceleration, use js engine
Alpha 3-many files pached and kernel too, don't work adreno 200
Alpha 4-Touchscreen fixed!
Alpha 5-touch working, audio working
Alpha 6-Screen is not flickering, but very slow. Touch works, bad very badly
Alpha 7-Device can wake up from sleep
Alpha 8-Fix touch
Alpha 9-fix wi-fi
Alpha 10-android 4.0.3, fix gallery, audio and network stats
Gapps for ICS
multiupload
Please DONATE ME
PayPal : KY32FMN633JNE
WebMoney :
WMZ : Z133095981000
WME : E310660703253
​

Does it boot normally? It's possible to get any screenshots (I know this is a nob question, but I will see how it looks). What about the performance?

Omg.. ICS finally on our Ace.. Will wait until it's released for end users like me.. +1 for the effort.. Go CM9..

dragonnn said:
Does it boot normally? It's possible to get any screenshots (I know this is a nob question, but I will see how it looks). What about the performance?
Click to expand...
Click to collapse
It is first build and it can't work(

Axel2033 said:
It is first build and it can't work(
Click to expand...
Click to collapse
The means no boot? Nothing? Ok waiting for the next effects of you work, you are amazing.

are you killing me what we will do first axel2033,fixing kernel??

slaid480 said:
are you killing me what we will do first axel2033,fixing kernel??
Click to expand...
Click to collapse
I don't think why it don't work(
I think problrm in kernel
may be ketut can hepl)

Axel2033 said:
I don't think why it don't work(
I think problrm in kernel
may be ketut can hepl)
Click to expand...
Click to collapse
ketut is in china for the moment dude

Hope we get this as a new Year Gift

Axel2033 said:
I don't think why it don't work(
I think problrm in kernel
may be ketut can hepl)
Click to expand...
Click to collapse
check coolya's github I think he has a fixes kernel for cm9!!!

last change in cooly's kernel was 20 october

Which problem do u have now? No mount or surfaceflinger wait files?

Axel2033 said:
last change in cooly's kernel was 20 october
Click to expand...
Click to collapse
what kernel are u using, was about to port from this https://github.com/ilarrain/kernel_galaxyace

Update the update-script )
Assert failed on device getprop
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
Change this:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830");
Click to expand...
Click to collapse
to this:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" || getprop("ro.product.board") == "cooper" || getprop("ro.product.model") == "cooper" ||
getprop("ro.product.device") == "GT-S5830L" || getprop("ro.build.product") == "GT-S5830L" || getprop("ro.product.board") == "GT-S5830L" || getprop("ro.product.model") == "GT-S5830L" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830" || getprop("ro.product.model") == "GT-S5830");
Click to expand...
Click to collapse

djsky2011 said:
what kernel are u using, was about to port from this https://github.com/ilarrain/kernel_galaxyace
Click to expand...
Click to collapse
i built my kernel from this sources but it don't work too(

shouldnt the update script read format("ext4", "EMMC", "/dev/block/stl12");
instead of
format("ext4", "EMMC", "/dev/block/stl12", "0");
EDIT: nevermind it basically does the same thing

Second problem of this build is - kernel.
1) no mount
2) no proper sysfs entries for surfaceflinger

Axel2033 said:
i built my kernel from this sources but it don't work too(
Click to expand...
Click to collapse
what about porting from another device with similare hardware stuff???

Wayland_ACE said:
Second problem of this build is - kernel.
1) no mount
2) no proper sysfs entries for surfaceflinger
Click to expand...
Click to collapse
I tried six kernels

Axel2033 said:
I tried six kernels
Click to expand...
Click to collapse
I can fix second error very easy with kernel recompile, but I dont know how to fix no mount error.

[AOSP] AOSP flashable zip 6.0.1

thanks to @zacharias.maladroit for the kernel and system.img in this aosp build and @celderic for for letting me use his rom as a base for this. this can be dirty flashed over the stock firmware but it is recommended that you disable any form of lock screen security when you do so.
link: https://drive.google.com/file/d/0B1GT7O5RajNnSE9HT1RWU3N3MzA/view?usp=sharing
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR HOUSE CATCHES FIRE OR YOUR PHONE BLOWS UP BECAUSE OF THIS YOU ARE CHOOSING TO DO THIS MODIFICATION TO YOUR DEVICE THUS,YOU WILL BE RESPONSIBLE FOR THE CONSEQUENCES

Nice :good:
Haha - that disclaimer is somewhat large,
the "relevant" part almost goes unnoticed

_LLJY said:
thanks to @zacharias.maladroit for the kernel and system.img in this aosp build and credit to the guy who made the slim stock rom for letting me use his rom as a base for this. this can be dirty flashed over the stock firmware but it is recommended that you disable any form of lock screen security when you do so.
link: https://drive.google.com/file/d/0B1GT7O5RajNnMF9NVnVNVVliLUU/view?usp=sharing
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR HOUSE CATCHES FIRE OR YOUR PHONE BLOWS UP BECAUSE OF THIS YOU ARE CHOOSING TO DO THIS MODIFICATION TO YOUR DEVICE THUS,YOU WILL BE RESPONSIBLE FOR THE CONSEQUENCES
Click to expand...
Click to collapse
failed to mount '/system' (invalid argument)

Dockyy said:
failed to mount '/system' (invalid argument)
Click to expand...
Click to collapse
i have fixed that issue will reupload once zip has finished signing

_LLJY said:
i have fixed that issue will reupload once zip has finished signing
Click to expand...
Click to collapse
nice

_LLJY said:
i have fixed that issue will reupload once zip has finished signing
Click to expand...
Click to collapse
new version: use the one in the first post instead

_LLJY said:
new version: https://drive.google.com/file/d/0B1GT7O5RajNnVmVkNmFIQTNJWUk/view?usp=sharing
Click to expand...
Click to collapse
same issues
run under twrp 3.0.1-0 from androplus

Dockyy said:
nice
Click to expand...
Click to collapse
reupload: edit use the one in the first post instead

Dockyy said:
same issues
run under twrp 3.0.1-0 from androplus
Click to expand...
Click to collapse
hmm seems wierd, try mounting system before flash?

_LLJY said:
hmm seems wierd, try mounting system before flash?
Click to expand...
Click to collapse
indeed i can't mount system partition idea ?

Dockyy said:
indeed i can't mount system partition idea ?
Click to expand...
Click to collapse
that might be a problem caused by the first zip, try installing system.img from the zip via fastboot, then boot into recovery and try again

_LLJY said:
thanks to @zacharias.maladroit for the kernel and system.img in this aosp build and credit to the guy who made the slim stock rom for letting me use his rom as a base for this.
Click to expand...
Click to collapse
I don't think we've ever spoken before, it would be polite to ask instead of making things up saying i let you when we had no conversation about that.
i'm not going to report you as this could be a misunderstanding, but please ask next time and say what you are using from my rom.

celderic said:
I don't think we've ever spoken before, it would be polite to ask instead of making things up saying i let you when we had no conversation about that.
i'm not going to report you as this could be a misunderstanding, but please ask next time and say what you are using from my rom.
Click to expand...
Click to collapse
I am sorry but this is a misunderstanding, we have talked before via PM and (although for a separate project) you did let me use your update script from your ROM

_LLJY said:
I am sorry but this is a misunderstanding, we have talked before via PM and (although for a separate project) you did let me use your update script from your ROM
Click to expand...
Click to collapse
You're right that was a few months ago! Just looked through my messages, can't seem to find what I replied to you though.
Strange as I don't remember at all haha, maybe I misunderstood your question at the time. Sorry my previous post seems rather rude now.
Do you need any help? I see you're having issues flashing the system image, what base of mine are you using? The simple one from my first 5.1.1 rom, or my aroma one from the latest 6.0?
Edit-
You where right, made a fool out of myself now haha sorry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my E6653 using Tapatalk

celderic said:
You're right that was a few months ago! Just looked through my messages, can't seem to find what I replied to you though.
Strange as I don't remember at all haha, maybe I misunderstood your question at the time. Sorry my previous post seems rather rude now.
Do you need any help? I see you're having issues flashing the system image, what base of mine are you using? The simple one from my first 5.1.1 rom, or my aroma one from the latest 6.0?
Edit-
You where right, made a fool out of myself now haha sorry.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yes you are most welcome to help, I am having issues getting the system partition to mount and flash properly, I am using your simple 5.1.1 update script.

_LLJY said:
Yes you are most welcome to help, I am having issues getting the system partition to mount and flash properly, I am using your simple 5.1.1 update script.
Click to expand...
Click to collapse
ifelse(is_mounted("/system") == "/system", unmount("/system"));
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
package_extract_file("system.img", "/dev/block/bootdevice/by-name/system");
From what I remember, that is the script I used in that version of my rom.
Try this -
ifelse(is_mounted("/system") == "/system", unmount("/system"));
format("ext4", "EMMC", "/dev/block/mmcblk0p43", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p43", "/system");
package_extract_file("system.img", "/dev/block/mmcblk0p43");
Sent from my E6653 using Tapatalk

Actually I've tried the patched flashable and got into the same problem, but resolved by extracting the system.img from zip and manually flashing it, but now i have another problem, i forgot about the pin lock and now I'm stuck at the lockscreen, tips?

Will I run into problems if I flash this on E6683?

I factory reseted the phone to bypass the pin, the rom is very laggy and unusable from my experience, but looking forward to use it as a daily driver as soon as the problems are fixed

udbhav.vy said:
Will I run into problems if I flash this on E6683?
Click to expand...
Click to collapse
yeah, it might not working properly,
@erikcas is the expert on dsds (dual sim) devices - he has written a single sim, dual sim detection script and kernel changes that got included upstream in the kernel,
there might be some additional changes needed,
I thought that full support was in AOSP itself but apparently it needs some modifications still
superalin98 said:
I factory reseted the phone to bypass the pin, the rom is very laggy and unusable from my experience, but looking forward to use it as a daily driver as soon as the problems are fixed
Click to expand...
Click to collapse
never EVER call an AOSP ROM laggy unless you haven't locked and unlocked the phone after the boot at least once, lol
Did that help ?

Bootloader Unsupported!

Guys help me out.
I have flashed the latest twrp 3.1.0.0 on my moto g, later I have tried to flash RR 5.7.4 with pico gapps.
Whenever I try to flash custom roms it saying "Update process ending with ERROR 7"
It says the reason: This package supports bootloader: 0x4882, 0x4883, 0x4886 ; This device has bootloader 0x4887.
[See attached image]
How to solve this?
Sent from my Moto G 2014 using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached image here
Sent from my Moto G 2014 using Tapatalk

bennyrichardaon said:
attached image here
Click to expand...
Click to collapse
1 this is the wrong place where write this
2 the error is that your bootloader is newer than the ones supported. Now, we know that downgrading bootloader is impossible, so you need to modify the updater-script file in the rom zip file. To do that, use google; i'll not write here how to do that
Sent from my Moto G 2014 using XDA Labs

Zenzfum000 said:
1 this is the wrong place where write this
2 the error is that your bootloader is newer than the ones supported. Now, we know that downgrading bootloader is impossible, so you need to modify the updater-script file in the rom zip file. To do that, use google; i'll not write here how to do that
Sent from my Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
I'm sorry for writing here, coz I was afraid and in hurry.
Flashing stock marshmallow wont solve this problem?
Sent from my Moto G 2014 using Tapatalk

bennyrichardaon said:
Flashing stock marshmallow wont solve this problem?
Click to expand...
Click to collapse
You can flash whatever you want but many marshamallows roms and older doesn't "support" new bootloader, you need to add it in the update-script file.
For sure you can install nougat roms now
Sent from my Moto G 2014 using XDA Labs

Zenzfum000 said:
You can flash whatever you want but many marshamallows roms and older doesn't "support" new bootloader, you need to add it in the update-script file.
For sure you can install nougat roms now
Sent from my Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
Thank you bro, I'm gonna try with Nougat rom now.
Sent from my Moto G 2014 using Tapatalk

Solution is:
Get a zip file manager (7-zip, file-roller, Betterzip, ...) and search the xyz-rom.zip for META-INF/com/google/android/install-script. Extract the install-script (or edit directly inside xyz-rom.zip) and edit the install-script with your choosen text editor.
Remove everything to line:
ifelse (...) ... this ist the first line of the new edited install-script and leave all coming below as it is. Now put the edited install-script back in your xyz-rom.zip and save it.
### Just be sure it's a Rom for your device ^^
This removes the bootloader check for the Moto G 2014. So don't flash Nougat Rom, if you have KitKat bootloader.
###
Now check out all the good 'ol ROMs
### EDIT: Solution 2 ###
If you know that you have bootloader 0x4887 you just replace 0x4886 with 0x4887 in install-script:
Search for:
( ... )
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4886"
( ... )
Edit to:
( ... )
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4887"
( ... )

Download and flash old bootloader file and flash ,flashing would be fail, boot again and flash again and boot and flash old bootloader, in fastboot mode will see 48.86 written. That may downgrade or help out you.
Sent from my XT1068 using Tapatalk