Related
Hi I'm currently running the s9 port oreo rom beta 1 still
It's a bit buggy and a few bits and pieces that annoy me on it
Can I flash a custom nougat rom over it without having to wipe?
I really really cannot be bothered installing all my apps and everything again and signing in again
I'm not rooted also
I do have TWRP installed tho
jacksskinz said:
Hi I'm currently running the s9 port oreo rom beta 1 still
It's a bit buggy and a few bits and pieces that annoy me on it
Can I flash a custom nougat rom over it without having to wipe?
I really really cannot be bothered installing all my apps and everything again and signing in again
I'm not rooted also
I do have TWRP installed tho
Click to expand...
Click to collapse
no, you need to full restore with odin to go from 8 to 7, bootloader etc needs flashed, use smart switch to backup to sd card and restore back when done
Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!
I posted this in the Q&A thread but it looks pretty dead, I can delete that if needed but hoping to get some help on this one.
I had an Android 10 update this morning, and ever since the person on the other end cannot hear me at all. No way to fix, reset etc.
I don't think I can roll back right? My only solution might be to unlock BL and flash custom, because I cannot wait for a patch to fix this.
Anyone have this same issues? Is there an alternative to going custom? If I do go custom what is the closest to stock that actually fixes this?
This sounds like the problem I have been having since December with still no permanent fix. A temporary fix is to turn on the loudspeaker and then back off and the other caller can hear you. Seems the bug will never get fixed after waiting 3 months now for a fix now.
I decided to use a custom Rom (Ion OS is what I'm using, but any AOSP Rom will do), which fixes the issue altogether. Or you could downgrade back to MIUI 10, which I can confirm it also fixes the call audio issue. So, yes you'll need to unlock the bootloader. I tried other MIUI Roms like Mi-globe, Xiaomi.EU, and ROS-MIUI, and all give the same issue. Well, the ones that's base on android 10 give the call audio issue, the ones based on android 9 don't.
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
Hello orangekid, am on the same situation as you was. The 2 mic Works flawlessly when i rec a vidéo or audio memo but when its on call other hear me with buzing and muffling sound.
I am on custom rom Android 11 (EvolutionX 5.3).
Can u plese give me a link to the modem that you flashed in order to ride off this issue.
Thanks in advence
Sld_Ultra said:
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
Click to expand...
Click to collapse
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Sindalf said:
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Click to expand...
Click to collapse
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Thanks for
Sld_Ultra said:
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Click to expand...
Click to collapse
Thanks for the reply, i was with official MIUI 12 globale version , now i am using évolution x 5.3, i have also replaced my screen and only some twrp Works.. the issue it not related to hardware because when i rec a vidéo or audio memo its Works normally, but when calling the sound is muffled and buzing.. i will try to get back to an android 9 rom ? I will try and will see
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Ezio553 said:
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Click to expand...
Click to collapse
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Robbo.5000 said:
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Click to expand...
Click to collapse
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Ezio553 said:
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Click to expand...
Click to collapse
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Robbo.5000 said:
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Click to expand...
Click to collapse
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Ezio553 said:
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Click to expand...
Click to collapse
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Robbo.5000 said:
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Click to expand...
Click to collapse
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Ezio553 said:
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Click to expand...
Click to collapse
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Robbo.5000 said:
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Click to expand...
Click to collapse
Thanks for the info.
I tried custom miui rom and well flashing dfe worked fine so i think its just for official miui.
Hi!
Recently updated my Moto G9 Plus to A11, but is laggy and buggy as hell in matter of emulation, when A10 doesn't have this problems. So I intented to downgrade to A10 but at the flashing moment (fastboot with stock rom A10) fails at some point (vbmeta). It boots anyway, but breaks NFC module, so can't use it until upgrade to A11 again.
Cause of this, tried some custom roms like Lineage that I found in Telegram room. Didn't realize that i've installed an A12 rom, that I do not knew how to add Gapps. So, when tried the A11 one, the recovery doesn't allow me to install it because of the Anti-RollBack function. Then I give up and tried to go back to A10 stock, and had a bootloop as a result. Then flashing A11 solve the problem, so I have to stay in that f***ing OS...
I'm kind of new in this, besides i've done some things like this before, but I do not have any clue on how to procede... Really want to switch to A10 or A11 custom like Lineage, but don't know how... Any help you can give me?
PD: Sorry, I'm Argentinian, gave the best of me to make this understable