Related
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
Well my 3T after days of "Pending Shipment" is on the way and luckily, Stable Nougat is out!
So I had some questions about recovery in preparation.
1. In OnePlus's stock recovery, is there a way to mount storage? I ask because basically, while I'm still waiting for my phone to arrive, I'd download the Nougat Rom and as soon as I receive the phone, boot into recovery, mount storage, get the file and then flash the Update to have a completely clean install.
2. If it's not possible to mount storage in recovery and I have to setup the phone, I'd just put the Update on the phone's storage after setup and would then, be able to do a clean install from the stock recovery right?
Just wanted some clarification as I think just having the update ready to go would save me time of actually downloading the update.
Thank You and Happy New Year
The internal storage is mounted automatically in stock recovery.
Apart from that, if you want to reinstall your system, download the full rom. The ota will only work when your system partition is untouched.
Also, why do you want to re-setup your phone? If you do not want to redownload your update, do not do a factory reset.
Jo_Jo_2000 said:
The internal storage is mounted automatically in stock recovery.
Apart from that, if you want to reinstall your system, download the full rom. The ota will only work when your system partition is untouched.
Also, why do you want to re-setup your phone? If you do not want to redownload your update, do not do a factory reset.
Click to expand...
Click to collapse
I think you misunderstood, I don't have it yet it's on the way.
I have the 1.4gb Nougat rom and what I'm saying is that instead of setting up the phone and then waiting for Nougat to download and etc,
as soon as I get, boot into recovery and just install Nougat to save myself time while doing a clean install at the same time and moving from there.
But you answered my question about storage being mounted in recovery, thanks.
star4oelife said:
I think you misunderstood, I don't have it yet it's on the way.
I have the 1.4gb Nougat rom and what I'm saying is that instead of setting up the phone and then waiting for Nougat to download and etc,
as soon as I get, boot into recovery and just install Nougat to save myself time while doing a clean install at the same time and moving from there.
But you answered my question about storage being mounted in recovery, thanks.
Click to expand...
Click to collapse
I think it would be best if you would just sideload the ota package
I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.
gavin19 said:
I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.
Click to expand...
Click to collapse
Well that sucks, to much work for me, thats why I wont go back to MIUI even tho im curious with all the new updates on MIUI..... Im good with a AICP custom rom
Ultraman666 said:
Well that sucks, to much work for me, thats why I wont go back to MIUI even tho im curious with all the new updates on MIUI..... Im good with a AICP custom rom
Click to expand...
Click to collapse
I just installed epic coming from AICP it wasn't a big deal for me, it's all in the OP
james1089 said:
I just installed epic coming from AICP it wasn't a big deal for me, it's all in the OP
Click to expand...
Click to collapse
AICP to MIUI/Epic is no different than anything else. You just flash it. The challenge comes from trying to keep the unencrypted status when doing so without having to transfer all your media off/onto the phone.
gavin19 said:
AICP to MIUI/Epic is no different than anything else. You just flash it. The challenge comes from trying to keep the unencrypted status when doing so without having to transfer all your media off/onto the phone.
Click to expand...
Click to collapse
Well as far as I know I'm still unencrypted
gavin19 said:
I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.
Click to expand...
Click to collapse
That's about the same for me will use it for a week then go back to AICP.
james1089 said:
Well as far as I know I'm still unencrypted
Click to expand...
Click to collapse
If you go into Settings > Security and it says 'Encrypt Phone' then you're still unencrypted.
gavin19 said:
If you go into Settings > Security and it says 'Encrypt Phone' then you're still unencrypted.
Click to expand...
Click to collapse
I'm still unencrypted, epic flashed everything I didn't do anything. It flashed dm-verity and SuperSU.
I'm fairly sure my USB port is broken (after 3 weeks), my phone charges "slowly" (10 hours to fully charge) and my PC won't recognise my phone at all, even in ADB/fastboot. I'm trying to send it back for a warranty repair, but I want to try get it back to stock to see if that solves the problem and then if not for the warranty repair.
Currently on lineageos, rooted with TWRP. I'm wondering if it's possible to flash a stock rom image using TWRP to achieve this? Possibly using one from this list
One of these from the link says "recovery", would this be the one to go for? If so, how would I keep the .zip on my storage after a wipe, or would I not need to wipe?
Sorry for the long post, wanted to give as much info as possible!
Cheers
Bump?
Clean Flash Recommended
Wipe Dalvik System Data and Cache
Flash Stock Rom Beta/Stable
..
first use the wipe menu and then select the rom file and swipe to confirm the flas in sd card just open zip and swipe to confirm Flash.
..
if in bw copying the rom if it stuck in the middle and then close it self or while flashing it say "zip is corrupt"
make sure you have enough space and get the stock rom zip from Official Source.
GooD Luck.
MIN313 said:
Clean Flash Recommended
Wipe Dalvik System Data and Cache
Flash Stock Rom Beta/Stable
..
first use the wipe menu and then select the rom file and swipe to confirm the flas in sd card just open zip and swipe to confirm Flash.
..
if in bw copying the rom if it stuck in the middle and then close it self or while flashing it say "zip is corrupt"
make sure you have enough space and get the stock rom zip from Official Source.
GooD Luck.
Click to expand...
Click to collapse
Thanks for the reply, is it possible to save the rom somewhere that it won't get deleted after a wipe? I don't have an external SD card slot. I'm a little scared because if I get it wrong I have no USB connection to get anything onto my phone ??*
hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!
p_vujic07 said:
hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!
Click to expand...
Click to collapse
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"
p_vujic07 said:
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"
Click to expand...
Click to collapse
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do
p_vujic07 said:
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do
Click to expand...
Click to collapse
Finally I done it, i formatted the data and then installed Havoc OS. Thanks @p_vujic07 (myself)! You are such a genius!
sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0
fonzacus said:
sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0
Click to expand...
Click to collapse
heyy, please sorry for this late answer. i was moving out so i couldn't answer you. it wasn't xiaomi.eu, but it was mi-globe. i tried to install with root (magisk) or wihout it but it wouldn't work. i tried xiaomi.eu, but when i saw that MIUI won't be supported on Redmi 8 i installed havoc again.
the encryption wasn't a problem so i really don't know what was it. maybe i am stupid so i get this now, but do you need to have official MIUI for mi-globe to work? i don't know, and, honestly, i don't want to. i am happy with my havoc, so anyways thank you and sorry for the latest answer you'll ever see!
like i said, most miui roms do require stock stuff (remember the wipes), you could also manually install a miui imgs and (theoretically) install miui roms but yeah i havent tried that.
how much internal storage does it show
are you using orfox 11.1_0 beta
did you flash an encryption disabler
Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)
p_vujic07 said:
Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)
Click to expand...
Click to collapse
Orange fox is R11.0_2
I installed havoc os only because I can't receive messages, like from what's up. With havoc os it works perfectly fine so I just wanted to install MIUI to see if they fixed the problem in 12.5 (or what was it) version
you should prolly reinstall stock again as sdcard0 should show 48gb (max 64). something messed up your partition. if its a low priority you could let it slide.
miui based roms wont work from most custom roms since they are using different system|vendor imgs.
Oh, you didn't understand. My phone has 32 gb, so it's all good. I don't want to install MIUI now because I don't know if my problem if solved (notifications) and MIUI 13 is going to come out, and Redmi 8 won't support it
ah sorry, i completely forgot about the 3/32 variant (ive only seen the 4/64).
i doubt 11 will even come out as fastboot 12.5.1 is only out for china only, and its been months lol. wouldnt matter to me for tons of reasons