Develop Bugs

Can't flash custom roms

Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.

nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?

Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp

nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.

Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22

Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?

Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.

Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange

nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?

Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time

nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try

Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works

OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.

This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,

I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....

mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.

mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?

XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!

mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.

XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again

mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??

mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!

XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..

mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.

XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!

mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.

@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!

Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk

freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

Moto G5 automatically boots into TWRP

Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?

I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.

I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings

CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.

SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?

Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings

grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully

OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect

Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup

rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?

[Help]twrp stock rom system,vender & anything needed for restore data REDMI 6 PRO

i accidently flash the custom rom but now i dont have the original rom backup :crying::cryinglz help any body can upload the twrp system ,vendor and any other things required to restore the original rom :angel::angel:
redmi 6 pro indian version or atleast english version plz
edit : twrp sakura

Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/

coolek33 said:
Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/
Click to expand...
Click to collapse
will i be able to flash the stock rom because i tried indian version but it wont work twrp sakura
also which one shall i download fastboot or recovery ?

If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.

coolek33 said:
If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.
Click to expand...
Click to collapse
1) lol is there a way to not to lock my bootloader again because if it fails then all is left is fastboot??
2) and also twrp will be removed or shall i flash twrp again or will it brick my device ??
3) or i need to wait 15 days and unlock my device again??
man lot of questions
4) my mi account has unlock permission so do i need to permission again because right now i am using custom rom to keep my phone alive.:crying:
these questions will raise to all if they did the same mistake some more questions but lets see these first
also thanks man you are wonderful helper

If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.

coolek33 said:
If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.
Click to expand...
Click to collapse
i flashed
crdroid rom from redmi 6 pro forums
bootable
kk i will try advanced wipe
also that redmi6 pro tool kit u mentioned is it mi unlock tool if not plz send me the link plz
also thanks i will contact you when something went wrong
also when i flashed custom rom it shows installing unconditionally why
also the restore function is not working is it the twrp fault or the rom
it doesn't boot says boots on logo and then shows the boot animation waits for 5 min and boots twrp again automatically why???(when i try to restore the crdroid rom not to mentioned i tried flashing resurrection os but goes on boot loop )

When flashing custom ROM different from miui you should wipe dalvick, cache, data and system before flash. Then flash RR or something else gapps and boot.

Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436

coolek33 said:
Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436
Click to expand...
Click to collapse
found this site
https://mi-globe.com/rom-builder/

Ethical Hacker|Youtuber said:
found this site
https://mi-globe.com/rom-builder/
Click to expand...
Click to collapse
lol man that unlock tool did the trick i flashed the above rom from the mi globe rom and my phone got locked again i open the tool and then i unlocked the phone and boom it got unlocked but remember that when u unlock ur data will be deleted and always keep the backup of ur twrp image
after unlock and the login id and pass that pass u will need to enter the phone startup otherwise just boot to fastboot and then bypass account
man finally back to miui without any bugs with root man what else we want

Question POCO F3 bricked

Hey, I just unlocked my bootloader after waiting for the 7 days today I wanted to install the MIUI EU, and i follow the steps that they have on their website, installed and boot into recovery mode TWRP format data, and install the ROM that i downloaded, after that the wipe on the cache. When i rebooted my phone he didn't boot and was stuck on POCO screen. After 1 hour it was stuck on that, I decided to try and flash stock firmware with miflash tool, did the steps and after 604 seconds it shows success on the result but it doesn't boot the same thing stuck on POCO screen.

You need to Format data. Not cache.
Then the phone will boot up just fine.
Go, do it again.

Try to flash it using miflash again.
Then Boot TWRP, then flash it again + ( FORMAT DATA)

laid1995 said:
Boot TWRP, then install it again.
Click to expand...
Click to collapse
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again

Don't freak out. Your phone is fine. As long as you can boot into Fastboot. Then you are fine.

skullgnik said:
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again
Click to expand...
Click to collapse
Try otg.

laid1995 said:
Try otg.
Click to expand...
Click to collapse
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp

skullgnik said:
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp
Click to expand...
Click to collapse
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.

laid1995 said:
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.
Click to expand...
Click to collapse
What option should I select then?

skullgnik said:
What option should I select then?
Click to expand...
Click to collapse
Please tell me you didn't select " wipe and lock " before !

i did
laid1995 said:
Please tell me you didn't select " wipe and lock " before
Click to expand...
Click to collapse

skullgnik said:
i did
Click to expand...
Click to collapse
welp...... Try unlocking the bootloader again

Do as he says. Hopefully it gets unlocked.

laid1995 said:
Do as he says. Hopefully it gets unlocked.
Click to expand...
Click to collapse
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!

You're welcome.
As you wish, just try, at least to unlock bootloader since you're still fresh. As to make sure that it can be unlocked.

skullgnik said:
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!
Click to expand...
Click to collapse
you don't have to use memeui, official EvolutionX just released today!

JustAnAverageGuy_19 said:
you don't have to use memeui, official EvolutionX just released today!
Click to expand...
Click to collapse
I will think later this day about installing a custom ROM. but I don't hate miui as much as people usually hate, I find some things extremely useful I just don't like some UI esthetics i prefer the minimalist look of pure android. But some things like the cloning apps are very handy to me. Some bugs that are present atm on custom ROMs for this device like the double-tap to wake up are very negative to me because I have always used that feature since 2014 and I'm extremely used to it.