Database Info

OTA Updates [ROM][4/13/14] GPE for M8VZW

I recently flashed my HTC One M8 with [ROM][4/13/14] GPE for M8VZW. Curently the rom is a little laggy and the camera is really slow. How will I be able to update the rom? Will it update OTA? Any idea when the lag issues will be fixed?
Thanks

timothyl88 said:
I recently flashed my HTC One M8 with [ROM][4/13/14] GPE for M8VZW. Curently the rom is a little laggy and the camera is really slow. How will I be able to update the rom? Will it update OTA? Any idea when the lag issues will be fixed?
Thanks
Click to expand...
Click to collapse
It's all on the ROM developers... I would suggest you post this question in that ROM's thread for best response. Custom ROMs will not update "OTA" since you have a custom recovery on your phone. You will have to rely on the Devs to provide new ROM versions with the OTA updates "embedded" in them. (Though, I think if there is a Firmware update, you can manually apply it once someone posts a process for doing so on S-Off/Unlocked M8's)

WorldOfJohnboy said:
It's all on the ROM developers... I would suggest you post this question in that ROM's thread for best response. Custom ROMs will not update "OTA" since you have a custom recovery on your phone. You will have to rely on the Devs to provide new ROM versions with the OTA updates "embedded" in them. (Though, I think if there is a Firmware update, you can manually apply it once someone posts a process for doing so on S-Off/Unlocked M8's)
Click to expand...
Click to collapse
I would post but cant since I just created an account. When flashing an update to the rom will it reset all my settings so I have to go through the setup process again?

timothyl88 said:
I would post but cant since I just created an account. When flashing an update to the rom will it reset all my settings so I have to go through the setup process again?
Click to expand...
Click to collapse
you should not have to if youre just flashing a newer version over the same ROM but just an older version, UNLESS the dev says to wipe, in which case you will have to go through setup all over again.

timothyl88 said:
I would post but cant since I just created an account. When flashing an update to the rom will it reset all my settings so I have to go through the setup process again?
Click to expand...
Click to collapse
Ideally, it's always better to do a clean install when you flash any ROM, just to prevent any possible issues from coming up. However, it's not always necessary when you're just flashing an update to a ROM you're already running. Though if the update includes a new version of Android, it's usually highly recommended to do a clean install. And if you're running one ROM and decide to switch to another, a clean install is recommended again, if not absolutely necessary.
I would recommend checking out Titanium Backup or Helium. They're both app backup solutions (if you decide you want to start checking out different ROM's more often, you'll be very happy you have this) that will let you restore your apps and app settings after a clean flash/wipe.

timothyl88 said:
I would post but cant since I just created an account. When flashing an update to the rom will it reset all my settings so I have to go through the setup process again?
Click to expand...
Click to collapse
As Abe and sfreemanoh have already stated, that too is up to the Developer. If you are changing ROMs (Example: Have Stock ROM that's S-Off/Rooted and decide to flash ViperOneM8), you really need to Factory Reset your phone. Titanium, Helium, or MyBackup are three ways to save your Application/System data before your wipe.
If you are merely updating your current ROM version (Example: ViperOneM8 v1.0 to v1.5), the Developer should always post what needs to happen. In many cases, if there are just minor updates, the Devs will say it's OK to "Dirty Flash" without a wipe. Sometimes Devs always tell you to wipe and do a clean install. (ViperOne actually has "OTA" update files, which is basically a smaller update file that you can dirty flash.)

Thanks guys for the answers.

[ROM] Mokee 5.1.1 STABLE (Daily Driver)

First Thing First : I'm not the developer of this ROM. Just Sharing "MY" experience
It's been a long time Mokee builds are available for Mi 4i. I've been using it since 2nd last build (more than 10 days) and currently on latest built i.e. 25th Jan 2016. And I can say that it's Stable.
What's Working :
Everything, except volume rocker keys on earphone.
Highlights:
DT2W
D2TS
Ambient Display
Not even a single FCs or Reboot since installation (more than 10 days now)
CoC is working fine
FB is working fine
More than 24 hours backup (With normal use, NO intensive gaming and ~4 hours SOT)
Installation Instruction (Which I followed, You can go with normal way):
1. Flash MIUI ROM 5.6.11 (I tried to install on 7.1.1, it keep on rebooting. Tried everything, but no luck)
2. Flash TWRP as permanent Recovery
3. Root using SuperSU
4. Wipe everything (but ROM & Gapps Folders)
5. Flash ROM
6. Reboot to System (No need to set-up anything, just do next next)
7. Go to Recovery, Flash Gapps
8. Reboot to system (Again no need to set-up anything, just do next next)
9. Factory Reset (From settings, NOT from recovery)
10. Set-up now
11. Enjoy and All the Best
I know it's painful the way I set-up ROM, but yes I'm not facing any problem at all (Fingers-crossed ). We three colleagues are using it. So it's tested now (you can say)
I've only one phone and I'm using it as a daily driver.
Downloads:
ROM
Gapps : pico version

Enjoy the New ROM guys

this rom is still stuck in LP. was hoping for MM already

ajaxcbcb said:
this rom is still stuck in LP. was hoping for MM already
Click to expand...
Click to collapse
You are very much correct my friend, but again it's a very good alternative for :
1. Those who don't wanna be on MIUI.
2. Struggling to find a CM daily driver.
//TM

good to know. I couldn't take the constant reboot from Remix ROM. Just installed Mokee yesterday. So far so good. Keep my fingers crossed.

getting very high wakelock on *alarms* on any mokee rom

Yeah this is the most stable custom rom for mi4i ...
- official
- update OTA almost every week ..

Can anyone verify if fast dormancy is present in the rom? either through wakelocks or logcat(it should say fast dormancy service or otherwise)

Is ambient display working on this rom?

Hey I am not able to do it. I tried it several times, but every time it says that ERROR IN UPDATER BINARY ZIP.......I am not able to flash it. Help me.

Rajat Naik said:
Is ambient display working on this rom?
Click to expand...
Click to collapse
Yes, Check OP.

xposed support?

lineoxkun said:
xposed support?
Click to expand...
Click to collapse
works, no problem!

imagine92 said:
works, no problem!
Click to expand...
Click to collapse
Nice! Definitely will try this ROM tonight! Thanks OP for sharing [emoji1]
Sent from my MI 4i using Tapatalk

What's your SOT on MIUI 7 with similar type of use?

not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.

sik619 said:
not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.
Click to expand...
Click to collapse
Use twrp 2.8.7
http://forum.xda-developers.com/showthread.php?t=3204594

Is it smooth as any other moto g mobile lolipop version...becoz i always get a feel that miui is laggy..i never install a custom rom before

hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me

sik619 said:
hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me
Click to expand...
Click to collapse
I suggest you to use miui 6.6.10.0 glob stable before flash mokee rom

cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)

Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.

hjrry said:
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
Click to expand...
Click to collapse
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?

Nitefire77 said:
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Click to expand...
Click to collapse
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?

hjrry said:
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
Click to expand...
Click to collapse
Try a different GAPPS package, maybe a larger one. Just to see. For one, some people complained of missing features like notification bar pulldown with the very smallest GAPPS package. Now this isn't a reason it shouldn't install, but try a different package to see if it make a difference in completing the installation.

hjrry said:
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Click to expand...
Click to collapse
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.

plasticdoc said:
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
Click to expand...
Click to collapse
First, restore your backup. You did make a backup, right?
Then re-flash after you download a different GAPPs package. Some say Open Gapps works great for them, while others say Slim GAPPS is best. We don't know why some don't work for some people but work for others.
If that doesn't fix your issue, then try this:
Download the unofficial CM13 found here in this forum and try it.
Also, download Resurrection Remix (Marshmallow) and try it.
Both are variants of CM13 anyways. Just trying to see if something is wrong with your phone and you can't flash any ROM whatsoever or if it's something your phone doesn't like about official CM13.
The unofficial CM13 is CM13 with just a few of the Resurrection Remix tweaks thrown in, like permissions to download Moto apps from the Google Store, etc. It's 90% CM13, 10% RR.
If none of those CM13 variants work, you can alway try AOSP Mokee (Marshmallow).
IF NONE of those work, either your phone is severely messed up or you are doing something wrong.

ChazzMatt said:
Download the unofficial CM13 found here in this forum and try it.
Click to expand...
Click to collapse
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.

plasticdoc said:
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
Click to expand...
Click to collapse
I don't know. Not everything with our phones is completely logical. Occasionally more of an art than science. Same reason one GAPPs package works well for someone but won't install for another person. Open GAPPS vs Slim Gapps.
Here's a personal example... My wife and I both have XT1225 with CM12.1 and yet hers can't run BHB27 kernel. Occasionally I'll get it to install, and run OK for a day or two but then next time I reboot it it does endless bootloops. I even tried different governors and I/O schedulers. Nada.
Mine is a Puerto Rico (unlocked Claro) XT1225 I flashed to India 5.0.2 before flashing to CM.
Her's is a Mexico direct-from-China-Motorola factory XT1225 I flashed to India 5.0.2 before flashing to CM.
Later I flashed Puerto Rico XT1225 radio over both.
There's just some difference there in her XT1225 which does not like BHB27 kernel.
Maybe if I did an exhaustive formatting of the entire internal memory and reinstallation of everything on her phone, it would work. But instead I take the easy way out and she's just running CM12.1 with default CM kernel, and that's running well. So, I go with what works.

phone app not working
unfortunately telephone has stopped working.

wajid1213 said:
unfortunately telephone has stopped working.
Click to expand...
Click to collapse
What does that have to do with this thread? > cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)
I don't even think you are using this phone, to be honest. So, why did you post here? You posted same thing in another thread, for ANOTHER PHONE, not even related to Quark.
You seem to be using this phone: Xiaomi Redmi 2 -- since all your other posts before this and after this are over there.
http://forum.xda-developers.com/search.php?searchid=422491957

MIUI V8.2.4.0.MBEMIDL Global Stable Released

Get it while it's hot :
http://en.miui.com/download-320.html

Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Sent from my Redmi 4 Prime using XDA-Developers Legacy app

I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Flynhx said:
Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Click to expand...
Click to collapse

senseii said:
I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Click to expand...
Click to collapse
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app

Bet this rom weighs more than an average car....

I was using stock 8.2.1 Global Stable. After auto-updating to 8.2.4, had sound glitches, unlock lag and Telegram bugs I've never seen before. I don't recommend to migrate to this version from 8.2.1.

I haven't had any sound glitches or unlock lag (I don't use telegram).
As for battery life it's great, 2 days use, 6 hours SOT so far and I have 50% battery left (4G on all the time).

Flynhx said:
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
Click to expand...
Click to collapse
5th day with the phone. i got it update it to 8.2.4, charged it, unlocked bootloader, installed twrp/root and i had about 10 hours sot during a 3 day period on 2g and a little 3g and wifi disable when screen is off. those 10 hours included a lot of restarts that consume energy a lot of copying things via wifi browsing messenging and a few calls. no problems so far hope i helped.

This update don't bring big changes. Don't understand why you afraid of update. All work's fine including battery life and performances.

Upd:
1. Sound issues and Telegram bugs - no more. One-time glitch?
2. Usual Xiaomi micro-lags when switching apps seem to disappear. So 8.2.4.0 feels way more smooth for me.
3. Battery life - no noticeable changes.
4. MiPicks app added along with annoying ads.

I wonder Why eu version not yet published ?

Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?

BadHappiness said:
Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?
Click to expand...
Click to collapse
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).

sas_sas said:
I wonder Why eu version not yet published ?
Click to expand...
Click to collapse
xiaomi.eu is based on the china rom, not the global. they won't release until there's an official release for the CN rom.

senseii said:
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).
Click to expand...
Click to collapse
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?

BadHappiness said:
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?
Click to expand...
Click to collapse
Yeah you should wipe the cache and davlik cache at least before flashing the new rom. Full wipe would be best.
To get root you'll have to re-flash the super su zip file after you flash the rom.

Re' 8.2.4.0 global
Just did a clean full wipe and flashed epic zip again for another try, though I still have noticeable battery drain.
Thinking of going 8.2.4.(and then uninstalling a few apps n' make a few minor mods for better battery life)
I have twrp installed, read somewhere I can not get rom updates via OTA due to this. (As MIUI recovery is needed for update?) Is that true?
In which case does that mean when there is a new global rom update, and I flash zip in twrp(if that's the case) I would lose my settings and aps? (Guess I would) Or as it's newer/similar global update could I get my settings back from mi cloud or Titanium back up?
Tired of changing roms and then setting up all the apps.
Sorry if this a newbie type question.
Thanks for any info (=

Tried to delete my last post, without luck, found answer/s in other threads (=

The zip file is corrupt

Question Xiaomi 12 cupid no OTA update

Hi,
My Xiaomi 12 still hasn't gotten an new update and is stuck on MIUI 13.0.27.0( SLCEUXM) with security patch of oktober 2022.
I would like to get to the latest miui 14 and would like to know what is the best way to manually update this safely with a original ROM?
Should I do this incrementally start at MIUI 13.2.6.0 and then go to the next till I get to the latest or can I just update to the latest MIUI 14 directly?
Tnx

Gradually is the safest method.
Skipped the Beta stables.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com

Thank you for the quick response.
I downloaded the MIUI downloader app are those ROMS good to?
I need to choose for a recovery ROM and then I can install it with the updater app right? So starting with version MIUI 13.2.6.0 would be the safest?

Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.

NOSS8 said:
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
Click to expand...
Click to collapse
You mean this one right?
It says it's only around 80mb is that correct?
When it's for a update from Android 12 to Android 13.

Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.

NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
So I tried to install the stable recovery ROM MIUI 13.2.6.0.TLCEUXM but it didn't work I keep getting this message "can't verify update can't flash this stable rom"
Then I tried a newer version recovery ROM MIUI 14.0.5.0.TLCEUXM but same message.
Also tried your suggestion to use the incremental update of the current ROM V13.0.27.0 but then I got the message "can't verify update can't downgrade ROM version"
Do you have any other ideas on how to fix this problem?

Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.

NOSS8 said:
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
Click to expand...
Click to collapse
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?

Jappie3 said:
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Click to expand...
Click to collapse
Nope, you can re-lock the bootloader after installing the stock rom.
No need with a Xiaomi Eu rom (certified play store, everything works).

NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?

Jappie3 said:
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Click to expand...
Click to collapse
Nope,only solution unlock the bootloader.

Just to be sure I downloaded the 2 latest versions that I hadn't tried yet.
The recovery ROM of version MIUI 14.0.7.0.TLCEUXM and 14.0.8.0.TLCEUXM.
And they both seem to work
Since I'm still on Android 12 now and missed so many updates in-between these 2 latest versions. Would it be safe to install one of these?

Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).

NOSS8 said:
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
Click to expand...
Click to collapse
So it's not safe to just install one of these recovery versions manually with the updater?

Jappie3 said:
So it's not safe to just install one of these recovery versions manually with the updater?
Click to expand...
Click to collapse
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.

NOSS8 said:
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
Click to expand...
Click to collapse
So it's just a risk of updating no matter what version I use. I never had a boot loop before.

Jappie3 said:
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Click to expand...
Click to collapse
Zero risk does not exist and this risk increases when you force the update by skipping versions.

NOSS8 said:
Zero risk does not exist and this risk increases when you force the update by skipping versions.
Click to expand...
Click to collapse
Oke, yeah I wanted to do it step by step till I got to the latest miui 14 and still don't get why the older versions don't work.
The only older version I could find that also worked was version V13.0.33.0.SLCEUXM but can't find much about that update.

Logical sequence