Related
Can you guys suggest which miui rom i shoukd try? Are there miui roms of both stock and cm9 ? If yes which one to try and is there any brick bug ?
Any help is appreciated
Wait for Rocket ROM MIUI if you want the best possible MIUI for the Note.
Search for Rocket ROM in the Dev section and vote for MINI.
In the mean time install Rocket ROM v10
Sent from my GT-N7000 using xda premium
Whiskeyjack4855 said:
Can you guys suggest which miui rom i shoukd try? Are there miui roms of both stock and cm9 ? If yes which one to try and is there any brick bug ?
Any help is appreciated
Click to expand...
Click to collapse
The brick bug is there with every ROM that has Stock ICS Kernel.Kernels that have MMC_ECAP_ERASE command removed are safe but for some reason MIUI doesn't support these kernels :silly:
CM9 MIUI.Read the OP.Follow the instructions.
Stock MIUI
FabreFaction said:
Wait for Rocket ROM MIUI if you want the best possible MIUI for the Note.
Search for Rocket ROM in the Dev section and vote for MINI.
In the mean time install Rocket ROM v10
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I used rr v 10 but now i am back to cleanote v5...
So is eybee going to make a miui based rom???
warfareonly said:
The brick bug is there with every ROM that has Stock ICS Kernel.Kernels that have MMC_ECAP_ERASE command removed are safe but for some reason MIUI doesn't support these kernels :silly:
CM9 MIUI.Read the OP.Follow the instructions.
Stock MIUI
Click to expand...
Click to collapse
Too many complaints in the thread in both miui roms!
Whiskeyjack4855 said:
Too many complaints in the thread in both miui roms!
Click to expand...
Click to collapse
Though it seems you asked for an opinion on which one to use and it does appears that you did your homework and read up on both the main miui roms available at the moment, imo to say that there are to many complaints regarding them is a little unfair as there isn't a rom forum on here that doesn't in some shape or form have an compliant on whats not working or could be improved that's human nature.
As I really can not comment on the VengeanceNote Edition MIUI 2.8.3- v2.4 + Test builds version due the the fact that I'm not a big fan of cm9 but the rom developer (Gerrett) works very hard on improving it for being a test build (as the title suggest) so yes bugs are to be expected as in any rom. I personally do use the TMT-ver 2 and when properly flashed as per instructions it performs very well. Yes it does have a suspected kernel but being a long time miui user I flash mine from a relatively safe kernel , wipe cache,dalvik, format the system, factory reset then flash the rom and reboot, along with formatting my internal sd card and installing from scratch though it takes me a bit (1 hour or so) and everything works fine and it saves me a few headaches along the way, there are the standard things that miui themselves need to fix like the fc's in the About phone Status and in the Mobile Networks when you want to select Network Operators (these have been known issues since my S2 days) and few people have an issues with the theme manager but for me it does what I want it to. I get decent battery life being a semi-light user never less then a day and a half to 2. But it does vary on what I'm doing..
In the end to ask an opinion for what to use you'll get a variety of each individual who answers your post but what might work well for them may not apply to you and your phone so try what you like if it doesn't suit you then move on to another..
lilbrat said:
VengeanceNote Edition MIUI 2.8.3- v2.4 + Test builds version due the the fact that I'm not a big fan of cm9 but the rom developer (Gerrett) works very hard on improving it for being a test build (as the title suggest) so yes bugs are to be expected as in any rom. I personally do use the TMT-ver 2 and when properly flashed as per instructions it performs very well. Yes it does have a suspected kernel but being a long time miui user I flash mine from a relatively safe kernel , wipe cache,dalvik, format the system, factory reset then flash the rom and reboot, along with formatting my internal sd card and installing from scratch though it takes me a bit (1 hour or so) and everything works fine and it saves me a few headaches along the way, there are the standard things that miui themselves need to fix like the fc's in the About phone Status and in the Mobile Networks when you want to select Network Operators (these have been known issues since my S2 days) and few people have an issues with the theme manager but for me it does what I want it to. I get decent battery life being a semi-light user never less then a day and a half to 2. But it does vary on what I'm doing..
Click to expand...
Click to collapse
Now that's an intelligent reply.. Downloading tmt right now thanks!
Hy everyone! I read in XDA that have many phone dual boot system (dual boot manager)! It is possible to make this solution for Galaxy Mini 2?
Yes, it should be. Since system and data partitions are large enough. But I personally don't think it is useful (at least for me it isn't)
TheWhisp said:
Yes, it should be. Since system and data partitions are large enough. But I personally don't think it is useful (at least for me it isn't)
Click to expand...
Click to collapse
Easy switch from CM to Stock
Because in the CM 10 not work everything (Cam,BT) so not need to restore stock rom or other custom rom in recovery.
djfnz said:
Easy switch from CM to Stock
Because in the CM 10 not work everything (Cam,BT) so not need to restore stock rom or other custom rom in recovery.
Click to expand...
Click to collapse
Good point, really looking forward to something like that..
That would actually be a very useful feature .
Just think about having a fully-packed CM10 build with all the apps and stuff as the main OS , and another pretty much empty stock ROM just for bluetooth and camera . It would be a temporary improvised solution for the problems that are currently in the CM10 build .
However I never did that . Will it really work with such a combo ? Considering we would need different kernels and stuff .
djfnz said:
Hy everyone! I read in XDA that have many phone dual boot system (dual boot manager)! It is possible to make this solution for Galaxy Mini 2?
Click to expand...
Click to collapse
hen how can i o that dual boot
elkhshap said:
hen how can i o that dual boot
Click to expand...
Click to collapse
Not now! It is a idea! Its not developed for Mini 2!
i think galaxy y dev knows this and the other rom can be installed on sdcard(stock rom) while the main rom is in the phone(cm10)..and it requires a modified kernel and a script for the 2nd rom to be booted...like activating it via terminal...
To be honest, before we think about dual booting the device, CM or stock or even with Ubuntu now. The question is this: why would you want a device that can dual boot two operating systems? how will it benefit us the end users to have dual boot on an mid range or an entry level device like SGM2 ? even for a high end device like SGS3 or Sony Xperia Z I don't see how will do anything good for us, for tablets maybe but for smartphones I don't see how can that be something useful. (not that I'm against the idea)
I like the idea, but to be honest, there are more important things we need for our device before we get on dual boot... We don't even have devs.. If TheWhisp ever leave us, we're going to be ****ed up and the development for our device would be pretty much dead... So yah, why would you use dual boot when you don't have 2 good roms to boot up... xD just sayin'...
+1 befor dual boot we need 2 good room thanks god we hawe theWhisp
That go to Galaxy S2, google play are SGS2 Dual-Boot Setup (LolBoot)? https://play.google.com/store/apps/...xMiwibmV0LmhlbGxjYXQuZHJvaWRkZXYubG9sYm9vdCJd
TheWhisp said:
Yes, it should be. Since system and data partitions are large enough. But I personally don't think it is useful (at least for me it isn't)
Click to expand...
Click to collapse
I agree with you. One ROM is enough to be on our device.
Are all Mi3 roms compatible with Mi4?
Sent from my MI 4 using Tapatalk
Yes.. Also, you should probably ask this question in an already existing related thread instead of making another. You'd probably get a quicker answers and the forums will be cleaner
No. I remember installing some very old CAF rom which did not boot in my Mi4w.
The phone been released for 2 months now and yet not even an official TWRP recovery. not a single custom rom too.
i've been looking at Mi 8 forums and it has much better support. at least they have pixel experience rom
do you think it's still early for custom roms to be released or this device really has poor support?
Give it some time. Mi 8 and Mix 3 also took a while before the first ROM came.
SirTAVARES said:
then you have time to learn how to build for us
Click to expand...
Click to collapse
i am sorry i didn't mean to be rude. i am just asking cause i've been waiting so long for a pixel rom and i was kinda concerned. the mi 9 would shine with it.
It took almost 7 months for custom roms to be usable on OnePlus 6
Just chill
I think sm8150 source code just got released not even a week ago, now developers get their first real look and can start working on builds. Really tho, unless the phone you are looking at already has strong developer support don't assume one without it will get it.
Just use GSIs meanwhile? They work very well...
Mohammed779 said:
Just use GSIs meanwhile? They work very well...
Click to expand...
Click to collapse
I think that depends on your individual set up. I use TMobile and have 2 sims, 1 for work and one for personal, granted I've only tried floko but I can't use them both with LTE selected, only manage to get edge working. When switching to LTE, I get constant disconnects every few seconds. Sms only seems to work properly with GSM as well. Might be a TMobile US issue, dual SIM issue or dual SIM on same network. Not real sure.
The Mi9 is out for months. Normal whene coming custom roms this comes in the first month. I think we will not see any custom rom now but Miui is also good with custom launcher. I missing nothing.
The device doesn't have "really poor support", the interest and capable people are and will be there. The problem is just the drop of sources. This was to be expected when you have one of the first devices with a new SD SoC. Threads like this really add to the increasing stupidness on XDA.
Sources are out for weeks.
Hot-Proton said:
Sources are out for weeks.
Click to expand...
Click to collapse
You clearly have no idea what you're talking about. Xiaomi kernel source code has been out indeed.. but go look at CAF
CrazyBeaver2377 said:
The device doesn't have "really poor support", the interest and capable people are and will be there. The problem is just the drop of sources. This was to be expected when you have one of the first devices with a new SD SoC. Threads like this really add to the increasing stupidness on XDA.
Click to expand...
Click to collapse
Thanks for clarifying this for all of us "not so much into all technical details" people. I can understand your frustration, but I think for most people eagerly waiting for something else then MIUI, (who are not willing or knowing where to start with GSI Roms) its good to have one of these threads out there (maybe even pinned on top).
As you are stating it's only a matter of time, and that is good to know for all of us. It would also be great to have some DEVs that are planning on building for the MI 9 in such a thread to even built more confidence.
Just a word from another Dutchmen. Have a good weekend y'all! And try (just as I am about to) not to check XDA MI 9 forum every 6 hours every day. Just wait some weeks. Things are probably about to become very Pixely soon.
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
randomblame said:
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
Click to expand...
Click to collapse
Thanks Kelsi For your hard work.
And don't let these idiots pressure you!
Don't they get you work for FREE and you probably have
a life also Lol.
randomblame said:
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
Click to expand...
Click to collapse
You are making a really good work.
Unfortunately i have not the device so i can't make a good work fast, maybe in another month i will fix recovery
mauronofrio said:
You are making a really good work.
Unfortunately i have not the device so i can't make a good work fast, maybe in another month i will fix recovery
Click to expand...
Click to collapse
Yeah it's good enough for now for my purposes but needs improvement. The big question is how do we make it compatible across different dtbos
randomblame said:
Yeah it's good enough for now for my purposes but needs improvement. The big question is how do we make it compatible across different dtbos
Click to expand...
Click to collapse
Can't you include a dtbo in the rom zip?
Can i ask you if i can use your kernel in my TWRP?
mauronofrio said:
Can't you include a dtbo in the rom zip?
Can i ask you if i can use your kernel in my TWRP?
Click to expand...
Click to collapse
You can use my kernel of course, pstore works with it so it's actually possible to debug init with some effort pressing both volume buttons and ai button sends a soft reset to recovery signal which is the only way to keep the ramoops info in memory. The problem is if you flash a dtbo then the boot.img may be incompatible. Recovery boot and dtbo all have to be matching unless there's a way to make recovery work off the existing kernel in /boot
I cant understand the Problem here. Just Look at phhusson the god of devs for GSIs. The Day He posted on xda that his New Main device is the mi9 was the Day my next device was also the mi9 (just arrived today). His aosp gsi is working on mi9 for weeks with just some realy small Bugs and i think it wont last long until He has fixed all Bugs. And from that Day on we will have every custom Rom thats available as a gsi with their next Update.
https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
https://github.com/phhusson/treble_experimentations/releases
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
I dont like gsi. For flashing need a PC. Gsi is for me not a custom rom. I need a custom rom what i can flash with twrp, without pc.
hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed