I've a Moto Z Play, I've been using /e/ OS for a few months and it worked quite well. Today the phone froze while I was using it. I rebooted and since then it's stuck on /e/ logo (= boot loop).
I was not updating system, I was just using phone
I can enter in TWRP recovery, use adb shell, etc..
I already did cache and dalvik cache wipe, and rebooted without SIM nor SDcard and it didn't work
I managed to dump boot log (
Code:
adb shell cat /sys/fs/pstore/console-ramoops > ./boot-loop-kernel-log.txt
) but I can't understand what is failing
I uploaded my logs here: drive.google.com/open?id=1ekTRe_dWSLKq8TmLqa26uae0SOE9uccy , sorry I can't post the link because I'm a new user.. but url is complete. There are 3 files:
Number 1: I let the phone reboot several times, the log is 150 seconds.
Log number 2: I switched to recovery as soon as I detected the phone rebooted, so log is only 30 seconds. The phone makes a small vibrations at every reboot. However the screen always shows the /e/ OS logo.
Log number 3: again I let the phone reboot several times.
Perhaps some hardware might be failing.. perhaps the camera or the GPS.. On this forum I saw a post of somebody stuck in loop because of screen temperature calibration fail, he deleted a file (that doesn't exist on my device) and solved the problem; but my problem is that I can't understand boot log, I can't understand what is going wrong. :crying:
[SOLVED] I solved the issue
I solved the issue. I went to TWRP and did a simple wipe. I didn’t want to do this because I was going to loose all my apps and configs, and actually I lost them, but at least device is usable again.
Related
After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
SvenHee said:
After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
Click to expand...
Click to collapse
Usualy for the fastboot output that you got it means you need to reinstall the drivers.
Sent from my SM-G850F
Reinstalling drivers if for windows is it not?
Until now I found that linux is super easy in installing adb and fastboot, and previously, during instalation of the phone, installing adb and fastboot was all I did.
Assuming that the 10.1 ROM still is present on your SD card try to reinstall it dirty. Just wipe cache and dalvik cache before rebooting into the system. Only the rom.
Got it working again with just a factory reset, but off course, all data and settings were gone.
I did try to put (partial) backups back but that broke the system again.
It is a shame that all my texts are gone, but I'll get over it.
Thanks for the help guys!
Hey everyone,
as you can read I have huge problems with my m8 :crying:
About my Device:
Bootloader Unlocked & S-ON
HBOOT: 3.16.0.000
RADIO: 1.16.2133165.UA10G
Telekom HTC One M8
ViperOneM8 1.7.0
Android Version 4.4.2
Fastboot getvar-all output:
hxtp://i.imgsafe.org/1cbd28a.png (thx spam protection)
It started some days ago with Swiftkey (Keyboard App) complaining about it can't safe it's language module (I ignored it).
After that WhatsApp completely lost it's chat history and tried to restore it which worked fine.
Then Telegram bugged around with chats in general, received and sent messages didn't appear in the app anymore.
The next App was Googles Playstore, Error 492 no App updates possible.
After a few (hot)restarts everything went to almost normal but from that point on I needed to restart my phone frequently (additionally the WIFI stopped working sometimes), I noticed that I couldn't create new files with ES explorer anymore in /emulated/0.
Sometimes I could but most of the time it simply said "An Error occured".
Today I restarted the m8 again, and all my Apps were gone (vanished from Homescreen & "All Apps").
I tried to stick to Venoms FAQ:
0. I cant access/write to my internal SDCARD
Run this command from shell
Code:
Code:
adb shell su restorecon -FR /data/media/0
Click to expand...
Click to collapse
Which resulted in to following Error:
/sbin/sh su not found
I tried to boot into recovery (TWRP) but it stuck with saying "Entering recovery" from the Bootloader. Nothing happend, so I killed it (Holding Power and Vol+) back to the Bootloader.
I tried flashing different versions of TWRP (twrp-2.8.7.0-m8,twrp-2.8.6.1-m8,twrp-2.7.0.1-m8) but everytime I got the same result ("Entering recovery" and a reboot after 30 secs.)
So I flashed recovery-clockwork-6.0.4.8-m8 which finally let me enter recovery again ...
After entering it I wiped dalvik cache and cache and rebooted the Phone, with the same issues decribed above. (sporadically read only sdcard0, Messenger buggy etc.)
My homescreen is still empty but at least my Apps are back in the overview, Phone is still unusable though.
I have absolutely no idea what to do.
Hi everyone of you savior angels,
after rebooting form TWRP (3.2.1-0) following today's lineageos ota update, my phone boots: 1st/2 boot logo sequence, asks me once (out of two) for the pin code, 2/2 boot logo sequence and then after some time , 30 sec maybe, the screen blacks out and it restart into recovery mode. There, it now says "RescueParty" once I have entered the password.
I have tried to let it cool, to wipe Dalvik and Cache, and Factory Reset. Still the same. I can not find the downloaded files form the update.
I am at work now and do not have access to my usb cable.
Any thing you could recommend?
cheers
Got it!
pepite_ said:
Hi everyone of you savior angels,
after rebooting form TWRP (3.2.1-0) following today's lineageos ota update, my phone boots: 1st/2 boot logo sequence, asks me once (out of two) for the pin code, 2/2 boot logo sequence and then after some time , 30 sec maybe, the screen blacks out and it restart into recovery mode. There, it now says "RescueParty" once I have entered the password.
I have tried to let it cool, to wipe Dalvik and Cache, and Factory Reset. Still the same. I can not find the downloaded files form the update.
I am at work now and do not have access to my usb cable.
Any thing you could recommend?
cheers
Click to expand...
Click to collapse
Ok so I tried a few things.
While in recovery I could access the internal storage through my computer. First I copied all the pictures and good stuff. Then I sent to the phone a freshly downloaded latest version of LineageOS (released today). Unplugged the brick, installed the system through TWRP, rebooted. Same crap.
Thing I noticed is that if plugged on the computer or on the power adaptor, the phone would not reboot into recovery, but would stay in the second loop sequence, seemingly for ever? At least for 30 min+
Then I did the same with the previous LineageOS (last week's). Same troubles.
Right. This starts to sound like a clean wipe. So I did that. For the science, I installed the newest LineageOS version (the one that initiated the problem it seemed). Then latest openGapps. And bam! It worked!
Need to reinstall all the crap now.
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.
tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.
Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse
What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.
@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.
Had to do a factory reset, and all was good. Using LSposed with Magisk and reinstalled several mondules. Upon reboot, the screen hangs at "Pixel is starting." So I rebooted into safe mode, knowing the Magisk modules would be disabled, but the same thing happens, even in safe mode. Booted again. I can access all my settings, and adb works fine. But I'm clueless as to what I should do, even with adb and settings access.
Will appreciate any help. Everything is backed up, I'm just trying to avoid the nuisance of having to factory reset again and all that entails.
Thanks.
You can try Official Google Android Flash Tool and uncheck the wipe data option (and don't force flash all partitions, either, which will also wipe), and don't forget to uncheck the option to re-lock the bootloader.
That official site has solved many weird issues where even manually flashing the full factory image hasn't solved the problem. Good luck, let us know if that's what you do and how it goes.
my old go-to for boot issues was last_kmsg. I recentlky found abou about boot-chart, which logs what happens during boot, and may log an error for you. You will have to run this in recovery if yopu are in a non-booting state
To enable it:
Code:
mkdir -p /data/bootchart;
touch /data/bootchart/enabled;
try a reboot, which fails. Reboot to recovery and retrieve the logs
init/grab-bootchart.sh - platform/system/core - Git at Google
I havent had to use it "in anger" yet, but it will be my tool of choice.