Related
Hi,
I have tested the liquidremix rom which is great, but I still wanted to go back to my stock OSS
So I started TWRP, hit restore, everything seem to work fine, but when I reboot the system I'm stuck at the boot animation.
When I reboot the device to TWRP and check the file manager or my backup folder there are only cryptic and weird letters...
How do I restore my backup properly ?
Try to go back to TWRP 3.2.1.0 i think that that works
everything is gone, you will have to restore with the brick tool, happened to me last week and still not sure why, apparently backing up with TWRP you only need to ticket DATA and that's it.
You need to do two things whenever you restore with TWRP. First is factory reset in TWRP before the restore (that will wipe data). Second is restore system, boot, and data ONLY.
The weird file names and cryptic letters is from the encryption from the old rom. I strongly recommend that you invest in an OTG flash drive so you can store TWRP backups on it. Then you can properly wipe the phone. On the plus side this has happened to me before and I never needed anything special like the unbrick tool to get my TWRP backup up and running smoothly.
and there is a better twrp than twrp. The official is by Dees Troy and the un-official one by Joe Moss Jr. is here. https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Joe's big improvement is a usable 'mtp', ie. access that thumb drive.
Also puts the vibration back in to the key press.
First if you r seeing weired letters in twrp like xdjdhdhdhd folders. Then go to fastboot mode flash newest twrp. Img then ij recovery first flash your liquid remix furst, then flash twrp installer zip niw reboot to recovery.
Now factory reset your phone.
Now if you have oos backup. Then restore everything except system.
And then restore system alone at last now reboot it will work.
your gonna need the flashable oos 5.1x which is one here
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
fastboot to twrp
abd push the stock.zip to the phone <-assuming you know this.
and flash it from twrp.
reboot
fastboot twrp again and flash twrp.
this is where decryption comes in handy
Restoring backups with twrp will fail almost all the time. I've yet to do a successful restore and I've tried every method. You're gonna have to flash back to stock OOS and start over.
If anyone has successfully restored more than one backup then I would start a new thread with the exact method you used.
That worked.
I still wonder why not to restore system.
If I take a nandroid backup should one backup
system or system image, data or data image ?
I was trying a new rom the Resurection Remix V6.2.0 Android 8.1.0. i wanted to go back to my TWRP Backup of OOS 5.11 . I wiped data/cache/System . Tried to restore rom . it restored successfully but i didnt do wipe data thing. when i tried to reboot twrp blu, the recovery was lost. then i had to fastboot boot reovery. and lot of wierd folders were created on my phone internal memory. All data lost.
i had to flash the full 5.11 stock zip via twrp. tried to reboot again lost in bootloop. Switched back to stock recovery and make a factory reset then it booted.
switched off the phone back to Blu spark TWRP. again wipe data cache and system. Then restore the TWRP Backup previously double saved on a usb drive. This Time it restored successfully and booted as well fine.
i think i should have made a factory reset or format data before restoring from A Lineage OS Rom OS to OOS TWRP Backup
thats what made the whole internal drive mess and to be formatted as well
My Question is it only important to format data and then restore twrp or also backup and make restore of system.img of OOS backup as well
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
Try installing magisk too.
mikex8593 said:
Try installing magisk too.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried installing magisk in between OOS and the TWRP, and then also tried installing OOS, TWRP, rebooting, and installing magisk. No luck either way.
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Format is the answer.
MaxRabbit said:
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Click to expand...
Click to collapse
just simply flash oss9.0.2 two time using twrp then get hold of 9.0.2 boot img go back to twrp and the select flash image flash the image and let it boot.
if it works toss a thanks.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
Thank you for this. I was trying to dirty flash 9.0.2 to fix a notification issue and ended up in the same situation as you. Format ended up fixing it. Only crappy part is I lost about all my text messages with my SO. Google said it has a 2mb backup for SMS so I'm hoping it got all 30k+ of it
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
Tried this and it ended up causing the exact same problem. The folks installing the new OB8/9 seems to be having similar issues. Not sure what's going on.
its because of security patch. 9.0.2 has nov sec patch, lineage you flashed has dec sec patch. i have experienced this in pixel rom. just flash lineage Nov build, then wipe data and system and flash OOS 9.0.2 and twrp.
do a clean flash
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
You know if all else fails you could always download the Qualcomm MSM tool and boot into Qualcomm mode (with the phone off hold vol down button for about 10-15 seconds and plug into computer), you won't see anything on the screen, load up the tool and it shall put u back to full stock. This will solve all and any sort of bricking which if you flash alot you will by default probably learn how to use
fastboot into twrp
Flash TWRP within twrp
Format all data.
Reboot recovery
transfer OOS
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot recovery
Flash kernel/magisk/etc
Reboot system.
I just want to tell you that I love you. The format data finally fixed this for me.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
abati said:
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
Click to expand...
Click to collapse
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
mikex8593 said:
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
Click to expand...
Click to collapse
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
tabletalker7 said:
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
Click to expand...
Click to collapse
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
abati said:
after whiping data, phone is stuck and twrp does nothing
Click to expand...
Click to collapse
After a whipping I wouldn't be inclined to do much either!
croques said:
After a whipping I wouldn't be inclined to do much either!
Click to expand...
Click to collapse
what do you mean, could you be more clear and specifiek ?
abati said:
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
Click to expand...
Click to collapse
Use a fastboot rom. That will wipe EVERYTHING - and guarantee that you have a usable phone afterwards
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
You probably wiped system that's why you had nothing to boot into
yldlj said:
You probably wiped system that's why you had nothing to boot into
Click to expand...
Click to collapse
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Its the easy answer, say that you wiped system or such.
If you wiped Data with Magisk installed, without flashing the stock kernel, you won't be able to boot, since Magisk stores stuff necessary to boot on Data.
Usually, people is stuck on a infinite bucle on TWRP after this, you couldn't even enter TWRP? that's new. The issue you're telling sounds like you changed slot in TWRP somehow to an unused one or something like that, never heard of that.
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Yeah I have wiped data in twrp with no issues. TBH it just sounds like there was no system to boot into. Wiping data is just that and shouldn't make the phone unbootable. Also you fixed the issue by flashing OOS which makes me believe this also. If you want to factory reset your phone the best way is to do it through settings.
Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
who ah way said:
Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
Click to expand...
Click to collapse
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
strongst said:
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
Click to expand...
Click to collapse
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
who ah way said:
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
Click to expand...
Click to collapse
Generally the factory reset does all too need(from android settings). Why theres something left of your device I don't know.
But I meant format internal storage, not wipe internal storage.
So reboot to twrp - wipe - format and follow the instructions reading the hints.
Again: that does not wipe your twrp, system, system data only the internal storage like music, photos etc.
For installation, it's OK what you wrote
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
who ah way said:
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
Click to expand...
Click to collapse
It's a good way to break a potential boot loop issue down, time consuming, but worth the effort in case it boot loops
Hello everyone,
As stated, I began by waiting the 7 days to get the bootloader unlocked, then proceeded to copy this EU rom to internal storage, after following this video, my phone reboots after installing the room and goes straight into TWRP. When I click on reboot on TWRP, regardless if I choose System, Recovery or Bootloader, the phone keeps coming back to twrp. I would really appreciate if anyone can help me.
desmocedici_77 said:
Hello everyone,
As stated, I began by waiting the 7 days to get the bootloader unlocked, then proceeded to copy this EU rom to internal storage, after following this video, my phone reboots after installing the room and goes straight into TWRP. When I click on reboot on TWRP, regardless if I choose System, Recovery or Bootloader, the phone keeps coming back to twrp. I would really appreciate if anyone can help me.
Click to expand...
Click to collapse
Seems some system files got wiped. Open twrp and format data (don't wipe), after this restart to recovery and transfer the rom into your phone and flash, then reboot that's it. If this still occurs boot loop or returns to twrp, then download full firmware and flash it through mi flash, make sure to only select clean flash not to lock, and then wait until it boots to the welcome screen. After that flash twrp, format data (don't wipe), restart to recovery and transfer the rom into your phone, and flash and then reboot.
Hope this will fix your problem, please let me know
mrnannu said:
Seems some system files got wiped. Open twrp and format data (don't wipe), after this restart to recovery and transfer the rom into your phone and flash, then reboot that's it. If this still occurs boot loop or returns to twrp, then download full firmware and flash it through mi flash, make sure to only select clean flash not to lock, and then wait until it boots to the welcome screen. After that flash twrp, format data (don't wipe), restart to recovery and transfer the rom into your phone, and flash and then reboot.
Hope this will fix your problem, please let me know
Click to expand...
Click to collapse
Thanks for your reply.
I was able to get it fixed by changing the filesystem on the data & internal partitions to f2fs. Did a reboot and phone went into MIUI after that. I regret flashing the EU rom but that's another topic.
You
desmocedici_77 said:
Thanks for your reply.
I was able to get it fixed by changing the filesystem on the data & internal partitions to f2fs. Did a reboot and phone went into MIUI after that. I regret flashing the EU rom but that's another topic.
Click to expand...
Click to collapse
Can go back to Chinese again if you want. Just flash latest .zip format ROM from http://mifirm.net .