Database Develop

[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!!!!

Android Open Kang Project - vibrantmtd - build 35

{
"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"
}
Check out the ROM Feature list here.
Check out the comprehensive FAQ by brainfire!
Newest change logs are available at the AOKP site
Make sure you're on the latest CWM
MAKE A NANDROID
wipe data/factory reset in recovery
flash ROM
flash Gapps
reboot
Find all builds and milestones at the AOKP site. If unsure hit the "Releases" tab and you'll find them ordered by latest release!
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to me
Donate to Whitehawkx
Donate to Jonathan Grigg
Donate to Zaphod-Beeble
Donate to ProTekk
Donate to CyanogenMod
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Check out the ROM source on github. Open source, in the spirit of community kangage.
If you'd like to help with AOKP, please don't hesitate to contact me. I'd love to get as many developers in on this as possible!
Best way to help out or contact us is via IRC.

mute/unmute probably exists
gps probably doesn't work
the rest you tell me

Romanbb said:
mute/unmute probably exists
gps probably doesn't work
the rest you tell me
Click to expand...
Click to collapse
Why hello there... SECCY BEAST YOU!
I THINK, i just wet my pants....
Sh!t bro, just as I got done setting my phone up from the Zen Mastah, ICZenwitch!!
Edit:
I just noticed, while reading this thread, it brings me to tears to see all the "Big Devs" in this thread....
I see Romanbb, iynfynity, Shredd, Br1ck'd, Dougfresh, Alex9090, Moped, Scrizzers, Mr_Psycho, vibranturk, Smartassassin, oka1 (thru a thanks, but still counts as him reading this thread, you know you miss the Vibes bro!), 12paq, and ddanc1984.............
Damn. All we need is Whitehawkx, Dan_Brutal, Eugene373, MasterTM, and especially Jellette... Collab of the BIG WHIGZ!
Ok, i'm done crying, about to try this baby out... Ok, maybe tomorrow, lol. Gotta fix my keyboard issue in Zen Master's Domain

Wohoo AOKP...

The best rom.
I send PM please read it.

What in the world are you doing back in the vib section
WooWee thanks
Is this going to be TRIGGER ICY BLOODY BULLET lol
---------- Post added at 04:31 AM ---------- Previous post was at 04:10 AM ----------
If y'all don't know THIS dude made the vibrant not suck!

Can i flash this Rom on my Vibrant 4G??? I959v ?
Sent from my HTC Desire using Tapatalk

sam razzy said:
Can i flash this Rom on my Vibrant 4G??? I959v ?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
absolutely not

Tried to install and got a (status 7) installation error?
About to try again, but I just figured I'd post it while I mess with it.

uurrnn said:
Tried to install and got a (status 7) installation error?
About to try again, but I just figured I'd post it while I mess with it.
Click to expand...
Click to collapse
Might be a bad download try redownloading. Flash the rom and then the gapps and reboot after.
Sent from my Galaxy Nexus using xda premium

krazie1 said:
Might be a bad download try redownloading. Flash the rom and then the gapps and reboot after.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's what I figured. About to try now, will report back.

Roman, Br1ckd has a dope version of you're ****
We'll be honored

Hmmm Return of 7zip hero..
uurrnn said:
Tried to install and got a (status 7) installation error?
About to try again, but I just figured I'd post it while I mess with it.
Click to expand...
Click to collapse
I think status 7 error comes from different recovery so after you get that error reboot into recovery again and reflash.

assert failed: getprop("ro.product.device") == "vibrant" || getprop("ro.build.product") == "vibrant" || getprop ("ro.product.device") == "vibrantmtd" || getprop("ro.build.product") == "vibrantmtd" || getprop("ro.product.device") == "SGH-T959" || getprop("ro.build.product") == "SGH-T959"
Error (Status 7)
Installation Aborted
:|
Tried a new DL, tried rebooting recovery.

Same error 7
Cant install, get the same error. smack my ass

dudeimgeorge said:
Cant install, get the same error. smack my ass
Click to expand...
Click to collapse
Good to know it's not just me.

uurrnn said:
assert failed: getprop("ro.product.device") == "vibrant" || getprop("ro.build.product") == "vibrant" || getprop ("ro.product.device") == "vibrantmtd" || getprop("ro.build.product") == "vibrantmtd" || getprop("ro.product.device") == "SGH-T959" || getprop("ro.build.product") == "SGH-T959"
Error (Status 7)
Installation Aborted
:|
Tried a new DL, tried rebooting recovery.
Click to expand...
Click to collapse
Assert scripting issue?

yeah re-downloaded it 4 times. and tried installing..same issue.
WISH I WENT TO SLEEP 3 hours ago. SMACK. MY. ASS.

dudeimgeorge said:
yeah re-downloaded it 4 times. and tried installing..same issue.
WISH I WENT TO SLEEP 3 hours ago. SMACK. MY. ASS.
Click to expand...
Click to collapse
First, welcome back, Roman!
Just put one of those keywords in the "ro.product.device" or "ro.build.product" lines in /system/build.prop, then reboot to CWM recovery to flash AOKP. Most likely, you are running a rom that has "GT-i9000" or "galaxymtd" in these fields.
Suitable keywords are "vibrant", "vibrantmtd", or "SGH-T959".
MP
EDIT:
I added a CWM flashable to make things a bit easier. Flash this first, then immediately flash the AOKP rom.
This overwrites your current /system/build.prop with the one from Roman's AOKP rom. This should also work if you formatted the /system partition, and are also getting the assert error.
RE-EDIT: Assert doesn't prevent installation, even if /system is formatted. "Fix" did not resolve status 7 errors, so I'm pulling the script. It appears to be un-necessary.

thank you for trying..but this did not fix it. every time i change the keyword to one of the options it would reply back on the status 7 with another one...and even after using your fix buildprop zip..no go
once again... smack my ass

[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 ?

[ROM][n4][android7.1]MoKee71.0-NIGHTLY for the Nexus 4

The MoKee 71.0 (Android 7.1) for the Nexus 4.
{
"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 have pushed the latest source to MoKee, and MoKee have build the nightly rom for nexus4 successful!
Now you can download the latest Rom from http://download.mokeedev.com/?device=mako
and I will continue to improve the function, MoKee will also continue to modify and add exciting new features.
Also very grateful to @stephanmc 's work. Without his results I will have a hard time getting the job done.
Downloads: http://download.mokeedev.com/?device=mako
- Gapps (ARM/7.1/Pico is fine)
[Install]
- Download latest MoKee Rom from http://download.mokeedev.com/?device=mako
- Flash and boot the latest TWRP
- Wipe System + Dalvik cache + cache.
- Flash the Rom
- Flash gapps (If you want)
- Reboot and Enjoy
[Any Bug? ]
- Has not been found
[Source ]
- https://github.com/MoKee
[Changelog]
- http://changelog.mokeedev.com/
If you are a developer and need help, email to me([email protected]), I will try to help you.
:highfive:If you like it, please hit thanks button, and you can make me a donation to support development, or share with others.
And I'm trying to make Android6.0 Rom for SHARP SBM303SH, the official kernel source is very old. I am using caf msm8974 lastes kernel sources to build it. If you are interested, you can contact me([email protected]).
XDA:DevDB Information
MoKee71.0(android7.1), ROM for the Google Nexus 4
Contributors
countstarlight, countstarlight, stephanmc
Source Code: https://github.com/MoKee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: MoKee open source
Version Information
Status: Nightly
Created 2016-11-23
Last Updated 2016-11-23

Mmm...The pictures are too large.

was a thread already open?
http://forum.xda-developers.com/nexus-4/development/rom-official-mokee-source-project-t3505589

Cizzle4 said:
was a thread already open?
http://forum.xda-developers.com/nexus-4/development/rom-official-mokee-source-project-t3505589
Click to expand...
Click to collapse
The MoKee 6.0 and above source is only for developers, if you are a developer, you can contact the administrator.

countstarlight said:
The MoKee 6.0 and above source is only for developers, if you are a developer, you can contact the administrator.
Click to expand...
Click to collapse
im not the dev, just a random user who saw 2 thread about the same rom

countstarlight said:
[Any Bug? ]
- Has not been found
Click to expand...
Click to collapse
Can anybody confirm that DRM protected videos can be played on this rom - it doesn't work on any other Nougat varsion I've tried

spysiuk said:
Can anybody confirm that DRM protected videos can be played on this rom - it doesn't work on any other Nougat varsion I've tried
Click to expand...
Click to collapse
Can you give me a sample video? I will go to test and adjust.

countstarlight said:
Can you give me a sample video? I will go to test and adjust.
Click to expand...
Click to collapse
I've compiled current ExoPlayer (https://google.github.io/ExoPlayer/) demo application (attached) and have problems playing Widevine Secure videos - I'm attaching logs where you can see that there're DRM related errors.
Also applications from playstore like CANAL+ Sport Online (https://play.google.com/store/apps/details?id=pl.ncplus.canalplussportonline&hl=pl) doesn't play videos.
I think that this is caused by DRM security level which is set to L1 (which is not supported on Nexus 4 on Nougat?) and those videos can't be played on L3:
11-26 12:49:02.714 19067-19079/? E/QSEECOMAPI:: Error::Cannot open the file /firmware/image/tzapps.mdt
11-26 12:49:02.714 19067-19079/? E/QSEECOMAPI:: Error::Loading image failed with ret = -1
11-26 12:49:02.714 19067-19079/? E/DrmWidevineDash: Error: Service_Initialize: Loading tzapp image failed, ret = -1
11-26 12:49:02.714 19067-19079/? D/DrmWidevineDash: Service_Initialize: ends! returns -1
11-26 12:49:02.714 19067-19079/? E/DrmWidevineDash: service_initialized returned failure
11-26 12:49:02.714 19067-19079/? D/DrmWidevineDash: OEMCrypto_Initialize: ends! returns 1
11-26 12:49:02.714 19067-19079/? W/WVCdm: Could not initialize L1. Falling Back to L3.

coolapk? what is it?

Hey, does this ROM's default kernel come with color control? Or could anyone suggest such a kernel? I've tried hellspawn but the performance was abysmal for me.

Ra1d3R said:
coolapk? what is it?
Click to expand...
Click to collapse
Coolapk is not a system application, It is one of my own applications that I use every day.

The last release MK71.2-mako-201708280916-NIGHTLY have the best battery experience ever whit the nexus 4. awesome rom includes xposed, audio fx , lawnchair, and a lot of things. Amazing!

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