Not sure if I'm posting this in the right place feel free to move or delete it if needed.
My question is...
I recently flashed cm 10.2 nightly onto phone. Now the first one I flashed gave me an option to change the reboot button to show an additional menu for reboot options (boot to recovery, reboot, etc). But after flashing that latest nightlies for the past 2 nights I still have the option to select for a reboot menu but nothing shows up. Thought maybe it was just the latest update until I flashed today's/last nights update.
Not a huge issue as I can always hard key into my recovery but it was a nice feature. Just wondering if anyone knows why this may have happend.
Thanks
Sent from CM 10.2 optimized sph-l710
Related
Hi there,
Longtime lurker, first time poster! Before I get into my issue, I would like to let you all know that I did do my due diligence and didn't find a concrete course of action to address this problem.
Here is what I did (as per Cyanogenmod Wiki)
1. I downgraded the phone to an exploitable version of Froyo
2. I rooted the phone
3. I installed Cyanogenmod 6 (because 7 wasn't working)
4. Installed Google apps for the above version.
5. Market and account wasn't working
6. Found CM version 9 beta
7. Installed that - it worked
8. Installed Google Apps ICS version - worked well
9. I finished doing this sometime in the morning, and the phone worked a good four hours before trouble began
10. I got a call, and post call the call manager (or equivalent Android process) stopped responding. I restarted the phone
11. Since then it has been rebooting after loading the home screen.
12. Post this, I searched online
13. One recommendation was to clear data, cache and restore factory setting via recovery.
14. I also formatted SD card and reinstalled CM 9
15. Issue persisted.
16. I tried another mod (Audacity 3) didn't work and has same issue.
Someone suggested I do a SuperWipe and reinstall the mod.
I would love to hear from you guys in terms of what I can do next. I am sure the device hasn't been bricked - I can still access recovery and bootloader.
Thanks in advance!
EDIT: Found the solution. The phone was rebooting because of an in compatible build of Google Apps. Downloaded the right one from Cyanogenmod Wiki, and its golden!
ive had the same and android revolution, just flash a rom like andromadus beta 4. or another rom
Thanks!
I did do that for a bit. I tried A different ROM but liked CM better. Also, I made a mistake with the build of google apps - which was the reason it kept rebooting. Have been using it for a couple of weeks and it works great.
Yes, I know this belongs in the thread for this ROM, but I'm still trying to hit 10 posts without spamming.
Three issues with v3.0 -
1. It wiped my APNs
2. I can enter new APN info but it does not save, even after I hit "Save," so I have no no phone, sms, or data
3. The Home button doesn't work
Any suggestions for fixes, particularly for the APN issue?! Rolling back to 2.7 for now.
Same to me,but only when try to flash a new RIL,otherwise apn is set right.
Flashing new RILS (various version ) got the signal lost,i don't know why.
Sent from my MP711I using xda app-developers app
Bizarrely enough, all problems resolved
Okay, so my APNs suddenly went away in 2.7, I couldn't get the phone to re-read them, and couldn't get it to accept new entries. I confirmed that the apns-conf.xml file was present and that it contained the correct info for my provider.
What the heck, I re-flashed 3.0. Still no APNs, still no home button. So I tried changing one setting after another trying to see if it would trigger a re-read of the APN file. Switching airplane mode on and off didn't do it, but whether by coincidence or not, after locking and then unlocking the phone, suddenly I had four bars AND the home key worked.
So, if you were holding off trying 3.0, give it a shot. VJ says "let it settle" after flashing -- I guess that what he means is it just takes a good long while for the system to get everything up and running.
I had issues with that ROM starting from version 2.7, and with the AOKP as well,
after some usage, the phone will freeze and restart, after that my home button will not work, all of the system configuration would wipe out, the Google play button in the drawer will vanish and so on.....
I think it is got to do with the a2sd script, I've tried using m2sd instead and the problem hasn't happened again...
so if you are experiencing the same problem try this....
Sorry but home button work on every rom wich i used. Issue of apn happen to me when try to flash another ril, i don't know a way to fix, but is a strange situation when flash a fresh rom. Have you performed a full wipe? Or better a full format except fat32?
Sent from my HTC Desire using xda app-developers app
Search did not give any results i guess. Finally got the nexus up and running again / was on CM10 and had neglected to wipe data when flashing the 4.2.2 factory image. It was pretty weird, I think. The phone had sat on the 'X' screen time after time, minutes not counted.. I had at first vol up/ vol down / power and had gotten a red exclamation for some reason. Eventually got into fastboot, I had used the toolkit by mskip / reflashed the 4.2.2 image , made sure to clear data and all works fine. When flashing a custom rom it sticks on the google unlocked screen. Why? What is the problem? How does this fix itself or going about it to get it fixed? ....... Again, if this is a stupid question and you have easily found the answer by all means pass along the right keyword. If this is not a stupid question, you don't think, and are cool about helping me out, by all means, please do so.
Edit . I had flashed stock then custom rom on another device with only the usual, i guess, load time. The best advice search forums gave me was , just wait'.
http://forum.xda-developers.com/showthread.php?p=38127432
Flashed cm-10.1-20130217-NIGHTLY and got stuck on the "Google" logo on reboot. Booted to recovery and installed the Feb 16 build and all is good. Hopefully the next nightly works well.
From the CM thread.
Hello.
Try to flash the 2013.02.17 nightly AND some 4.2.2 kernel.
I tried with LeanKernel 6.0exp1 and it works
There are reports with working flashed 2013.02.17 with Franco's Kernel latest too.
vfmmeo said:
hello.
Try to flash the 2013.02.17 nightly and some 4.2.2 kernel.
I tried with leankernel 6.0exp1 and it works
there are reports with working flashed 2013.02.17 with franco's kernel latest too.
Click to expand...
Click to collapse
perfect work.
Merry Christmas to all!
JLM, have posted similar on your other site.
Having a problem with the BrokenPop 5.0.2 on my L900 (Sprint Note2)
I can't seem to dial out with this rom. I get popup saying 'Unfortunately, Dialer has stop"
Are others seeing this problem? Is this an rom issue or a setup issue on my end?
I don't expect a daily driver from an early alpha of this rom and do expect issues but I would hope that I can at least make phone calls, after all, the Note 2's primary function is a phone
What I have done so far.
DL and installed rom twice. Both DL check via MD5 OK
Using Philz 6.07.9 recovery
1. Backup internal sdcard to pc
2. Factory reset / Install new rom option
3. Wipe/format internal sdcard
4. Reboot recovery (selected yes to restore root notification)
5. Install rom
6. Boot rom
7. Boot into recovery
8. Flash Gapps
9. Did minor setup of things like Wifi, Google Login, Play Store, DL ES File Manager.
10. Try to make phone call using dialer (phone icon) and get 'Unfortunately, Dialer has stop"
11. DL another free dialer from Play Store.. same error message.
I'm open to suggestions on how to get this to work.
I do like what I see from my little tour around this rom, but not being able to make calls is a major issue for me even for an alpha release. For now I have fallen back to my trusty Community Rom 4.4.2 which has been rock solid for me.
Thanks
bump.... a few people have viewed this posting .. anyone else having this problem? I have since try to install once again.. had some limited success with dialer, but then problem returns. even made a nandroid of when it was working.. still my favorite early lollypop rom for the l900
I installed Broken5.0.2, ran it for 24, and found it seemed to be one of the least reliable functioning loli roms for L900. I personally am preferring the LiquidSmooth 12-23 nightly. The LS rom has overcome the wifi/screen off hotboot bug, the keyboard bug, but still needs the manual GPS fix. Right now it offers hands down the most functioning options at this particular time and the phone is semi reliable??? Lol its doesnt FC but its buggy.
My two cents ... Cheers!
I've tried LiquidSmooth 12-23 nightly also.. one thing I had issues with was I have a OTG usb drive and did not find a way to unmount it. Did you find that function anywhere in LS?.. Other issue I have is no XPOSE support right now.. and I'm not a fan of the AOSP messaging pgms. Lots of things I don't like about TW .. but they make a nice messaging pgm
I did see a semi-workaround where you click on the carrier setting and it kinda resets the capability to make calls.. kinda hokey.. but it seems to work.. Lolllypop is still very early.. and I guess these are the growing pains for being alpha testers. Hopefully over time it will get more mature. Back on 4.4.2 for now.. everything works.. the thing is huge.. over 2gb nandroids using high compression.. but hey, everything works.. Thanks for responding.
Hi,
I was on the paranoid 4.4.4 rom on my I9300, everything worked fine.
I did the last update with paranoid 5.1.1 but it didn't worked well, i have multiple error and Google service won't work anymore.
The thing is, i can't do anything at all, like restore my last backup because i lost the root access with the update.
I can't load in recovery mode, i tried the HOME+VOLUME DOWN (or up) + POWER, it won't work.
I can't fine the debug mode on this version, so i really don't know how i can at least restore my last backup to go back to the 4.4.4 version.
Any help is appreciated, thaks for your time.
Root doesn't ship with any 5.x build of paranoid android. To reset you need to boot into recovery and restore your backup or flash a different ROM.
You don't need root access for that.
It sounds like you installed an incompatible gapps....
Thanks for your reply,
I managed to boot in recovery, using a method i found on the web, i pull the battery then hold the combination keys when i put it back, and it load in recovery just fine.
I think i couldn't install the proper gapps because i was in clockwork recovery, i installed the latest TWRP, but i still can't manage to install the latest paranoid rom prpoperly.
here's what i did so far:
- wipe all/ factory reset , install Paranoid5.1.1 + Gapps 5.1 mini => paranoid load but Black screen once it's loaded with the message "Android.phone interrupted" (gross traduction) popping every 2 sec, it disapear if i put the phone on airplane mode => make me think the Google service can't connect.
- Restore my last 4.4.4 backup then => wipe cache/dalvik=>install Paranoid 5.1.1 + gapps => same as the previous problem, but this time i have my old app and i can call and receive sms.
My guess so far is a problem with the Google service who can't synchronize, the Gapps i try to use are the pa_gapps-modular-pico-5.1-20150315-signed.zip
Any guess ?
Yeah. The problem is you are using old gapps. Use banks gapps
I had trouble with a clean install of PA 5.1 + Gapps on my S3 (i9300) and similar issues to yours, not sure why but I found that if I used th full fat "Stock" 5.1 Gapps the phone was fine and has been for a day or 2 now, the pico/mini/full seemed to be problematic (at least for me). Also moved to Philz Recovery using the "Rashr" app as my old CWM kept throwing an error of status 6 on any Gapps I downloaded... Must admit though that once stable PA Lollipop runs well on the S3 and battery seems better over the past couple of days too...