i'm having a boot loop after flashing any custom rom I tried all the roms available and all the recoveries too without any success although there was some roms working before that but now there aren't any rom working please help I couldn't figure out the reason
h.boushi1987 said:
i'm having a boot loop after flashing any custom rom I tried all the roms available and all the recoveries too without any success although there was some roms working before that but now there aren't any rom working please help I couldn't figure out the reason
Click to expand...
Click to collapse
download stock fastboot rom and flash it
Try to do all, what said in instruction, and It must boot
thank you all for your help i discovered the reason that i should flash vmeta.img and all roms worked for me
h.boushi1987 said:
thank you all for your help i discovered the reason that i should flash vmeta.img and all roms worked for me
Click to expand...
Click to collapse
Flash the vbmeta and your Problem is gone.
I had the Same Problem.
LM209 said:
Flash the vbmeta and your Problem is gone.
I had the Same Problem.
Click to expand...
Click to collapse
thanks alot that the wright solution for the problem
Related
my phone is not booting after switching rom from pa lollipop experience beta9 to pac rc3. it gets stuck at bootanimation. tried both philz and twrp to wipe and flash another rom. cm11, pac, pa, mokee nothing boots now. can anybody help me out? i'll be very thankful.
Flash Fastboot ROM for Redmi 1S...there is a loads of tuts available on net how to !
Shahi00 said:
Flash Fastboot ROM for Redmi 1S...there is a loads of tuts available on net how to !
Click to expand...
Click to collapse
yea, this should do. the process is a bit lengthy though. anyway, thanks for the help man.
GreyBlood said:
my phone is not booting after switching rom from pa lollipop experience beta9 to pac rc3. it gets stuck at bootanimation. tried both philz and twrp to wipe and flash another rom. cm11, pac, pa, mokee nothing boots now. can anybody help me out? i'll be very thankful.
Click to expand...
Click to collapse
here .This is solution for no boot problem .all aosp roms work fine
eswarvf said:
here .This is solution for no boot problem .all aosp roms work fine
Click to expand...
Click to collapse
I did the same. Downloaded the fastboot rom and flashed it via MiFlash. Couldn't flash it using cmd at first because there's no driver of redmi 1s for 32-bit os. Then tried MiFlash and it worked. I had to format all though, not formatting the storage didn't work out. It got fixed the day i posted this. Anyway, thanks for giving a solution (even if i already fixed my phone).
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
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
dg89 said:
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
Click to expand...
Click to collapse
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
tiklmypikl said:
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
Click to expand...
Click to collapse
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
dg89 said:
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
Click to expand...
Click to collapse
What verison of TWRP are you on?
tiklmypikl said:
What verison of TWRP are you on?
Click to expand...
Click to collapse
right now it is on v2.8.7.0 and i tried to install the new version but it's not working
My Mi Max is unlocked, rooted and runs LinageOS 14.1.
I have been wanting to try out MIUI again and downloaded the recovery Rom from the MIUI Forum.
I have been using nijel8's TWRP but tried others.
Installing the ROM works with no problems but afterwards I get the message that no OS is installed and when I try to boot nothing happens even after 60 Minutes.
Am I missing something?
Thanks in advance
entermaxx said:
My Mi Max is unlocked, rooted and runs LinageOS 14.1.
I have been wanting to try out MIUI again and downloaded the recovery Rom from the MIUI Forum.
I have been using nijel8's TWRP but tried others.
Installing the ROM works with no problems but afterwards I get the message that no OS is installed and when I try to boot nothing happens even after 60 Minutes.
Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
reboot to twrp and flash the rom again this time it should boot fine. I'll also facing this issues several times when I'm on miui rom only flash it again should solve the problem.
Zasnizas said:
reboot to twrp and flash the rom again this time it should boot fine. I'll also facing this issues several times when I'm on miui rom only flash it again should solve the problem.
Click to expand...
Click to collapse
Thank you. But unfortunatly is does not make a differnece. Still doesnt boot. I have also tried every combination of 'wipe' with this Flash.
The ROM doesnt even boot. The Phone doest post, but it does not try to boot as in the boot Animation does not show.
entermaxx said:
Thank you. But unfortunatly is does not make a differnece. Still doesnt boot. I have also tried every combination of 'wipe' with this Flash.
The ROM doesnt even boot. The Phone doest post, but it does not try to boot as in the boot Animation does not show.
Click to expand...
Click to collapse
Flash lazy_flasherhttps://androidfilehost.com/?fid=457095661767111293 after flashing stock ROM, it should boot after that
Sent from my Mi Max Prime using Tapatalk
T.kum1993 said:
Flash lazy_flasher after flashing stock ROM, it should boot after that
Sent from my Mi Max Prime using Tapatalk
Click to expand...
Click to collapse
Thank you. That was it. I have read about that file bevore but all the versions i came across did not work.
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.