Database Info

[ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project

I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?

kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
You must factory reset

Ryuinferno said:
You must factory reset
Click to expand...
Click to collapse
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK

kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
I am not sure as this is device specific... sorry...as long as recovery is compatible it should work

kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.

RCOO said:
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.
Click to expand...
Click to collapse
Thanks a lot @RCOO...... I have flashed back Samuri's Stock KK.... I was worried it had hard bricked....
Will try downgrading and then flash back n see what happens....:fingers-crossed:

whao there
kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
i did something very similiar. from what i understand (which isnt muchLOL). but Dhacker29 told me that once you upgrade you have to use the new kitkat bootloader. and the new bootloader only works with roms that have upgraded kernels 3.5 or higher(i think) so right at this momoent there are next to no roms but you can either use stock and modify it yourself or you can give Dhackers test build which isnt bad it has a few bugs but all the hardware works so far and my RAZR HD is playing games it couldnt touch before at all. here give this a try( oh turn off touch sounds to get rid of that anoying popping/cracking sound) i started this thread after having the same issues LMAO in it u will find links to the test rom . hope this helps
http://forum.xda-developers.com/showthread.php?t=2789490

@JohnnyMcG... I did the downgrade and it worked.... Flashed mokee and it works like a charm.
Sent from my DROID RAZR HD using Tapatalk

[Q] LOLIPOP to KITKAT downgrade help

Hello
had a question on if anything special is needed to go from lolipop and downgrading to kit kat or do i just flash like normal
I though i saw something about needing a special zip file in a thread but i just want to be sure i may be confusing it with the proximity zip or something
Thanks for answers

There's no such thing as a proximity zip. I think what you're referring to is the firmware zip. When going from KitKat to Lollipop you need to flash the Lollipop firmware and the Lollipop modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and the KitKat modem.
KitKat firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFM09OTEZ2NnVfekE/edit?usp=docslist_api
Lollipop firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modems:
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon

timmaaa said:
There's no such thing as a proximity zip. I think what you're referring to is the firmware zip. When going from KitKat to Lollipop you need to flash the Lollipop firmware and the Lollipop modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and the KitKat modem.
KitKat firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFM09OTEZ2NnVfekE/edit?usp=docslist_api
Lollipop firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modems:
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you for this. I was wondering the same thing. I am about to flash LP for the first time in a while so I am glad I ran into this great info!

timmaaa said:
There's no such thing as a proximity zip. I think what you're referring to is the firmware zip. When going from KitKat to Lollipop you need to flash the Lollipop firmware and the Lollipop modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and the KitKat modem.
KitKat firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFM09OTEZ2NnVfekE/edit?usp=docslist_api
Lollipop firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modems:
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
Click to expand...
Click to collapse
Strange, I have never had to flash the modem separately.
What exactly does it do?
I'm now running Lollipop YNG1TAS17L. I updated from KitKat to Lollipop via an OTA link using TWRP recovery. Should I still flash this Lollipop modem?

danielsinnema said:
Strange, I have never had to flash the modem separately.
What exactly does it do?
I'm now running Lollipop YNG1TAS17L. I updated from KitKat to Lollipop via an OTA link using TWRP recovery. Should I still flash this Lollipop modem?
Click to expand...
Click to collapse
No
The OTA did it for you automatically
Please do not flash any modem on it unless you are facing issues with your radio(network connectivity)

Mr hOaX said:
No
The OTA did it for you automatically
Please do not flash any modem on it unless you are facing issues with your radio(network connectivity)
Click to expand...
Click to collapse
Got it, thanks. ?

Heisenberg said:
There's no such thing as a proximity zip. I think what you're referring to is the firmware zip. When going from KitKat to Lollipop you need to flash the Lollipop firmware and the Lollipop modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and the KitKat modem.
KitKat firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFM09OTEZ2NnVfekE/edit?usp=docslist_api
Lollipop firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modems:
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
Click to expand...
Click to collapse
@Heisenberg
I just tried what u suggested, but it didn't work. I am on CM12s and I want to try PA 4.6 Beta 6. So I downloaded kitkat firmware and two modems too ( the two kitakat modems with 'Full' prefix. I went to recovery, flashed the firmware, then tried to flash the PA ROM. It showed an error, like "can't go back to old version Nov from new version May". It also showed error in update binary script. Then I flashed the modem and firmware, and tried to flash PA again, but it didn't work. Please, help me. I wanna go to PA kitkat.

deepaklunked said:
@Heisenberg
I just tried what u suggested, but it didn't work. I am on CM12s and I want to try PA 4.6 Beta 6. So I downloaded kitkat firmware and two modems too ( the two kitakat modems with 'Full' prefix. I went to recovery, flashed the firmware, then tried to flash the PA ROM. It showed an error, like "can't go back to old version Nov from new version May". It also showed error in update binary script. Then I flashed the modem and firmware, and tried to flash PA again, but it didn't work. Please, help me. I wanna go to PA kitkat.
Click to expand...
Click to collapse
What error did you get when flashing the ROM?

@Heisenberg
See the pic attached. It goes like:
"Can't install this package (Mon Nov 3 .....) over newer build (Mon May 25 .....)
E:Error executing updater binary in zip '/sdcard/MODs/Downloads/pa_bacon-4.6-BETA6-20141103.zip'
Error flashing zip .........
Edit: I just flashed cm11 firmware before flashing pa zip. I can see that in the image. And sorry for the poor pic quality. Taken from my dad'a Desire 310
Sent from my HTC Desire 310 dual sim using XDA Free mobile app

deepaklunked said:
@Heisenberg
See the pic attached. It goes like:
"Can't install this package (Mon Nov 3 .....) over newer build (Mon May 25 .....)
E:Error executing updater binary in zip '/sdcard/MODs/Downloads/pa_bacon-4.6-BETA6-20141103.zip'
Error flashing zip .........
Edit: I just flashed cm11 firmware before flashing pa zip. I can see that in the image. And sorry for the poor pic quality. Taken from my dad'a Desire 310
Sent from my HTC Desire 310 dual sim using XDA Free mobile app
Click to expand...
Click to collapse
Alright, first things first. I can see you're asking the same question in the PA thread, please don't double-post, only discuss an issue in one place at a time.
Is that a themed version of TWRP you're running? And did you wipe properly before flashing? The error you're getting suggests to me that you're not wiping properly.

I did a full wipe: wiped system, dalvik, data, and cache. And sorry for double-posting. Was li'l impatient.
---------- Post added at 03:23 PM ---------- Previous post was at 03:23 PM ----------
And yes, it is themed version of twrp, 2.8.6.1

deepaklunked said:
I did a full wipe: wiped system, dalvik, data, and cache. And sorry for double-posting. Was li'l impatient.
---------- Post added at 03:23 PM ---------- Previous post was at 03:23 PM ----------
And yes, it is themed version of twrp, 2.8.6.1
Click to expand...
Click to collapse
I'm unsure why it isn't working for you then unfortunately. I can only guess that the wipe isn't working properly because the installer is still able to detect the previous ROM. It might be worth flashing the stock TWRP instead of the themed version as that might be causing the problem.

Okay. Will try the same procedure with stock trwp.
Edit: @Heisenberg[/MENTION] The same error with stock twrp. Have a look.

Sent from my HTC Desire 310 dual sim using XDA Free mobile app

deepaklunked said:
Sent from my HTC Desire 310 dual sim using XDA Free mobile app
Click to expand...
Click to collapse
I can't see the text in that image. I'm not sure mate, does the same problem happen with other ROMs?

Woohoo! I finally did it. @Heisenberg PA 4.6 Beta 6 flashed successfully. What I did was just RESEARCH. As you said that the error has got something to do with TWRP, I searched for CWM. I then went into Philz Recovery thread. Just scrolled down for download links. Read this somewhere, "To flash older files, use recovery version 6.02.2- . Then I got the link to download CMW touch recovery version 6.0.5.0. And then the magic began. Wiped everything, installed cm11 firmware, and then installed PA. And now I am running PA. Anyways, thanks for giving the hint about TWRP.

deepaklunked said:
Woohoo! I finally did it. @Heisenberg PA 4.6 Beta 6 flashed successfully. What I did was just RESEARCH. As you said that the error has got something to do with TWRP, I searched for CWM. I then went into Philz Recovery thread. Just scrolled down for download links. Read this somewhere, "To flash older files, use recovery version 6.02.2- . Then I got the link to download CMW touch recovery version 6.0.5.0. And then the magic began. Wiped everything, installed cm11 firmware, and then installed PA. And now I am running PA. Anyways, thanks for giving the hint about TWRP.
Click to expand...
Click to collapse
Cool man, good to see you worked it out.

Thanks. I just want this information to be available to all those who want to downgrade. Could you just update the OP.

Heisenberg said:
There's no such thing as a proximity zip. I think what you're referring to is the firmware zip. When going from KitKat to Lollipop you need to flash the Lollipop firmware and the Lollipop modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and the KitKat modem.
KitKat firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFM09OTEZ2NnVfekE/edit?usp=docslist_api
Lollipop firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modems:
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
Click to expand...
Click to collapse
I'm reverting back to KK.
I've installed the firmware you provided, and the Full-YNG1TAS0YL-modem-flashable.zip modem. Then I've installed slimsaber (4.4.4) and Zane's boeffla kernel from here http://boeffla.df-kunde.de/zanezam/linaro/bacon/cm11.0/stable/
The proximity sensor is broken, any fix my friend?

just4u32 said:
I'm reverting back to KK.
I've installed the firmware you provided, and the Full-YNG1TAS0YL-modem-flashable.zip modem. Then I've installed slimsaber (4.4.4) and Zane's boeffla kernel from here http://boeffla.df-kunde.de/zanezam/linaro/bacon/cm11.0/stable/
The proximity sensor is broken, any fix my friend?
Click to expand...
Click to collapse
Probably because you flashed a Lollipop modem on a kitkat rom?

[Q] Probably a dumb question but..

If I want to flash a custom ROM that works with android 5.0.2 will this custom ROM also install 5.0.2 or do I first have to flash 5.0.2 and then flash the custom rom?
thanks.

runittwiice said:
If I want to flash a custom ROM that works with android 5.0.2 will this custom ROM also install 5.0.2 or do I first have to flash 5.0.2 and then flash the custom rom?
thanks.
Click to expand...
Click to collapse
If you flash a custom ROM, let's say 5.0.2, it will have been built from 5.0.2 source code. Therefore it is 5.0.2, although modified to some degree. Each custom ROM generally has instructions on what to do before flashing it, which is usually just wiping system, data, dalvik and cache partitions in recovery.

runittwiice said:
If I want to flash a custom ROM that works with android 5.0.2 will this custom ROM also install 5.0.2 or do I first have to flash 5.0.2 and then flash the custom rom?
thanks.
Click to expand...
Click to collapse
the custom rom is the firmware youre flashing..
i recommend you to flash this rom (stock) optimized version , as it has better battery backup and so for the moto g
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

skinnyj said:
the custom rom is the firmware youre flashing..
i recommend you to flash this rom (stock) optimized version , as it has better battery backup and so for the moto g
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
Ok, so it doesn't really matter if I'm running KK right now, If I flash a custom 5.0.2 it will also put my phone on 5.0.2?
Sorry I know quite a few things, but I know almost nothing at all about all this stuff.

runittwiice said:
Ok, so it doesn't really matter if I'm running KK right now, If I flash a custom 5.0.2 it will also put my phone on 5.0.2?
Sorry I know quite a few things, but I know almost nothing at all about all this stuff.
Click to expand...
Click to collapse
No, only if youre in GPE there is an additional step to be done , or else youre good to go..
i quoted the answer for your question from the thread -
Do I need to downgrade to 4.4.4 before flashing these ROMs?
No. However an additional step is required if you are currently running a GPE ROM; see next question.
Can I flash this ROM if I'm GPE?
Stock Motorola ROMs require a F2FS 'userdata' partition. If you are GPE, or have ever been; you may need to convert to Stock. More info in FAQ here.
:good:

[Q] Can't boot custom rom after flashing in TWRP

I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?

Gevork Gevorkyan said:
I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?
Click to expand...
Click to collapse
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4

BladeRunner said:
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4
Click to expand...
Click to collapse
Thanks for the link that thread and your advice was exactly what I needed.
For whatever reason after using the app/exe to flash 5.0.1 stock-rooted, Liquid Rom failed to install in TWRP. I reflashed the stock-rooted rom and CM-12.1 worked flawlessly. So I'm on CM right now :good: but I'll take another look into Liquid rom. Thanks so much!

Since you like AOSP, I recommend visiting the main m8 thread some other Roms. They are unified builds.

Bootloop: LG G2 D801 after TWRP install

Ok, so I just started to dig into my g2 today and decided to root it and such with hopes of trying out the resurrection remix rom. I followed this http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951 to root my stock D801 running 4.4.2 and it worked perfectly fine verified with the root checker app. I went on to install TWRP following this http://forum.xda-developers.com/tmo...l-one-click-freedom-tool-lp-30b-twrp-t3084474 which also worked fine so i booted into TWRP. First and only thing i did was create a backup. After the backup was done i rebooted and now I'm stuck with a repeating lg logo boot loop. I can still get into TWRP, and I can get into download mode so I'm not too worried. I tried restoring from the backup I made right before the bootloop started but it didn't work.
My question is what did I do wrong? Also, instead of going back to stock, could I just load resurrection remix onto the phone now and try to flash it even though its boot looping?

ravensfan8448 said:
Ok, so I just started to dig into my g2 today and decided to root it and such with hopes of trying out the resurrection remix rom. I followed this http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951 to root my stock D801 running 4.4.2 and it worked perfectly fine verified with the root checker app. I went on to install TWRP following this http://forum.xda-developers.com/tmo...l-one-click-freedom-tool-lp-30b-twrp-t3084474 which also worked fine so i booted into TWRP. First and only thing i did was create a backup. After the backup was done i rebooted and now I'm stuck with a repeating lg logo boot loop. I can still get into TWRP, and I can get into download mode so I'm not too worried. I tried restoring from the backup I made right before the bootloop started but it didn't work.
My question is what did I do wrong? Also, instead of going back to stock, could I just load resurrection remix onto the phone now and try to flash it even though its boot looping?
Click to expand...
Click to collapse
Did you actually ever upgrade to lollipop?
If not try flashing the 20g bootstack that can be found in the stock 30b roms by micromod...after that you should be able to restore your backup...

jamesd1085 said:
Did you actually ever upgrade to lollipop?
If not try flashing the 20g bootstack that can be found in the stock 30b roms by micromod...after that you should be able to restore your backup...
Click to expand...
Click to collapse
I did not. I was running on 4.4.2. I have since used the lg 2014 flash tool to flash the stock lollipop firmware, and subsequently followed the same process i mentioned above to root and get twrp installed. Now I have everything running alright, and a stable backup, but im running into issues flashing resurrection remix. I tried both the latest version on 5.1, and the newest version for 5.0.2. I first do a factory rest wipe on twrp, then i flash resurrection and the appropriate gapps ( 5.0 for the 5.02 rom and 5.1 for the newest one) both times i just get the lg logo after reboot. the logo stays for about 2 minutes until the screen starts to flicker and fade to grey. then i have to go back to twrp and restore.

ravensfan8448 said:
I did not. I was running on 4.4.2. I have since used the lg 2014 flash tool to flash the stock lollipop firmware, and subsequently followed the same process i mentioned above to root and get twrp installed. Now I have everything running alright, and a stable backup, but im running into issues flashing resurrection remix. I tried both the latest version on 5.1, and the newest version for 5.0.2. I first do a factory rest wipe on twrp, then i flash resurrection and the appropriate gapps ( 5.0 for the 5.02 rom and 5.1 for the newest one) both times i just get the lg logo after reboot. the logo stays for about 2 minutes until the screen starts to flicker and fade to grey. then i have to go back to twrp and restore.
Click to expand...
Click to collapse
RR is kit kat based and you will need to flash the 20g bootstack i mentioned and also the jb bootloader by blastagator...then you will be able to flash RR...to return to lollipop you will need to flash the 30b bootstack before restoring...30 bootstack can be found in same thread as the 20g...good luck

jamesd1085 said:
RR is kit kat based and you will need to flash the 20g bootstack i mentioned and also the jb bootloader by blastagator...then you will be able to flash RR...to return to lollipop you will need to flash the 30b bootstack before restoring...30 bootstack can be found in same thread as the 20g...good luck
Click to expand...
Click to collapse
Thanks! I'm not really sure what a bootstack is, so i guess i have a bit to learn, i will go and look up the 20g bootstack and see whats involved with it.

ravensfan8448 said:
Thanks! I'm not really sure what a bootstack is, so i guess i have a bit to learn, i will go and look up the 20g bootstack and see whats involved with it.
Click to expand...
Click to collapse
Both files can be found here http://forum.xda-developers.com/tmo...-tmo-g2-lollipop-30b-stock-rom-t3084687...for 30b bootstack though grab the one i linked in post 13 as the one in op breaks download mode so i fixed it in linked one the 20g one is fine i believe

jamesd1085 said:
Both files can be found here http://forum.xda-developers.com/tmo...-tmo-g2-lollipop-30b-stock-rom-t3084687...for 30b bootstack though grab the one i linked in post 13 as the one in op breaks download mode so i fixed it in linked one the 20g one is fine i believe
Click to expand...
Click to collapse
I wish I could hit the thanks button more than once, you are awesome. Everything is up and running smoothly now. I don't think I would have ever figured out that a lollipop rom needed a kit kat bootstack and a jellybean bootloader to run properly. I don't even know how I'd go about finding that out. Thanks again.

ravensfan8448 said:
I wish I could hit the thanks button more than once, you are awesome. Everything is up and running smoothly now. I don't think I would have ever figured out that a lollipop rom needed a kit kat bootstack and a jellybean bootloader to run properly. I don't even know how I'd go about finding that out. Thanks again.
Click to expand...
Click to collapse
No problem...by the way is download mode working after flashing 20g bootstack?...if not let me know as i made a modified version to fix but i haven't tested it yet...should work

maybe your problem is fixed by now, but did you try wiping cache/dalvik cache? That fixes 90% of bootloop problems for me.