Related
I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?
Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.
Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?
I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?
BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.
When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??
BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.
I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.
Hello all! Long time lurker and user of LOS 14.1 on my osprey. COM13 before that. I'm not a tech wizard like most of you, but I'd say I'm fairly good at navigating this stuff. Hope someone out there can help me out with MMS issues.
I'm on 14.1-20190220-Nightly with squid's kernel and my service provider is T-mobile. I can't pinpoint exactly when but at some point in the last month, I stopped receiving MMS messages. I can send them, but when I try to receive, I get the "check your APN settings" message. APN settings have not changed and I have confirmed they are correct. I've wiped the cache partition and that did nothing. I don't know what else to try.
A possible related issue: sometimes SMS doesn't come through either until I turn off WiFi, or reboot. This is a difficult thing to reproduce, it seems intermittent.
Any direction or advice would be greatly appreciated! Thanks!
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
R1ffR4ff said:
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
Click to expand...
Click to collapse
How long ago did you install 16.1? Any issues at all with it? I might just go that route
I recently did the Network Settings Refresh to try and solve an issue with constant dropped Bluetooth connections. But I will give it another try! Thanks!
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
R1ffR4ff said:
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
Click to expand...
Click to collapse
Interesting. Have you tested MMS and Bluetooth? If those are working, I might just do this.
Thanks for the tips, I keep full nandroid backups too, just in case. I hadn't heard about performing the factory resets during the process but I will do that this time. Is the sequence: factory reset, then boot the ROM, then reboot back into TWRP, then wipe and flash as normal, then boot into new ROM, then reboot into TWRP, factory reset, then finally boot the ROM and setup as normal?
It seems strange that droidthunder instructs you to copy the zip file to internal memory, then wipe the internal memory and then try to flash the zip. Doesn't seem like that would work. Why not just copy the zip to the SD card and flash from there?
Cheers!
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
R1ffR4ff said:
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
Click to expand...
Click to collapse
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
emanresutseb said:
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
Click to expand...
Click to collapse
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
R1ffR4ff said:
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
Click to expand...
Click to collapse
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
emanresutseb said:
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
Click to expand...
Click to collapse
You don't need Titanium as TWRP Nandroid backup saves everything on the internal memory and everything else I want to keep is on the cloud or copied via USB to my PC/Latop.
As for Greenify those kind of apps are useless.You don't need battery savers in Android and even less since Marshamallow.PIE has awesome Battery management and even learns your usage.
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
emanresutseb said:
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
Click to expand...
Click to collapse
Glad you found something that works
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
emanresutseb said:
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
Click to expand...
Click to collapse
I feel the same about the PIE rom on my G3.It makes the old phone feel like a Brand new one :laugh:
I know we don't have a complete implementation of recoveries, like twrp/of (I know it's basically the same), yet. But now that we have the kernel source, what is still missing (vendor?)?
Also and kinda of a similar question, what is still missing regarding a "normal" flashing process? Like wipe system, data, dalvik/art, cache, flash rom and not having to have a base stock firmware and needing to format data.
To be honest, I'm a bit confused with this phone. My other phones (admittedly last one's didn't get past Android 9), were so different in that regard.
So I'd really appreciate if someone could take the time to shed some light on this.
Maybe we'll see a stable version of twrp for surya but support for dynamic partitions will not be available soon.
Having to format data everytime you flash a new rom may be solved having the kernel source. I think it has to do with encryption keys. Even if you don't have any password set in the OS, miui still generates keys to encrypt the data and when you wipe only, they get deleted hence, data on the internal nemeory remains encrypted. That's what I think.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Ok, to be honest and judging by the fact that the announcement by Dees_Troy was over a year ago, things look pretty difficult to say the least.
I had my last phone (axon7) for so long that all the new implementations, like dynamic linking and super partition, weren't really on my radar.
Guess I was a little naive in thinking that the kernel source would be of any help in that regard.
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
pnin said:
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
Click to expand...
Click to collapse
How about EU ROM ?
Thanks for your thread.
I'm asking too.
I went from an old device too (redmi note 4 mido), and i'm a bit lost on flashing process.
Is it possible to :
Install orangefox via fastboot.
Wipe all & format data.
Flash recommend firmware for rom.
Flash custom rom.
Flash gapps.
And boot ?
Any problem with that ? What i'm missing ?
Don't have phone now, I'm waiting for shipping, and will wait for unlock bootloader access. I hope it will more clear and simple when I will discover poco x3.
You can do all those things. What you can't do for example is make a backup and restore your current custom rom.
Oh ok.
Sorry, miss understood your op post.
I was confused because on some custom roms thread, I find strange install instructions, like : dont wipe anything, format data AFTER flash custom roms...
Somes roms requires frimware 12.0.3. What about if phone have a more recent ? Can I downgrade just by flash fw+vendor on recovery before flash rom ?
And some people said they have bricked there devices.
Just to be sure to don't make stupid error on fresh new device, that I can't solve with miflash and fastboot.
Thank you for your reply.
I only clean flash roms, never backup, don't have a lot of apps, and majority have import/export options in-app.
But I hope for you it will be fixed soon.
atifnr said:
How about EU ROM ?
Click to expand...
Click to collapse
As @[armitage] pointed, it doesn't enable nandroid backups that I know of.
.
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
First of all. I have a Poco X3 Pro with 8GB RAM and 256GB Storage. MIUI is v12.5.2.0 (RJUEUXM). Model says M2102J20SG. I Have bought my phone 8 months ago and yesterday I decided to unlock it, mistakenly thinking that would let me disable the Xiaomi apps I do not like.
TL; DR:
1) Can I root my phone with stock rom?
2) Can I disable Xiaomi apps on stock rom if I root it?
3) Any suggestions for me with priority on stability over performance?
I have not been involved in rooting a phone in many years. The last android phone I had and rooted was a ZTE Blade and I mean the first Blade, which was like over a decade ago. After that I did a mistake to go on iPhone and then on an LG G6, that never made me feel like I needed to root it honestly.
The main reason I want to root my phone is to debloat it safely, removing/freezing/disabling quite a lot of Xiaomi's extra software, that I just do not want on my phone. MIUI seems quite enjoyable to me, although I have to admit, due to how I am worried that updating it will make my phone more sluggy and will affect battery life, I have yet to ever update it, still being on version 12.5.2.0.
I honestly would not mind to use a custom rom, but my preference is always stability over performance, except if that would offer me extra battery life and the current MIUI's battery life is beyond excellent in my experience, but maybe because LG G6's battery life was never that good since the day I bought it. I am definitely open to suggestions, about the course of action you people think I should take.
You can use adb commands to disable apps, but speaking from experience, you can only disable so much before things start to break, and some of the most annoying things (to me) cannot be disabled without breaking something. Also, when you update the system, all disabled things will most likely re-enable and you have to do the whole process all over again.
If you like MIUI, uninstall apps that can be uninstalled normally and use it as it is, or (and I highly recommend it) install custom ROM. If you want stability, ArrowOS or Crdroid is what you should take a look at. ArrowOS comes with gapps, while Crdroid offers tons of customization and comes as Vanilla (you can flash gapps seperately, if you want).
You sure can root your phone with stock Miui. However, you need to unlock the bootloader, first. It implies loosing all your current data. After that is done, I see no point in running stock miui, I'd go for xiaomi.eu's stable or any of the AOSP roms currently available.
I'm currently running latest crDRoid, which I'm quite enjoying. It's based of LineageOS with added tweaks and is shipped without gapps - you must installed after flashing the ROM.
Make sure you understand the process:
1. Unlock bootloader - you must wait for the 7 days to do so.
2. Flash a recovery. I suggest looking for a beta of a recovery that supports Android 12 decryption, try Nebrassy's TWRP
3. Flash your preferred ROM
4. Root it with Magisk+useful modules: safetynetfix, gms doze, etc.
Enjoy.
- Regards,
Popletenec said:
You can use adb commands to disable apps, but speaking from experience, you can only disable so much before things start to break, and some of the most annoying things (to me) cannot be disabled without breaking something. Also, when you update the system, all disabled things will most likely re-enable and you have to do the whole process all over again.
If you like MIUI, uninstall apps that can be uninstalled normally and use it as it is, or (and I highly recommend it) install custom ROM. If you want stability, ArrowOS or Crdroid is what you should take a look at. ArrowOS comes with gapps, while Crdroid offers tons of customization and comes as Vanilla (you can flash gapps seperately, if you want).
Click to expand...
Click to collapse
No, adb commands is something I definitely do not want to do. I want the system to allow me to actually disable something, without any sort of "brute forcing", mostly cause like you mentioned, I am worried of breaking things. I do not per se dislike google apps, but honestly if I can have as less as possible, it would be better for me. I will look into both the custom roms you mentioned, thank you =)
aurocha said:
You sure can root your phone with stock Miui. However, you need to unlock the bootloader, first. It implies loosing all your current data. After that is done, I see no point in running stock miui, I'd go for xiaomi.eu's stable or any of the AOSP roms currently available.
I'm currently running latest crDRoid, which I'm quite enjoying. It's based of LineageOS with added tweaks and is shipped without gapps - you must installed after flashing the ROM.
Make sure you understand the process:
1. Unlock bootloader - you must wait for the 7 days to do so.
2. Flash a recovery. I suggest looking for a beta of a recovery that supports Android 12 decryption, try Nebrassy's TWRP
3. Flash your preferred ROM
4. Root it with Magisk+useful modules: safetynetfix, gms doze, etc.
Enjoy.
- Regards,
Click to expand...
Click to collapse
I unlocked the bootloader just yesterday, so I am done with the first part. I will definitely be checking crDroid, since it seems I can't get rid of MIUI what annoys me the most, which is it's bloatware. I guess since you guys mention to try a custom rom, I should give it a try at least, since i went ahead and unlocked the bootloader anyway. Thank you for the suggestion!
Popletenec said:
Also, when you update the system, all disabled things will most likely re-enable and you have to do the whole process all over again.
Click to expand...
Click to collapse
If you uninstall them via ADB on the active user profile they will stay uninstalled even after an update. I did so with 12.5.5 and upgraded to 13.0.1 a while back and they stayed uninstalled.
weltall2 said:
No, adb commands is something I definitely do not want to do. I want the system to allow me to actually disable something, without any sort of "brute forcing", mostly cause like you mentioned, I am worried of breaking things. I do not per se dislike google apps, but honestly if I can have as less as possible, it would be better for me. I will look into both the custom roms you mentioned, thank you =)
I unlocked the bootloader just yesterday, so I am done with the first part. I will definitely be checking crDroid, since it seems I can't get rid of MIUI what annoys me the most, which is it's bloatware. I guess since you guys mention to try a custom rom, I should give it a try at least, since i went ahead and unlocked the bootloader anyway. Thank you for the suggestion!
Click to expand...
Click to collapse
You could also try XiaomiEU rom, which is basically what you want: debloated MIUI. But to have true control over the apps and features you want, rom like Crdroid is the way to go.
Oh I have seen Xiaomi EU mentioned a lot, but I kept thinking it was just the European stock roms. I just looked it up thanks to you and it indeed looks exactly like what I was asking for. I wanted to stay on MIUI cause I really worry that if it is not vanilla, it might cause problems and most importantly battery life ones.
I probably will be trying to go for crDroid, but for now I am worried I might make a mistake. I would hate it if I ended up bricking my phone, since I love Poco X3 Pro.
weltall2 said:
Oh I have seen Xiaomi EU mentioned a lot, but I kept thinking it was just the European stock roms. I just looked it up thanks to you and it indeed looks exactly like what I was asking for. I wanted to stay on MIUI cause I really worry that if it is not vanilla, it might cause problems and most importantly battery life ones.
I probably will be trying to go for crDroid, but for now I am worried I might make a mistake. I would hate it if I ended up bricking my phone, since I love Poco X3 Pro.
Click to expand...
Click to collapse
Don't worry, you won't brick your phone if you just follow instructions, even then, you would have to do some crazy **** to hard brick your phone, most likely you will just end up with bootloop, which is always fixable by just reflashing the rom.
Read carefully and everything will be fine. I am on ArrowOS since I got the phone, updating regularly, rooting, using magisk modules, zero problems so far. Most of the time, battery life is better since useless bloat won't drain it so much.
Purely for battery life reasons I would personally never suggest switching to a custom rom from MIUI, because with a few ADB commands you can get rid of most of the "useless" bloat. However, if you are concerned about your privacy and don't want to feed Xiaomi with your data, then Lineage would be a good choice as an alternative OS, since at least the official versions are heavily regulated.
The battery life of a debloated MIUI is fantastic, at least in my case.
Ok, this will probably be a bit of a dumb and final question before I jump into the whole custom rome in the next days when I have time. I have seen a lot of times people mentioning TWRP or in general recovery that should be android 12 compatible, rather than the normal v11 provided in the twrp site. crDroid even seems to offer it's own recovery for it's latest android 12.1 version. I am still on Android 11 (MIUI 12.5.2.0). Does that mean I need to first update my phone to the latest MIUI to upgrade my software to android 12, or the recovery is backwards compatible?
I would definitely update to latest stock rom, then flash recovery and install ROM.
Hi!! I'm on the same situation here, coming from a Poco 1 (which is being really hard to let go) to a Poco x3 Pro so this thread is being really useful to me cause I'm basically on the same dilemma, stock vs custom?
I always used custom but when I bought my Poco 1 there was an automated script that unbloated the phone so I did that and stayed with the stock with no issues at all in this 3 years of use.
Now, for the poco x3, the only way of doing the same is by going app by app and removing it through ADB which, as you mentioned, is not that good if you are not sure what to remove so that made me think of going to a custom rom. I mean, I just installed it and all that xiaomi junk is removed.
What I didn't know is that the EU version was debloated so that could be a good option for me but, here's my questionk besides de bloated apps, which is the diference between EU and Global roms? Are they target for the same version of the phone or I could have like NFC disable or radio issues? Cause I though there were different version of the stock roms cause the hardware was diferent between devices.
Popletenec said:
I would definitely update to latest stock rom, then flash recovery and install ROM.
Click to expand...
Click to collapse
Ok, first I am going to let the updater do it's job finally and then the rest. Thanks for sharing your thoughts.
zorak20 said:
What I didn't know is that the EU version was debloated so that could be a good option for me but, here's my questionk besides de bloated apps, which is the diference between EU and Global roms? Are they target for the same version of the phone or I could have like NFC disable or radio issues? Cause I though there were different version of the stock roms cause the hardware was diferent between devices.
Click to expand...
Click to collapse
Just to point out, Xiaomi EU is in a way a custom rom. The Xiaomi.EU community taken the Chinese rom, that has less bloat and more features, translating it and sharing it to people. Just because it it called debloated, that does not mean it does not come with the same Xiaomi Apps. It is still MIUI and that means some Xiaomi apps will still be impossible to disable and also apps like the Xiaomi Security that will softbrick your phone if disabled, still is needed and will cause the same thing in the Xiaomi.EU rom.
It is the main reason I am thinking of trying crDroid, or else like you said, I would not mind just a debloated stock rom, since afar from all the needed Xiaomi apps, MIUI seems quite enjoyable to me. If you check their forums though, you will see even the Xiaomi.EU has it's own problems.
weltall2 said:
Ok, first I am going to let the updater do it's job finally and then the rest. Thanks for sharing your thoughts.
Just to point out, Xiaomi EU is in a way a custom rom. The Xiaomi.EU community taken the Chinese rom, that has less bloat and more features, translating it and sharing it to people. Just because it it called debloated, that does not mean it does not come with the same Xiaomi Apps. It is still MIUI and that means some Xiaomi apps will still be impossible to disable and also apps like the Xiaomi Security that will softbrick your phone if disabled, still is needed and will cause the same thing in the Xiaomi.EU rom.
It is the main reason I am thinking of trying crDroid, or else like you said, I would not mind just a debloated stock rom, since afar from all the needed Xiaomi apps, MIUI seems quite enjoyable to me. If you check their forums though, you will see even the Xiaomi.EU has it's own problems.
Click to expand...
Click to collapse
Ohhhh I see! I think I'll try crDroid too and Arrow, as long as it's debloated, the IR works as long with the radio and the nfc, I'm happy.