yesterday, i flash TWRP on my redmi 4 and after that intalling lineage os. but it got stuckked. in bootloop than i wipe data and trying to install stock but it also stuck. now phone is completely dead .
anyway to get it back???
sainiji said:
yesterday, i flash TWRP on my redmi 4 and after that intalling lineage os. but it got stuckked. in bootloop than i wipe data and trying to install stock but it also stuck. now phone is completely dead .
anyway to get it back???
Click to expand...
Click to collapse
Mi boot varutha
Related
I am Using Custom Roms From Last 5 Months. I ve installed cwm recovery in My yu yureka. Recently changed my Custom ROM To CR droid. It was Going smooth and neat. I Got bored of CR droid. Tried To change my ROM to miui Through cwm Got bootloop
Then I have restored my old CR droid ROM through cwm. And then I flashed Twrp 3.0 . and again I tried to flash miui ROM again got bootloop. And then again restored to CR droid which I have backed first. And then downloaded the Resuccurtion remix ROM and flashed through Twrp it booted up. And again I tried flashing miui Through Twrp. Phone started restarting again and again continuously and then went to my recovery tried restoring my old ROM phone booted up and I was using the same ROM. Next morning when I wake up phone rebooting again and again. Went to recovery , tried cleared system / factory reset Phone still rebooting. Made clean wipe flashed new ROM phone still rebooting
Don't know what to do. Then I flashed stock ROM using fastboot mode , flashed successfully phone booted up after completing setup wizard the phone started rebooting Help me to get rid out of this thanx :good:
Sorry for long explanation
I have same problem here after miui 8
waiting for solution
hope someone will solve
I have a similar case my device is in bootloop untill charger is connected.
I had similar(all most same) trouble you mentioned before and my bad luck i still dont have a solution :crying:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....
Whenever I try to flash a custom ROM it will stuck on bootloop
I try pixel experience pie ,pixel experience Oreo, crDroid rom
But as always in every rom it stuck on bootloop
Only stock room works after restoring
Pramod saxena said:
Whenever I try to flash a custom ROM it will stuck on bootloop
I try pixel experience pie ,pixel experience Oreo, crDroid rom
But as always in every rom it stuck on bootloop
Only stock room works after restoring
Click to expand...
Click to collapse
What about some more information?
- Is your bootloader unlocked?
- Are you rooted and if yes how (magisk version)?
- TWRP version?
- What's your actual stock firmware and from which you were coming from?
- Is your data partition encrypted?
- When you say "stuck on bootloop" what does that mean? Is it a bootloop like looping all the time without booting the OS or are you stuck on your bootlogo/bootanimation?
- Any error messages from TWRP?
You'll find the log in cache/recovery/last_log.
Nobody will be able to help you if you don't provide informations i.e. logs.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
What about some more information?
- Is your bootloader unlocked?
- Are you rooted and if yes how (magisk version)?
- TWRP version?
- What's your actual stock firmware and from which you were coming from?
- Is your data partition encrypted?
- When you say "stuck on bootloop" what does that mean? Is it a bootloop like looping all the time without booting the OS or are you stuck on your bootlogo/bootanimation?
- Any error messages from TWRP?
You'll find the log in cache/recovery/last_log.
Nobody will be able to help you if you don't provide informations i.e. logs.
Click to expand...
Click to collapse
★yes my bootloader is unlocked
★Root:- No, I didn't root my phone
★twrp version:- twrp-3.2.3-1-potter.img
★I am on Stock Oreo 8.1 by recovery my stock room after stucking and I am also coming from stock Oreo 8.1 (Sorry properly I didn't understand what u ask)
★yes,my device is encrypted
★it is stuck on that's rom logo, like if I install pixel rom it starts by a circular motion of Google and then stuck on Google logo....
Or when I install crDroid rom then it stuck on crDroid logo
And there is a loading line below the logo
★TWRP error:- Sometimes unmount storage/partition error occurred but when I repair data,cache and system in wipe option it will solve
Pramod saxena said:
★yes my bootloader is unlocked
★Root:- No, I didn't root my phone
★twrp version:- twrp-3.2.3-1-potter.img
★I am on Stock Oreo 8.1 by recovery my stock room after stucking and I am also coming from stock Oreo 8.1 (Sorry properly I didn't understand what u ask)
★yes,my device is encrypted
★it is stuck on that's rom logo, like if I install pixel rom it starts by a circular motion of Google and then stuck on Google logo....
Or when I install crDroid rom then it stuck on crDroid logo
And there is a loading line below the logo
★TWRP error:- Sometimes unmount storage/partition error occurred but when I repair data,cache and system in wipe option it will solve
Click to expand...
Click to collapse
Maybe try to format /data in TWRP to decrypt it. A lot of custom ROMs can't handle encrypted devices.
Post the last_log from cache/recovery when you try to flash a custom ROM.
Sent from my Moto G5 Plus using XDA Labs
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Pramod saxena said:
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Click to expand...
Click to collapse
Wolfcity said:
Maybe try to format /data in TWRP to decrypt it. A lot of custom ROMs can't handle encrypted devices.
Post the last_log from cache/recovery when you try to flash a custom ROM.
Click to expand...
Click to collapse
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Hello, did you find the solution? I'm facing the same problem with the rom crDroid for moto g5 plus.
viclib said:
Hello, did you find the solution? I'm facing the same problem with the rom crDroid for moto g5 plus.
Click to expand...
Click to collapse
The Solution for me was to format data. It is NOT JUST WIPE but to FORMAT.
That removed the encryption and I was able to flash any other rooms again
Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!
Which rom did you have while taking the first backup?
Wipe System, Data, Cache, then reboot the recovery and then restore the backup of System, Data and Boot. Don't restore recovery. See if this works.
Lisatio said:
Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!
Click to expand...
Click to collapse
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.
I finally tried an other Lineage Os Rom from XDA and it finally worked.
But I don't really know why.
The first one I tried to install was in fact a Potato OS... (You can download it from the same page!)
But still, this ROM was for Lavander too, I don't understand why it didn't worked....
Anyway my phone is OK now! Thanks a lot!
DarthJabba9 said:
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.
Click to expand...
Click to collapse
What would happen if I tried to restore my Backup?
Lisatio said:
What would happen if I tried to restore my Backup?
Click to expand...
Click to collapse
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.
DarthJabba9 said:
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.
Click to expand...
Click to collapse
Thanks a lot, I won't try then!
Do I have to Edit my thread title with a [SOLVED] sign?
Lisatio said:
...Do I have to Edit my thread title with a [SOLVED] sign?
Click to expand...
Click to collapse
I think that would be a good thing, otherwise, people will stumble upon it, and keep posting.
Hey!
I installed LineageOs on my Xiaomi Mi A1, everything went okay but when I installed the Gapps, it got stuck on the LineageOs logo. The volume button wasn't working right, yet somehow, I manage to enter TWRP and wipe that OS and restore the backup with the original Android One. But when I boot it, it got stuck on Android logo, unable to enter fastboot, TWRP or hard reset because of the volume button not working.
I don't know what else to do, to be honest...
p.d.: I'm new here, sorry if this is not the right section to ask.
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
royalasif said:
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
Click to expand...
Click to collapse
I chose Android 10 GApps since I installed LineageOS 17. I thought it was the right version.
So TWRP can't be used for stock rom? I didn't know, maybe that's what got me stuck on Android One logo.
Any idea on how to get out from that loop? ?
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
royalasif said:
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
Click to expand...
Click to collapse
Definitely I'll try Pixel Experience! Seems like a good choice. I still need to figure out how to enter Fastboot or TWRP without the volume button.
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
ranjodhricky said:
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
Click to expand...
Click to collapse
Adb cmd won't recognize the device, so I'll have to boot it to EDL mode. Is there any guide here? I don't know how to do it.