I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Rifat Rezwan said:
I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Click to expand...
Click to collapse
apply update via zip. or adb sideload. you will get out of the issue
sukhwant717 said:
apply update via zip. or adb sideload. you will get out of the issue
Click to expand...
Click to collapse
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Rifat Rezwan said:
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Click to expand...
Click to collapse
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
timbernot said:
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
Click to expand...
Click to collapse
I've flashed AICP Nougat and gapps. still no luck. even with adb I cant boot anything other than twrp.
Read the link I posted in my first reply. Jeeese
timbernot said:
Read the link I posted in my first reply. Jeeese
Click to expand...
Click to collapse
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Rifat Rezwan said:
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Click to expand...
Click to collapse
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
timbernot said:
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
Click to expand...
Click to collapse
Cleanstock solved the problem. Thanks
Rifat Rezwan said:
Cleanstock solved the problem. Thanks
Click to expand...
Click to collapse
Nice
Back Cleanstock up so can revert back to it , flash away until bugs have been ironed out.
Above , switching between airplane mode and data works for me after a reboot and works flawlessly after .
Try AICP ROM
Its marvelous , regular updates
Hi, I have the same problem, actually it happened after updating to latest version of lineage os. I tried everything (various wipes and flashes, restoring stock backups, flashing cleanstock as suggested) but no luck.
I can't even reboot to fastboot through adb, my phone is just a recovery!
I can't imagine how this could impact, but I've just changed my lcd. But I started the update after changing the lcd, and the phone was working before with the previous LOS version, so...
EDIT: ok, I managed to make it work, I flashed TWRP 3.0.3-M3 (I was on 3.0.3-M2, I didn't try to reflash the same version). Too bad I needed just this, I wiped everything, even internal storage lol.
Related
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage
delete
Just flash twrp again!?
Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me
daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.
What version of OOS was you on prior to flashing CM14.1?
daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.
Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?
I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28
jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.
DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.
malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it
Same, when I flashed cm 14.1 I also got blank TWRP.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?
LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!
Please try the modified TWRP, 3.0.2-22
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Use fox twrp to flash.
haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I used TWRP. Also tried orangefox
haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I also tried flashing the firmware first
-iwl- said:
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Click to expand...
Click to collapse
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
i have no idea what to do now
-iwl- said:
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
Click to expand...
Click to collapse
when i flashed miui 12 beta it showed on operating software installed before reboot.
paradise220 said:
when i flashed miui 12 beta it showed on operating software installed before reboot.
Click to expand...
Click to collapse
it seems they released a broken rom. i tested again with lineage os and it worked perfectly. so its xiaomi at fault here
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Use chinese twrp
JrAdams said:
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Click to expand...
Click to collapse
Gapps or any google related services doesnt seem to be working with this beta. lots of bugs encountered too, i might just go back to havoc os
Yunus Ceyhan said:
Use chinese twrp
Click to expand...
Click to collapse
Got it working already. just had to flash magisk along with the rom
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.