After flashing stock miui 11 using fastboot and relocking the bootloader i tried after 2 weeks i unlocked the bootloader sucessfully and flashed the OrangeFox recovery i had flashed before.When i tried to install custom roms it would get stuck at the boot logo of the rom,i tried 3 different roms including pixel experience(latest),crDroid and finally Evolution X.The only thing i can do at this point is flash stock miui again and when i do so my netflix has widevine l3 and not l1 as usual on the stock rom with locked bootloader.Any help?
georgedanel said:
After flashing stock miui 11 using fastboot and relocking the bootloader i tried after 2 weeks i unlocked the bootloader sucessfully and flashed the OrangeFox recovery i had flashed before.When i tried to install custom roms it would get stuck at the boot logo of the rom,i tried 3 different roms including pixel experience(latest),crDroid and finally Evolution X.The only thing i can do at this point is flash stock miui again and when i do so my netflix has widevine l3 and not l1 as usual on the stock rom with locked bootloader.Any help?
Click to expand...
Click to collapse
Format the data partition after flashing the custom ROM.
I think you wipe all partitions before installing custom rom right? You should not wipe system and vendor partitions after unlocking bootloader and installing recovery
Related
Hey guys
I m getting problems after successfully Flashing custom rom
I M using YU yureka On 4.4.4 kitat My phone is Rooted and Using Twrp recovery
I wanted to flash a customROM and upgrade yureka to CM 13
So First I downloaded CM 13 unofficial by santosh
Then wipe data dalvik cache and it was flashed successfully and then flashed gapps
Both got successful and when I reboot my device. Got stuck on YU logo I waited for 20-25,min but no result
Then I boot in recovery and restored my old stock ROM which was backed up
Then I downloaded crdroid ROM
But i got status 7 error so I deleted both rom
And Now I downloaded tamsek ROM it got successfully flashed and same problem stuck at boot logo I have restored to stock and using
But how do I flash Custom ROM
Why I m Getting error
help me some1
Reply fast with solution
What's the version of TWRP?
First try to update to COS12 stock ROM and check if its booting normally. Afterwards try to flash custom ROMs from latest TWRP recovery.
Yes I thought that only to flash it on COS 12 but if another solution is available to direct update it to CM 13
And I m using Latest version of Twrp recovery
Dark_Knight16 said:
Yes I thought that only to flash it on COS 12 but if another solution is available to direct update it to CM 13
And I m using Latest version of Twrp recovery
Click to expand...
Click to collapse
You have tried everything but nothing worked. So I think flashing official COS12 first is only option left now.
I am currently in MM, i want to go back to MIUI to try MIUI8 Global beta. I have one twrp back for MIUI7, but when i flash that from recovery (twrp 3.0.2), it shows error. Then i tried with twrp 2.8.7. but same error.
Now when i go back to MM by restoring the MM roms from TWRP recovery, phone is not unlocking even if i am entering the correct pattern. First i flashed revert back to TWRP 3.0.2, then tried to restore the back up MM roms.
I also tried to flash new MM roms, but the SIM and Wifi is not detecting.
Is there anyway that i can flash ROM. I don't think my phone is bricked, but somehow there was some error happened while i flashed MIUI backup from TWRP 2.8.7.
Device name Redmi2 2014818
You have to do Fastboot Update.
Persizi said:
You have to do Fastboot Update.
Click to expand...
Click to collapse
So will the MM recovery ROMs will work now if i again move to MM based on CM13.
rkpg said:
So will the MM recovery ROMs will work now if i again move to MM based on CM13.
Click to expand...
Click to collapse
Exactly. Just flash the TWRP recovery and you will good to go.
you may try flashing miui 7 rom from fastboot then install miui 8 from recovery ( from update > choose update package)
Flash phillz recovery by jav team and boot up in recovery then-clean to install a new rom-and flash miui 8 kk ROM it will successfully flash the ROM and will restore original firmware and ur good to go...phillz recovery will give no error while flashing...
Some times twrp gives an error by saying that its a ROM for 2014811 and u cannot install it on 2014818 better use phillz for flashing miui ROMs...
I hope this method will help u.
I haven't unlock my phone yet. I used the qpst tool to flashed the rom to zui 0.9. Then I flashed the offical twrp.
Offical cm13, cm14 and some aosp rom(slim etc.) can boot and work well on my device after flashing, but cm based rom such as nuclearom and bliss cannot boot. They always stuck on the boot screen and fail to boot into desktop after a clear flashing. Have I missed something?
You have to unlock bootloader and do clean flash otherwise you may encounter such problems with custom roms
Hi!
I have my device a few days ago and I wanted to flash globerom (alias smiui), but when I tried to flash it in twrp it gave me strange installation logs and when it finished it killed everything except fastboot (I couldn't boot into system, recovery and the power-and-volumeup mode) I flashed twrp again and restored my old backup and than it fixed everything, but when I tried to flash a newer miui (the one can be downloaded from miui.com) it did the same. So what can I do than?
I don't want to do flash in fastboot, because a corrupted fastboot package killed my previous redmi
Is there any risk less method to flash miui roms in twrp?
Thanks for all the answers in advance!
P. S. : Cm13 worked well
I prefer flash a fastboot MIUI ROM compared to a recovery MIUI ROM
Did you disable "DM-Verity" in TWRP after flashing and first start?
http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/
ConradB said:
Did you disable "DM-Verity" in TWRP after flashing and first start?
http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/
Click to expand...
Click to collapse
Thanks for the tip! It worked!
Hey XDA,
I've just unlocked my bootloader and flashed TWRP 3.1.1. I was on the stock Nougat OTA. I wanted to install LineageOS 14.1, but I get a bootloop on the latest nightly. Process was factory reset/wipe -> flash ROM, Gapps, SU -> wipe dalvik, reboot I figured that maybe it was an issue with the nightly, so I installed Resurrection Remix and got the same issue.
Stuck on boot animation, occasionally a very slight vibration.
Does anyone have an idea of what this is?
GuySurname said:
Hey XDA,
I've just unlocked my bootloader and flashed TWRP 3.1.1. I was on the stock Nougat OTA. I wanted to install LineageOS 14.1, but I get a bootloop on the latest nightly. Process was factory reset/wipe -> flash ROM, Gapps, SU -> wipe dalvik, reboot I figured that maybe it was an issue with the nightly, so I installed Resurrection Remix and got the same issue.
Stuck on boot animation, occasionally a very slight vibration.
Does anyone have an idea of what this is?
Click to expand...
Click to collapse
Search a little... most custom ROMs do not work on a device that was updated to Nougat due to differences in radio firmware and partitioning. Try a newer Nougat custom ROM like Dirty Unicorns, and only flash ROM and appropriate Gapps, after boot is verified try flashing root with the latest SuperSU (2.82) or Magisk (14.0) only.
And clean flash... wipe everything but internal/external storage, then flash.
GuySurname said:
Hey XDA,
I've just unlocked my bootloader and flashed TWRP 3.1.1. I was on the stock Nougat OTA.
...
Stuck on boot animation, occasionally a very slight vibration.
Does anyone have an idea of what this is?
Click to expand...
Click to collapse
I don't know any custom working with Nougat baseband.
Before custom N you should downgrade it.
Download last MM for your model, unzip, and flash:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to twrp, adv.wipe - everything(except sd card) and flash any custom N you want.
dzidexx said:
I don't know any custom working with Nougat baseband.
Before custom N you should downgrade it.
Click to expand...
Click to collapse
Awesome thanks mate. That looks to have worked.