Can not install any rom... Battery issue or Other?. Z00LD (ZE550KL) - Zenfone 2 Laser Q&A, Help & Troubleshooting

Z00LD, ZE550KL
Using since May 2016. Still getting 3.5 hours SOT. Tested many ROM.
Last ROM was AOSP Extended 6.7, Pie. Everything was working well.
Today, I wanted to root my device. So I installed Magisk 20.3 zip via TWRP latest recovery (3.2.3 may be). After installing that zip it was started bootloop. I didn't create any backup. So I made a clean flash the same ROM and GApps(full).
Here, the problem has started. The GApps is not installing properly. Before 100% done, it reboots and bootloop starts.
I used adb and fastboot to go back stock. Everything was done perfectly. But still, boot loops.
Can not find any reason, is it battery problem or others?
Please Help!!!

kowshikkhan.rcs said:
Z00LD, ZE550KL
Using since May 2016. Still getting 3.5 hours SOT. Tested many ROM.
Last ROM was AOSP Extended 6.7, Pie. Everything was working well.
Today, I wanted to root my device. So I installed Magisk 20.3 zip via TWRP latest recovery (3.2.3 may be). After installing that zip it was started bootloop. I didn't create any backup. So I made a clean flash the same ROM and GApps(full).
Here, the problem has started. The GApps is not installing properly. Before 100% done, it reboots and bootloop starts.
I used adb and fastboot to go back stock. Everything was done perfectly. But still, boot loops.
Can not find any reason, is it battery problem or others?
Please Help!!!
Click to expand...
Click to collapse
When phone reboots after stock image flash where you pluged in? if while pluged in booting perfectly and without pluged in boot looping that is kind of battery issue!!

Related

Mako always booting into recovery

Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?

zuk z1 bootloop when flashing any rom

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....

[Problem][OP2][CM14] Suddenly phone started loop reboot and not possiblŠµ flash rom

OP2 Š hone worked fine for over year. Today suddenly began reboot. Was installed CM14.
1. I tried clean flash CM14 from recovery - flashing 50% and stopped - tried several times.
2. I tried flash unbrick method 2 with QCOMDownloadTool - OxygenOS 3.0.2 from:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
phone flashed and booted, but I started installing apps, phone again started bootloops.
3. I tried flash unbrick old method with QCOMDownloadTool - H2OS 1.1.0 - phone worked but periodically reboots.
If I try load to phone large file on cable, phone rebooted in Android and in Recovery.
Problems with ROM?
some questions..
1. why the hell you are flashing a CM14 build, when cyanogenmod is a legacy project? did you try lineage OS?
2. which recovery are you using? I assume you are on latest TWRP
3. which error does the recovery output, when flashing suddenly stops at 50%?

A20 stuck in SANSUNG logo screen

After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
That's really strange.
What is your firmware date?
physwizz said:
That's really strange.
What is your firmware date?
Click to expand...
Click to collapse
I used this Firmware: XFA-A205FXXU2ASFA-20190803073130
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Imyou said:
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Click to expand...
Click to collapse
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
GSIs are here
https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Not sure about 3.0.2-0
I use this one
https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
Gsi* - I recommend HavocOs
Very stable , everything works and no bugs so far.
Been using it as my daily driver for like 2 weeks!
And as for twrp you can retry with the one you have but I don't know if the problem will happen again.
I'm sorry I have lost the link that I found my twrp
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
MorneDJ said:
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
Click to expand...
Click to collapse
Touch screen not working.
I would take it back under warranty.

[T560] All Android 7 ROMs not working, stuck on bootloop

Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated
phayme said:
Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated
Click to expand...
Click to collapse
Did you flash magisk or supersu before fist boot?
I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.
phayme said:
I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.
Click to expand...
Click to collapse
Try to flash rom without gaaps or magisk only base rom
gitanillo87 said:
Try to flash rom without gaaps or magisk only base rom
Click to expand...
Click to collapse
Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms.
@gitanillo87
Try to flash rom without gaaps or magisk only base rom [\QUOTE]
I did, still not working unfortunately
@magicmckinney Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms. [\QUOTE]
yeah all these roms are for my device (T560)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Flash my stock rom,with TPRW and later flash any nougat rom
First of all flash clean stock rom using Odin
-Install TWRP
-Factory reset
-Install CM13 and gapps (root optional)
-Wait to boot and pass all the steps in the initial setup
-When tablet completely booted reboot to TWRP
-Install any Android 7 rom ang gapps without factory reset
-Reboot
-Cross fingers and eventually it will boot!!!

Categories

Resources