Hello. I have a rooted OPO, running 05Q. Last night I finally succumbed to the temptation to flash a ROM. I used the app "CM downloader" to obtain the latest nightly of CM12. Using TWRP, I created a backup, then installed the downloaded ROM. It didn't work; the phone got stuck in what is, I think, called a bootloop. That is, it just kept showing "Updating Android" then going back to a CM animation, over and over.
After letting this go on for quite a while, I powered the phone down and rebooted into Recovery. From there I restored the backup I had created. That seemed to go without a hitch; everything looked as it did before I set out on this adventure. But when I let the screen go dark after 30 seconds of not doing anything, I found that double-tap wouldn't wake it, and neither would pressing the power button. It seemed to be still working, since notifications were coming in, but I couldn't get the screen to light up. So I did a reboot, which worked, but only until the screen went dark again, at which point I had the same problem.
So...I used Titanium to backup all apps and settings, and did a "reset to factory", then restored apps and settings. This seemed to work, but once again I found that once the screen went dark, the only way to wake it up was to reboot. And again, even though the screen was dark, the phone was working. I listened to a podcast while driving to work, even though I couldn't wake the screen up.
Any ideas what the cause of this might be? I did check the Settings to make sure the double tap to sleep and wake were turned on. Everything was as I'd left it. And in any case, even the Power button wouldn't do it.
You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
waterdaan said:
You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Click to expand...
Click to collapse
Thank you, that worked!
Related
Is this the right place to post this?
Inspire 4G Rooted, S-OFF, Clockworked with Bubby's One Click, and attempted to flash CM7.
I can make it past the set up, all the way into the phone. Shortly after, it will just kind of randomly freeze up and go through the boot animation again and then take me to a lock screen. I can unlock it and go back into the phone, but it will almost immediately freeze and go back to the boot animation again.
Flashed 3 times, once on RC2 and twice on RC3, using ROM Manager 3.0.1.0, Clockwork 3.0.0.6, wiping data and cache each time.
Please help!
Did this happen when you were turning on Wifi?
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
wberry85 said:
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
Click to expand...
Click to collapse
Its a known niggle with almost every CM build. It doesn't like wifi on the first boot. Let it come to the launcher screen and then reboot the phone. Things should go smoothly after that.
same thing happened to me. I just rebooted it a few times and problem solved. Had no idea that wifi was the problem though.
Awesome! Flashing now...
This works!!
Thanks again guys...
I just finished flashing SKY onto my phone, and it works, but whenever I put the phone to turn off or reboot, it goes into the powering off animation and finishes, but the soft buttons at the bottom stay lit up and won't turn off. Same if I try to reboot, it stays stuck with the soft buttons lit up and doesn't perform a reboot. I followed all the instructions except flashing a radio and kernel, they're still stock. So how can I make my phone actually turn off?
Sounds like you might have a bad install. I'd get a fresh download of the ROM, check the MD5 on it, then do a full wipe and reinstall. Make sure you're doing exactly as the 4.2F6 OP says to, and don't forget to wipe /system as part of the install prep.
Update your recovery it's usually the cause.
A simple way to fix it is to make a nandroid and restore it instantly.
Ok, the updated recovery did it. Updated my recovery since I realized I had used a outdated link and now it's working fine, rebooting and powering off normally. Thanks
Good evening everyone.
Going to try to be as concise here as possible.
Rooted my phone as per VINCOM's awesome guide here, everything went well.
Phone was functioning normally.
I proceeded to load superuser/ updated binaries etc.
Downloaded rom toolkit/titanium back up and proceeded to freeze certain apps that were considered bloatware.
after about an hour or so, I was on my browser, went to the home screen, but the browser stayed open, yet buzzed as if the command was heard.
did a battery pull, and since that it has stopped at the S logo opening screen.
I cannot get it to go into recovery at this point either. My phone has periodically shown the sticky power button issue with resets and every 2 second vibrations, but it had not done this for some time.
Upon trying to go into recovery (both volume keys held plus power, I seems to start doing the vibrating every two seconds.
At this point I am lost on what to do.
Any advice would be appreciated.
Me[kk]A said:
Good evening everyone.
Going to try to be as concise here as possible.
Rooted my phone as per VINCOM's awesome guide here, everything went well.
Phone was functioning normally.
I proceeded to load superuser/ updated binaries etc.
Downloaded rom toolkit/titanium back up and proceeded to freeze certain apps that were considered bloatware.
after about an hour or so, I was on my browser, went to the home screen, but the browser stayed open, yet buzzed as if the command was heard.
did a battery pull, and since that it has stopped at the S logo opening screen.
I cannot get it to go into recovery at this point either. My phone has periodically shown the sticky power button issue with resets and every 2 second vibrations, but it had not done this for some time.
Upon trying to go into recovery (both volume keys held plus power, I seems to start doing the vibrating every two seconds.
At this point I am lost on what to do.
Any advice would be appreciated.
Click to expand...
Click to collapse
Just an update, flashed stock firmware for ICS 4.04 successfully, managed to get the phone once into recovery, did a factory reset cache wipe twice... everything remains the same. FML
Me[kk]A said:
Just an update, flashed stock firmware for ICS 4.04 successfully, managed to get the phone once into recovery, did a factory reset cache wipe twice... everything remains the same. FML
Click to expand...
Click to collapse
managed to get my phone going.
tried flashing odin again with the stock 4.04 provided by VINCOM.
Things seem back to normal.
Still boggled by what bricked the phone.
Thoughts?
Okay this is the second time this happened. My phone just completely shut down randomly as I was opening a tab in Chrome. I turn it back on, flashes Samsung then the Slimkat screen but won't go past. I put the battery in it, it turns itself back on (vibrates right after I put the battery back in). I can get to recovery and I can get to download mode.
When I had CM11, the phone would keep rebooting. The last time it did this, it had the same problem, so last night I said screw it and went to Slimkat. To fix this issue, I had to go back to a stock rooted rom, then flash recovery, then flash Slimkat, etc. It worked until today. I flashed the build on my phone and that doesn't fix it either.
What is the problem? Seems like my phone is soft bricking itself? I'd rather not go back and configure everything yet again.
Okay I've wiped data, tried to reflash the rom, and now when I get into download mode, the phone just goes black.
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").