I'm having a redmi 6A (codename: cactus) device. I decided to install a custom rom to boost the performance of the device. Since there weren't much options of official builds for the device, I chose to try a unofficial build.
Here's the telegram group i found that rom on :Redmi 6A Official Updates
I chose the Octavi OS build from it.
As usual I unlocked the bootloader, installed twrp custom recovery and ready to flash the zip file.
Btw, here's the zip file I flashed : Octavi OS zip
I wiped all the necessary options and flashed the zip without flashing magisk(coz I don't prefer to root). After restarting, the miui logo came but the rom won't booted ever since waiting for hours, so I reverted back to stock.
But after few weeks, I again planned to flash the same build but with magisk file.. And surprisingly enough, the rom logo came and it booted without hassle.
But I wanted to know the exact reason for the former, so I can report it to the dev and he might fix it..
Thanks for your time to read my this sh*t here, any reply would be appreciated .
Related
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
10.3.2.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.3.2.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117882402
10.3.1.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.3.1.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=1395089523397934131
10.2.2.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.2.2.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=1395089523397908184
10.2.1.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.2.1.0.PDGCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=11410963190603887317
10.0.7.0
https://sourceforge.net/projects/xi..._MIMix2S_V10.0.7.0.PDGCNFH_v10-9.zip/download
https://androidfilehost.com/?fid=11410963190603845043
New links will be posted here.
10.0.4.0 bootloops for me
Coming from Pixel 3 Experience GSI ROM by EnesSastim. I can fastboot flash the official MIUI 10 Global which works but every time I flash this ROM via TWRP I just get bootloop.
Full wipe doesn't seem to help so I guess I'm sticking on the official Global ROM for now. Any ideas?
10.2.1.0 added in OP.
mike freegan said:
10.0.4.0 bootloops for me
Coming from Pixel 3 Experience GSI ROM by EnesSastim. I can fastboot flash the official MIUI 10 Global which works but every time I flash this ROM via TWRP I just get bootloop.
Full wipe doesn't seem to help so I guess I'm sticking on the official Global ROM for now. Any ideas?
Click to expand...
Click to collapse
Not sure if you ever figured it out but the instructions on EU's site are terrible and not very descriptive.
When they mean when they say "Wipe /Data" is to hit Wipe > Format Data > Type Yes (and swipe to confirm I believe) You will then have to copy over the zip to your phone and flash (That's why the instructions are written that way)
Keep in mind, that this will wipe your internal storage so make a back up. It also takes a long time to boot, longer than clean miui install.
is it possible to flash from one MIUI 10 rom to another? mine is on stock chinese 10 rom now, and can't see any files on the root folder of the phone under recovery. may need to use the rom's flash function.
Hello friends, I hope and can help me, it turns out I have the ROM installed but not let me have permissive the seLinux with the kernel stock, just let me if I put a modified kernel, the problem is that for me none of all the modified kernel gives me the autonomy that gives me and L kernel stock, I want to have the permissive ROM of seLinux with the kernel stock, someone knows how? Thank You for your help
10.2.2.0 added in OP.
Might sound like a silly question, but when the phone was first launched and people applied xiaomi.eu roms, some reported that installing magisk would brick their phones for whatever reason. Is this still the case? I just want to pass my safetynet
10.3.1.0 added in OP.
10.3.1.0 reuploaded: https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-10-3-stable-release.47170/post-480558
10.3.2.0 added in OP.
10.3.2.0 reuploaded.
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
fordstang99 said:
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
Click to expand...
Click to collapse
Trying the canary build
It worked with canary 19.4
Mods please delete if need be
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol