Hi,
I bought a Moto G 5g Plus and instantly unlocked the bootloader to install /e/OS. I did everything exactly like the guide and everything worked, except that it randomly froze for some seconds and then restarted. Because of that, I tried installing LOS for microg but ran into the same issue. After that I wanted to install stock firmware with Motorola's own RSD software, but it couldn't set the phone to fast boot, so I tried to do it with the batch file included in the firmware zip just to see that recovery mode and fastboot now both show the no command error. After restarting, somehow /e/OS started (no clue how or why) and that's the point where I'm stuck.
I can't reinstall because of the recovery thing, and my OS is unusable because of the crashes. I would guess it's some background service that's crashing it, but I'm not an expert. Did someone have this issue in the past and can help me with this?
Thanks!
Related
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
LG G4 815
S/N=511
tl;dr: Bootloop, did a lot of fiddling, finally ended up with installing a "somewhat" working setup in this order (Everything installed via TWRP, TWRP was via fastboot):
1. TWRP (SteadfasterX's) /O version
2. V29a Firmware, keep TWRP
3. Disable big cores kernel (From above V29a firmware thread, first reply by kessaras)
4. LineageOS 15.1
5. Mindthegapps
Having troubles getting it to boot past the LG bootscreen (Once it boots completely, it seems to work fine).
---------------------------------------------------
So yesterday I was browsing my phone when it suddenly restarted. It had done this before multiple times and it always has gotten back to working just fine. Only this time was different, after the LG bootscreen went away, it appeared again. I'm aware of the bootloop issues the device has and was hoping I would get lucky but apparently not.
Configuration when bootloop happened:
-LineageOS14.1
-Stock kernel
-TWRP (3.1.1?, cant remember exact version it was 3+ anyway).
I noticed I could still access TWRP (Although it did crash few times back to LG bootscreen), so I first tried wiping caches etc (No luck). Anyway, I was quite close to just giving up at this point, but decided to fiddle around with the thing. I found out about the issue with one of the "big cores" heating too much and that it was possible to disable those. I decided to give it a try, and while I was at it, wanted to try out the newer LOS15.1. Downloaded titan kernel (no big cores), installed and went onto install LOS. First issue, my TWRP wasn't new enough to install the LOS15.1 (Error code 7). Did some searching and found out about "unofficial TWRP" installations that allowed me to install LOS15.1 (Used SteadfasterX's TWRP, O/ version).
After this I got a few kernel crashes (Green screen with a lot of text, different error codes each time), all searches pointed to my own error during installing stuff (I had older firmware while LOS required newer), and I believe these crashes had nothing to do with the actual bootloop issue. To fix this I went and grabbed the V29a firmware and the big cores disabled kernel which is in the first reply of that v29a thread. After this I managed to install LOS15.1+Mindthegapps (Also rooted it) just fine and it booted up past the LG bootscreen. I grabbed Kernel Auditor to check if the big cores had been disabled and I could only see 4 cores (max 1,44ghz).
Now the phone seems to run fine when I actually get it booted up. I tried restarting the phone and I was stuck in the loop again (Did multiple restarts). I tried booting into recovery (I got into the "factory reset" dialogs just fine which takes you to TWRP) but after that instead of TWRP it went back to the LG bootscreen (Tried again like 3 times). After this I plugged in my phone to my computer and got into TWRP first try(I wonder if there's an actual reason for this, I know it could be just pure luck). Then I went onto the reboot options in TWRP and booted into system. First time I got past the bootscreen but it crashed when asking for my SIM pin code. Second time after booting the same way, I got it working just fine and now the phone seems to be working happily again.
Is there anything I can do myself to trace this issue and improve the chances of booting up the phone or am I forced to just rely on luck and hope it boots completely without crashes (In the case of a crash/I need to restart the phone)?
I was trying to flash vanilla AOSP GSI and everything was going as expected.
After that, I flashed "disable force encryption" and the fingerprint gestures files among with magisk and pico gapps and the phone started rebooting after a single freeze of 2 or 3 seconds right after the initial boot.
Actually I made several tries with different combinations trying to figure out what was causing that behaviour and I noticed that it used to happen patching "fstab.qcom" file in "/vendor/etc" path as stated in this guide, always keeping a backup of the original "fstab.qcom".
At some point my device started rebooting even after restoring the old "fstab.qcom" so I flashed the stock rom via fastboot but it didn't solve the problem, then I also tried to flash in edl mode (enabled with "fastboot oem edl") but no way, the phone keeps rebooting without letting me finish even the initial setup.
I can access fastboot, edl and recovery. I can also flash TWRP but I can't turn off the phone.
I don't know what else to do, please help me
Sorry for me being a big noob and for my unclear english.
Hi, is there anyone who has ever encountered with such issue? It just randomly restarting. I've done a MSMTool Unbrick Method but no avail, it booted but still randomly restarting. I suspect there is a hardware malfunction.
List of issues that I encounter :
1. Random reboot, a lot
2. Blinking screen on and off when boot animation shown
3. Always fail to do system update, locally and OTA
4. Google play store, gboard, oneplus launcher keeps crashing
5. ???
Will update the list once I remember and encounter a new one.
I've tried multiple method but still no sign of good news. I've tried wiping data & cache using default recovery, all in one tool and lastly MSMTool. Pls help!
Anyone?
Now, even MSM Tool cannot detect my device.
At first, my PC detected my phone as Qualcomm HS-USB Diagnostic 900e, something along that line. And then I found this tutorial to convert that into QDLoader 9008. But when I clicked enum, my MSM Tool didn't detect anything.
Few days ago my device start to restart by itself and then bootloop.
Normally I got bootloops in other phones (HTC) coz of MY fault always - like flashing wrong firmware or wrong version of boot.img but just like this bootloops is quite strange.
Maybe send it back - warranty if your bootloader is still closed etc.
Tapatalk via OnePlus 7T
I am really sad that my device still keeps restarting. I've countlessly tried to reflash the software using whatever tools exist. I've noticed something though, when playing youtube video, the video sometimes breaks (blur, I'll attach the ss later) and after several seconds it became normal again.
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.