Related
So today CM 7.2 RC1 was released for all supported devices. Here are some links
http://www.cyanogenmod.com/blog/cyan...rc1-is-upon-us
http://get.cm/?device=speedy
So I wiped my device clean and flashed the zip, and after booting up successfully (shows the screen that says "Touch the Android to begin") it just reboots on its own, and the process repeats. I double checked that the md5 was clean, and I tried wiping and flashing several times with the same results. Is this happening to anyone else?
Same for me here.
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
THEsunnypiglets said:
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
Click to expand...
Click to collapse
Usually you could but had risk of error, with me, it just made the reboots happen at 5 minutes intervals instead of 10.
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
cloverdale said:
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
Click to expand...
Click to collapse
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
sparksco said:
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
Click to expand...
Click to collapse
Audio is working fine for me.
cloverdale said:
Audio is working fine for me.
Click to expand...
Click to collapse
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
sparksco said:
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
Click to expand...
Click to collapse
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
cloverdale said:
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
Click to expand...
Click to collapse
Agreed. I have tried just about every kernel I can get my hands on. The ones that boot have no audio, the rest simply don't boot or bootloop or reboot after a moment or two (haven't tried the default kernel and turning GPS off/on yet).
I fail to understand how they let 7.2 out for the Shift when it isn't booting up reliably for the majority of users. At what point did it become safe to say it is a Release Candidate? I'm beginning to think it more a Return To Your Previous ROM Candidate.
[edit]
I just flashed back the default kernel with GPS disabled and it booted without issue. Enabled GPS after boot and it works without reboot. Rebooting phone with GPS enabled still results in bootlooping, tho.
So, here's my proposed solution to those still having problems, want audio, and can live without GPS being enabled all the time (since no audio also means no call audio, this should be the majority of you):
1. Flash the 7.2 zip.
2. Immediately flash pershoot kernel (the ones that boot without audio, like v14 port).
3. Boot and immediately disable GPS.
4. Reboot into recovery and reflash the 7.2 zip. (NO NEED TO WIPE ANYTHING BUT DALVIK CACHE, for those who are already setup on 7.2 or coming from 7.1)
5. Boot normally.
NOTES:
A. If you attempt to boot or reboot with GPS enabled, you will get caught in a bootloop again. Simply follow the steps above again to turn it back off.
B. You CAN turn GPS on after boot and use it without issue. But you MUST disable before powering off or rebooting, else you'll have to do the above steps again.
C. Even if you can live without audio, I advise AGAINST using the pershoot ports on 7.2 for daily use. Something is causing that kernel to drain battery at about 3-5 times the normal rate (may have to do with the audio issue), regardless of CPU speed.
Hope this helps until this gets officially fixed somehow.
[/edit]
I have this rather annoying problem with my OPO: When I'm on WiFi and go out of range and get within range of another WiFi (eg leaving from home in the morning and getting on the train where there's also WiFi) my OPO will not connect.
I've tried switching WiFi off and back on, tried forgetting network and connecting again but the network just displays as "Saved". Only thing that works is a reboot. Funny thing is that it actually detects open WiFi's and displays the question mark in the notification bar.
I've read that themes can cause WiFi problems so I haven't changed that. I'm using the Apex launcher with no visual changes.
I've rooted my phone but left the bootloader locked.
Any advice?
I'm rooted with the TWRP custom recovery installed. I had the same thing happen to me. If you toggle airplane mode on/off, it will reconnect. But, as for a solution, my fix was to restore a previous TWRP backup of my phone. I also had heard that the problem could be coming from a theme. What themes have you used? I bought the Flux theme and have been using its style and fonts. I was running the stock CM11s when this happend just a few days after getting my OPO. I would try a factory reset first. If that does not work, there is a thread in the OPO forums about flashing a factory image and getting back to 100% stock.
I have switched to the CM11 nightlies as of a couple of days ago. I will probably refrain from messing around with the theme packs for now.
kevinga said:
If you toggle airplane mode on/off, it will reconnect...
Click to expand...
Click to collapse
Works for me too
kevinga said:
What themes have you used?
Click to expand...
Click to collapse
None as I've read reports about themes causing WiFi problems.
kevinga said:
I would try a factory reset first.
Click to expand...
Click to collapse
Will probably unlock the bootloader. Then a factory reset should be taken care of I guess...
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you taken the OTA update yet?
kevinga said:
Have you taken the OTA update yet?
Click to expand...
Click to collapse
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
kroogar said:
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
Click to expand...
Click to collapse
I really hate to hear that you are still having the wifi issue. One would think that if you flashed all partitions with a factory image that it would solve the problem. You might want to have a look at this thread. This guy was unsuccessful in fixing his efs and bluetooth problems until he flashed Color OS and then went back to CM. Have a read: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Keep us posted.
kevinga said:
Keep us posted.
Click to expand...
Click to collapse
Will have a look at the ColorOS thread. But I think I'll give Mahdi another go first to see what that brings me.
Thanks for the link.
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you been able to fix your wifi problem?
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
kroogar said:
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
Click to expand...
Click to collapse
Although is sounds drastic I think it would be worth trying.
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
GoTexan20 said:
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Thanks for sharing. I think there are two things that can produce a major restore/fix to a phone - a nandroid restore and a major rom update. I hope it fixes yours. The nandroid restore is what saved mine.
Click to expand...
Click to collapse
kevinga said:
Although is sounds drastic I think it would be worth trying.
Click to expand...
Click to collapse
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
GoTexan20 said:
kevinga said:
I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Could it be Smart WiFi Toggler?
Click to expand...
Click to collapse
kroogar said:
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
Click to expand...
Click to collapse
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
If your WiFi 2.4 or 5GHZ?
Sent from my A0001 using Tapatalk
kevinga said:
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
Click to expand...
Click to collapse
Eh... nopes - should I have...?
fr4c said:
If your WiFi 2.4 or 5GHZ?
Click to expand...
Click to collapse
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
kroogar said:
Eh... nopes - should I have...?
Click to expand...
Click to collapse
Yes. I would recommend you consider doing that. If it works then I would flash a fresh Cm11s rom, not a nandroid backup. Flash the Color OS and do a full check of the Wifi.
Sent from my A0001 using XDA Free mobile app
kroogar said:
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
Click to expand...
Click to collapse
I was having the same issue, but here's what I did and it seems to have resolved my issue.
1) Updated firmware on my ASUS AC68 router
2) Boot into recovery mode (volume down+power), wipe cache and media, then factory wipe
3) When setting up phone, did not apply CM theme on the options after logging into CM account.
It seems like WiFi might drop when you get to homescreen, just reboot phone and Wifi should reconnect. Make sure to go into your WiFi settings and remove any networks that was saved, and re-add.
Still not ideal (since it seems like themes might be killing WiFi for some users), so hopefully a new OTA update will solve this problem.
After updating my Nexus to 5.0, the camera worked fine for a couple of weeks. However, starting from a few days ago, when I open my camera app, it won't function at all; instead, all I get is the screen shown in the screenshot.
I'm afraid that's all I can really explain about this problem, as I can't think of any other relevant details.
Thanks in advance.
Beplexor said:
After updating my Nexus to 5.0, the camera worked fine for a couple of weeks. However, starting from a few days ago, when I open my camera app, it won't function at all; instead, all I get is the screen shown in the screenshot.
I'm afraid that's all I can really explain about this problem, as I can't think of any other relevant details.
Thanks in advance.
Click to expand...
Click to collapse
Have you tried rebooting your device ?
MrFishiz said:
Have you tried rebooting your device ?
Click to expand...
Click to collapse
Of course, I tried it twice.
Guess what though? After reading your post, I decided to try it again just for the sake of it, and it works now...Thanks for the solution haha?
Beplexor said:
Of course, I tried it twice.
Guess what though? After reading your post, I decided to try it again just for the sake of it, and it works now...Thanks for the solution haha?
Click to expand...
Click to collapse
Sometimes I get this annoying message when I try to access the camera, it says " Cannot connect to the camera " so what I usually do is reboot my device and then everything works again aha.
Glad it sorted itself out.
Same problem. Rebooted 4 times. Cleared cache. Still no camera
I have the same issue, tried the following
Reboot
Clear camera data
Reboot
Clear device cache
Reboot in safe mode
Reboot
None of that worked.
Tempted to try a new ROM and go from stock 5.0.0... See if that helps
I'm on stock rooted 5.0 and I have gotten this issue multiple times. Multiple reboots fix it temporarily but I can't figure out what actually triggers the issue.
I rarely use the flashlight pulldown, and haven't at all during the last few reboot cycles that this has still happened.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
dcoaster said:
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
Click to expand...
Click to collapse
That's strange. I rooted several times with CrashXXL's method (currently unrooted) and never had any problems with anything. What launcher are you using? It could be that or some app you have installed. Have you installed Xposed and/or Gravity Box? If so, could be some module interfering with something.
Maybe you should consider returning to stock unrooted and doing the procedure all over again.
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
dcoaster said:
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
Click to expand...
Click to collapse
Yes, just use RSD to flash the stock su6-7.2 firmware. Here is the link to the firmware file:
http://motofirmware.center/files/category/18-droid-maxx/
If you want to save all your data and apps then flash the 1FF firmware file.
If you want to start over clean then flash the CFC file.