Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Newbie2022 said:
Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Click to expand...
Click to collapse
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Newbie2022 said:
.... i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe......
Click to expand...
Click to collapse
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming,
By starting without Gapps to see what happens with battery, you find if the reason is rom or Google.
Other reasons could be VOlte, pocket detection, proximitysensor, hanging updates.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Laptapper said:
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man yes i know the risk but it seems to be the only option i have i tried to dirty flash Roms following instructions, but the battery drain issue persist so i was trying as last resort to clean flash and then stock rom in a hope to resolve the issue. Thank you very much really appreciated
Elinx said:
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Click to expand...
Click to collapse
Yeah the issue was after flashing the rom something happened i don't know exactly what it is but the screen battery consumption hit the roof altouth i capped the refresh rate at 60 and use dark mode and brightness to 35 max . Before flashing the rom(lineage) i didnt had this issue with older other roms i flashed before the issue (pixel experience and pixel os)...I dirty flash other roms and even stock rom through Miflash tool but the same issue continued so i was hoping if i can clean flash the stock rom. Thanks alot man.
Newbie2022 said:
... i tried to dirty flash Roms following instructions, but the battery drain issue persist ....
Click to expand...
Click to collapse
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Elinx said:
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Click to expand...
Click to collapse
Ok i will check the spoof issue and try to flash stock rom again via Miflash tool hopefully the issue will be solved. Thanks a lot for the tips and insight
Related
Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?
Try to flash the new TWRP, firmware.
and flash the rom with full wipe
svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.
So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???
Nobody got any idea?
felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.
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.
Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
But I wanted to give ressurection, crdroid, havoc a try too.
Now there is a conflict between the statement of xiaomi.eu:
FORMAT /data partition (NEVER wipe System or Persist!)
Click to expand...
Click to collapse
And e.g. crdroid:
Wipe Data/Cache/System when coming from non-AOSP ROMs
Click to expand...
Click to collapse
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings
houston_ said:
Now there is a conflict between the statement of xiaomi.eu:
And e.g. crdroid:
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
Click to expand...
Click to collapse
No need to format /System, as it afaik can result in an instant-bootloop to Fastboot, which may then cause you to reflash the whole MIUI Fastboot ROM.
When coming from MIUI to AOSP ROMs, formatting /Data (aka the "Format Data" Option where you have to type "yes") should be enough.
Same process goes when going back to MIUI from AOSP.
Hope it helped!
houston_ said:
Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
......
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings
Click to expand...
Click to collapse
The system partition is home to the OS. Every time you flash a ROM, you replace the system partition. If you want to return to stock, flashing MIUI will restore the stock system partition.
In reality there is no need to wipe the system partition, because flashing a ROM will wipe it automatically anyway, before installing the new ROM.
When flashing new ROMs, doing a factory reset is all that's needed. You should rarely need to enter advanced wipe menu in TWRP.
The only extra step required is when flashing over MIUI (official or custom version). In this case you will also need to format data too.
Follow my guide for flashing
https://forum.xda-developers.com/k20-pro/how-to/simple-guide-flipkart-owners-t4151007/post83329343
Thanks for both of of your answers! So nothing really changed since my HTC10. On my Cubot I used gsi images... Unsuccessfully, but quite easy.
Just wanted to ask before loosing something important
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
Okay sorry for coming here with this, but I've searched for a way to resolve this on my own and can't seem to be able to.
I'm using Octavi Rom on my Redmi Note 10 Pro, and I recently tried to do the update from 3.0 to 3.2. I use TWRP custom recovery, and ofc no device decryption, so I had issues wiping dalvik/cache. I already assume I did something wrong because everyone else was able to install fine. My device didn't boot loop but from the first time it loaded, I had issues logging in because my settings crashed, system crashed, my phone is very slow, and I have no idea what to do to fix it. https://hastebin.com/osihiyibal This is the log I get when the settings crashes.
Can someone give advice on what I can do? I can't open device settings *at all*. I can't wipe data or do a factory reset. I would just like some help because my phone is pretty unusable sometimes in this state, and not sure if I can wait for A12 decryption to be a thing. Thanks in advance.
If you are okay with losing everything and just want a clean install and use the device you can try the following. If you already have TWRP installed but are getting the decryption error, Go into TWRP go to Wipe, Format data, Type yes, then click the blue check mark. It should clear the decryption and you can do a fresh install of whatever operating system you want to install.
Thank you so much! You're a life saver. I was able to reinstall the rom with no issues by wiping the data. Everything is working great too. Like having a new phone all over again, but I don't care. So much better than the crashing and slowness. <3 Thank you!