[Solved] Sometimes stuck on bootscreen can't even powerdown! LOS 14.1 - HTC One A9

Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated

Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that

Related

[Solved] try this if you're stuck at the boot loading screen

While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:

One plus One stuck in a reboot loop after cyanogen nightly update

So I haven't had any luck with my Oneplus One lately . I had rooted the phone and was running the CyanogenMod nightlies for a while, but recently for some reason when I updated it for Nov. 25 I have been suck in a reboot loop where the phone boots up and it starts updating apps, but then it continuously does this cycle of rebooting and updating apps. I have tried to enter recovery mode to try and remedy the situation as I have twrp, but for some reason it doesn't boot to recovery when I press down the power and vol down buttons. I have tried to adb to try and reboot into recovery mode but I haven't been able to get it to work. I'd really appreciate some help on this as I have no idea what to do at this point.
I should also mention that I would like to see if it is possible to recover my data as I foolishly did not make a back up.
Thanks in advance.
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
I installed the newest version of nightlies CM 13.0 2015 11/30 along with gapps 6.0, but now my phone just boots up and optimizes apps but when it restarts after that it just goes to a black screen.
I know I can wipe everything through twrp and install cm 13.0 probably eliminating the issues I am having, but I'm reluctant to do so as I would like to retrieve my sms messages. I have taken my photos off my phone so I have that.
If any one can advise me on if I can restore my sms from the twrp back up I have made then I'll wipe my phone and do a clean install.
Thanks in advance
i have the exact same problem. would be nice to have it fixed and working without losing all the data.
So I decided to go ahead and wipe my system as I have all of the data I could get out of my phone on my pc now. I get get cyanogen working nicely, until I go into twrp and try to restore the data files I had backed up. This goes well until the reboot then a message pops up saying something isn't working (too fast too read). I then get a blank screen.
Now I still have the same problem of how to put the data I had saved when I used twrp back on to my phone. I believe something in my data is corrupt which is why this is happening, but I'm not sure. Is there just a way to extract say the sms from the data I have saved, that's really all I need at this point. The backups made by twrp are in a format .WIN that I have never seen before and I would appreciate the help if someone can advise me what to do from here.
CM13.0 struck in Reboot loop
When I was browsing and doing some multitasking stuff..noticed that phone was lagging a bit .So i thought to reboot so that it would come out of that...But it completely struck in reboot loop forever.
please help me out of this issue.
Thanks in advance
Novius vi said:
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
Click to expand...
Click to collapse
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
vindows18 said:
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
Click to expand...
Click to collapse
Are you pressing the Vol down button and power button. Also I unscrewed the back of the phone to unhook the battery cable then I pressed the buttons. I found also, through trial and error on my phone, that you can hold down the buttons for too long so you have to watch and make sure on that. I found that you should hold the 2 button combo through the oneplus one boot logo and you'll see the lights dim then you let the buttons go and its worked so far at least on my phone.

[2016]Random Reboots on my ONE. Please help.

Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").

[Resolved] SuperSU Update Then Stuck on CM logo

All was well until this morning I got a notification that SuperSU needed updating. I said yes, and it gave me two options: 'Normal' and TWRP, or something similar. I went for normal. After a few moments a message appeared saying that the update was successful and that I should reboot my phone. I clicked reboot and now the device gets to the animated CyanogenMod logo and stays there forever.
I booted into recovery (by holding the volume down button at the same time as the power button), and from the main TWRP screen have backed up the phone (and copied the contents to an external device) and tried clearing the cache. This has not helped.
Can anyone advise what I could try next please?
UPDATE: Fixed it . I found a copy of UPDATE-SuperSU-v2.65-20151226141550.zip in the Download folder of the phone's internal storage, installed that using TWRP and rebooted the device. It has started fine, with the only strange thing being that SuperSU no longer appears in the Android Apps Drawer. Any idea why this might be? Is this likely to be a problem? I'm not sure I fully understand what SuperSU really does.

Wokeup to my phone stuck in a bootloop... [SOLVED]

UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!

Categories

Resources