My Lenovo A6000 Plus is getting stuck on boot loop and showing other weird behaviors. I factory reset it and cleaned its cache from the recovery screen but that didn't solve the problem. Is there possibility that this is a software problem which would be solved if i flash stock ROM / kernel? If yes then how to do that? The instructions i found online for flashing ROMs on my phone, i found them incomplete for me.
Related
I was recently flashing a rom on my rooted Verizon S5 via Safestrap on one ROM slot. I flashed the rom then downloaded the 0A8 kernel. Upon bootup, the phone was stuck on a boot loop, but I can get into recovery and download mode. I have already tried to factory reset the phone via recovery and I have also tried to put on the stock kernel again. Both were unable to resolve the issue. I have a fulll nandroid backup so wiping anything would not be an issue, but is there any way to solve this problem?
Also, when the phone boots up, it stays on the S5 boot screen and you will hear the boot sound but it will remain at that screen for an infinite amount of time. Can anyone help?
Thanks!
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
sounds like your system is fcucked currenty. should probably boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
Try booting up after that.
e753 said:
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
Click to expand...
Click to collapse
When flashing these ROMs are you wiping properly (system, data, cache, dalvik cache) first? You should try going back to stock, but you'll need to do more than the previous person who replied has said. First you need to wipe data in TWRP, then you need to flash the full factory images, not just the ones mentioned above. You'll find instructions for that in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
I had that problem today. I traced it down to my wifi. Turning off wifi allowed me to boot with no further issues.
1) Boot loop as soon as I got to work.
2) Dirty flashed the ROM
3) Restored backup from 4 days ago.
4) Wiped system and reflashed ROM and gapps. Same issue.
Finally chased it to the wifi. The instant it connected, bootloop. I ran and app called FXR Wifi fixer. Ill see if it bootloops tomorrow at work. No problems on my home wifi after all of this.
e753 said:
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
Click to expand...
Click to collapse
i wouldn't consider this to be strange really. something was not correct in the system partition probably. pretty standard when flashing different ROMs
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
As the title says, i can't to seen successfully boot any android pie/android 10 based rom on max pro m1.
>bootloader already unofficially unlocked.
but during erasing process, i accidentally booted into recovery from where i booted into system , where encryption started again.
>so i booted back to twrp, format data then flashed decrypt.zip
> then flashed havoc 9.0 based rom, gapps then >wipe from twrp itself.
> rom boots fine after boot logo,but after welcome screen, google loading screen comes after which screen goes blank black and finally shutdowns after few minutes.
>tried force shutdown, multiple times, data wipe,format data,decrypt.zip after mountung vendor as well.
Still same issue, just after rom boot logo finished loading, the phone just goes blank black.
what should i do ? Asked many threads,telegram groups, nobody is replying /helping, everyone is just ignoring it.
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
CHGR1999 said:
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
Click to expand...
Click to collapse
my problem is solved by flashing stock pie which was twrp flashable .
akhil17kr said:
my problem is solved by flashing stock pie which was twrp flashable .
Click to expand...
Click to collapse
So you don't use havoc anymore? Or did you first flash stock, update to pie, then flash havoc? I'm stuck too... Won't let me flash havoc, need to get firmware 16 or something.
Try factory reset or wipe data
i got the same issue and still can't not flash any custom rom, the same thing happen to my phone when i flash any custom rom 8 9 or 10, i changed recovery already but it didn't work