I flashed and installed latest 4.4.2 nightly build by Pac and most of the apps seem to be working fine except whatsapp. After installing whatsapp on newly loaded ROM, it fails at the verification step. I have also tried taking App+Data backup through Titanium from my stock rom where Whatsapp is getting verified and then working without any issues. After restoring the app/ app+data/ data only on the newly loaded custom ROM Whatsapp skips verification step but I am not able to receive any new messages. Later on, I faced the same problem when I flashed to Parandroid's latest 4.4.2 build. Any solution/fix to this issue?
Fixed
intensegamer1 said:
I flashed and installed latest 4.4.2 nightly build by Pac and most of the apps seem to be working fine except whatsapp. After installing whatsapp on newly loaded ROM, it fails at the verification step. I have also tried taking App+Data backup through Titanium from my stock rom where Whatsapp is getting verified and then working without any issues. After restoring the app/ app+data/ data only on the newly loaded custom ROM Whatsapp skips verification step but I am not able to receive any new messages. Later on, I faced the same problem when I flashed to Parandroid's latest 4.4.2 build. Any solution/fix to this issue?
Click to expand...
Click to collapse
Never mind guys! Got it working, apparently I needed to verify my mobile no. on Hangouts (default sms app) first.
Related
Good day xda,
My problem is that, after I installed a Custom ROM (specifically the lastest of CM11 nightly), I'm having a lot of errors like "Unfortunately, LG Keyboard AOSP bla bla bla has stop", "Unfortunately, phone has stopped", "Unfortunately, com.googleapps. bla bla bla has stopped" and my back button does not work anymore. I also tried their stable release and I got a lot of errors too, back button not working and keyboard not working so I cannot type a message. Of course I also installed gapps. I tried their stable release because I thought it's "stable" and now I am back at the stock rom.
What should I do?
Bad google apps download 4.4 g apps
Sent from my LG-E975 using xda app-developers app
Sorin90 said:
Bad google apps download 4.4 g apps
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
Thanks man. Will try this. Feedback later.
Just want a feedback. I already installed a custom rom cm-10.2.0 with gapps for Android 4.3 and it works fine. What I want is to have my apps and data and pictures be in my new custom roms. I tried to flashed the "update.zip" provided in TB but only the apps are restored and the data on it didn't restore. Same goes to pictures, contacts and messages.
Guys, please let me know if:
1. Is it possible to moved or installed to a new custom rom and restore ALL your data from your previous rom including, pictures, contacts, messaging data, the apps and the data?
2. Is it possible to update the custom rom?
Please help me. I'm a newbie in android.
Help me please.
Ronald07 said:
Just want a feedback. I already installed a custom rom cm-10.2.0 with gapps for Android 4.3 and it works fine. What I want is to have my apps and data and pictures be in my new custom roms. I tried to flashed the "update.zip" provided in TB but only the apps are restored and the data on it didn't restore. Same goes to pictures, contacts and messages.
Guys, please let me know if:
1. Is it possible to moved or installed to a new custom rom and restore ALL your data from your previous rom including, pictures, contacts, messaging data, the apps and the data?
2. Is it possible to update the custom rom?
Please help me. I'm a newbie in android.
Click to expand...
Click to collapse
Hey bro ,yes you can have old data but not the apps but they carry space on your phone ....you can later explore them through apps like ES File Explorer which can be found in play store....you can have data which is present in your internal memory storage but none of your apps after flashing as it is fresh ROM
all you need to do is unchecked your internal storage while flashing the ROM
PS if you find lots of errors in the ROM ..try different ROM ..Stock is best if you ask me personally ..you can get the stock ROM in forums
Try and let me know
Hello guys I just wanna inform you that there is something happening with the CM 11 4.4+ based ROMS
they deleted my Baseband and IMEI
I restored through KIES and got my Baseband and IMEI back but this thing keeps happening and I cannot figure out why?
It's painful procedure because I did this more then 10 times
First I had to Reflash everything through KIES which makes my phone as DEFAULT
then I had to ROOT and install the ROOTED Original 4.3 then I had to install Clockwork Mod with MOBILE ODIN in order for me to install different ROMS
after that I do FULL WIPE ALWAYS
Cache / Dalvik / Data / System even Internal Storage
I installed CM11 whatever ROM u choose:
http://forum.xda-developers.com/showthread.php?t=2453586 (tried this one no success)
Tried this one:
http://forum.xda-developers.com/showthread.php?t=2565259 again the same thing Bad baseband
Also this one:
http://forum.xda-developers.com/showthread.php?t=2493905 OMNI Rom (first installed older version everything was fine but when It updated to the latest OMNI I got the same Unknown Baseband and no DATA whatsoever)
so what the heck is going on? Please help me?
recovery might be the issue
I just had this problem yesterday. You wouldn't happen to be using TWRP recovery would you? I found that if I was using TWRP and Kit Kat AOKP I would have no service and my APN list would be empty. If I used Philz Custom recovery or CWM it would work fine.
I tried going downloading the newest 2.6.3.1 version of TWRP and it made my phone unable to boot. I had to flash another recovery via Odin in order to get back into my phone.
Just a thought.
I've had this issue as well and for some reason the latest nightlies don't play nice with my phone and recovery I'm using the latest official twrp for t0lte. Not t0ltetmo. I recently tried fishing the last multi window and I lost my microphone use. I have since reverted to a homemade build from January.. It seems to be the only thing that works.
Sent from my SGH-T889
Guys I used both CWM and TWRP both the latest versions... and this thing happen during both tries... I don't think it's the Recovery!
Help!
I'm on CM11 (latest nightlies) and there's a lot of bug here
so I wondered If I can flash CM10.1.3 (stable) via TWRP Recovery while i'm on CM11 is possible?
(Flash CM10.1 over CM11)
Thanks in advance
mrgwin said:
Help!
I'm on CM11 (latest nightlies) and there's a lot of bug here
so I wondered If I can flash CM10.1.3 (stable) via TWRP Recovery while i'm on CM11 is possible?
(Flash CM10.1 over CM11)
Thanks in advance
Click to expand...
Click to collapse
Possible Yes, advisable No.
You're likely to come across loads of app crashes or other problems if you flash CM10 over CM11. It's best to backup apps with Titanium backup Pro, and your SMS etc with SMS Backup. Makes sure contacts are synced to google as well.
If you're having problems with nightlies flash the SNAPSHOT version, That is the most stable out of CM11.
Which issues are you having, I am on CM11 and not had any real issues?
TheATHEiST said:
Possible Yes, advisable No.
You're likely to come across loads of app crashes or other problems if you flash CM10 over CM11. It's best to backup apps with Titanium backup Pro, and your SMS etc with SMS Backup. Makes sure contacts are synced to google as well.
If you're having problems with nightlies flash the SNAPSHOT version, That is the most stable out of CM11.
Which issues are you having, I am on CM11 and not had any real issues?
Click to expand...
Click to collapse
What If I wipe my data and reinstall all the apps?
P.s. I'm having the Camera issue, often showed up " Can't connect to the camera" Which didn't happen on Touchwiz Rom
mrgwin said:
What If I wipe my data and reinstall all the apps?
P.s. I'm having the Camera issue, often showed up " Can't connect to the camera" Which didn't happen on Touchwiz Rom
Click to expand...
Click to collapse
Yes, that will be fine. What I was referring to that is not advisable is a non-clean flash (keeping data).
I have had the Camera issue on various nightlies and needed reboot. There is a app in store that enables you to fix camera when you get this error which is better then rebooting device.
As far as I remember I didnt have the camera issue on CM11 Snapshot.
TheATHEiST said:
Yes, that will be fine. What I was referring to that is not advisable is a non-clean flash (keeping data).
I have had the Camera issue on various nightlies and needed reboot. There is a app in store that enables you to fix camera when you get this error which is better then rebooting device.
As far as I remember I didnt have the camera issue on CM11 Snapshot.
Click to expand...
Click to collapse
Thanks! But what android version of CM10.1 is ?
I heard that it's 4.2.2
is it okay to flash while i'm on 4.4.2? (No IMEI lost issue or hard brick?)
Thanks again
mrgwin said:
Thanks! But what android version of CM10.1 is ?
I heard that it's 4.2.2
is it okay to flash while i'm on 4.4.2? (No IMEI lost issue or hard brick?)
Thanks again
Click to expand...
Click to collapse
The no IMEI/brick etc are caused (afaik) by n00bs flashing wrong device rom or corrupt archives or flashing is interrupted etc.
Just wipe device and flash new rom in recovery, You should be fine.
Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)
Copy important files to computer. Factory reset. Set it up as new device.
ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?
jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova
Hi All
I've been having such trouble flashing custom ROMs on my Samsung Galaxy Tab Pro 10.1 WiFi SM-T520. I was sucessfully able to flash TWRP 2.8.7 via odin on the device. However, I've tried several ROMs (CM11, 12, 12.1, Unofficial Liquidsmooth) each with their own issues but whichever is able to be flashed always ends up with random startup reboots. I cannot for the life of me figure out why or what is the reason. If I flash back to stock Samsung firmware, everything is fine, works perfectly but no custom firmware.
CM12.1 out right hangs during install in TWRP. The only way I was able to install it is via Cyanogen Recovery which I flashed via odin then attempted to install the rom but even still ends up in random reboots during first bootup and a few times during optimizing apps.
Just a note, I have been doing full wipes (cache, data, system) prior to flashing the ROMs. I don't know what else to do. CM12.1 works really great and smooth but cannot use it because of these random reboots. Can anyone shed some light so I can have a successful flash?
ALSO, I would like to note one suspicion I have and that is my tablet came preloaded with KOT49H.T520UEUAOD1 (T520UEUAOD1_T520XARAOD1_XAR) Samsung Firmware Build. I wonder if perhaps something with this latest build shipped is causing my troubles but am not sure.
Thanks in advanced!
Try booting back to recovery immediatly after new rom flash and perform factory reset and it ahould fix it in most cases.
Sent from my LG-D800 using XDA Free mobile app
I tried the factory reset suggestion but unfortunately did not make a difference.
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Mossey said:
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Click to expand...
Click to collapse
No backup/restores involved for me. Are you still experiencing this issue with CM12.1 or was restoring the backup the problem in your situation?
I am wondering if perhaps the bootloader version that is based off of the latest official stock ROM that was released in April/May 2015 has something to do with my issues. Is there anyone that was on the latest stock Samsung ROM that has been able to successfully flash a custom ROM and use it in a stable way (short of minor CM bugs)?