Database Users

will not log into google account

after flashing evervolv rom the second time, and the flashing GAPPS, it tells me it cant establish a reliable connection to the server, however, i had it all working yesterday morning. does anyone know what to do?

Dunno. I've flashed Evervolv a few times with no problems other than the known features that ain't working yet.
^ Shift Faced

when i flash a rom that has gapps already installed, everything works, however on CM7 and evervolv, the ones that i have to flash GAPPS myself, it wont work

nbunn said:
when i flash a rom that has gapps already installed, everything works, however on CM7 and evervolv, the ones that i have to flash GAPPS myself, it wont work
Click to expand...
Click to collapse
You may be flashing the wrong GAPPS then.
^ Shift Faced

jesusice said:
You may be flashing the wrong GAPPS then.
^ Shift Faced
Click to expand...
Click to collapse
Its the same GAPPS ive flashed the past 100 times

nbunn said:
Its the same GAPPS ive flashed the past 100 times
Click to expand...
Click to collapse
And it never works. At least redownload it and try that. If not that maybe one of us can make you a new flashable with minimal apps, similiar to the tiny gapps packages that several mdpi roms carry with them.
Sent from my PG06100

nbunn said:
Its the same GAPPS ive flashed the past 100 times
Click to expand...
Click to collapse
And you said everytime you have to flash GAPPS yourself it doesn't work. And no one else is having that problem. Therefore, you are doing something wrong.
Remember: Think horses. Not zebras.
^ Shift Faced

jesusice said:
And you said everytime you have to flash GAPPS yourself it doesn't work. And no one else is having that problem. Therefore, you are doing something wrong.
Remember: Think horses. Not zebras.
^ Shift Faced
Click to expand...
Click to collapse
Umm, the first times I flashed it it worked perfectly, so I don't know how it could be my fault considering I have done it the same every time. I mean I don't know how much I could do wrong by installing a zip file from recovery.
Smoothtaste, that souds great, ill re download the rom and GAPPS both when I get home, then ill get back on here
Sent from my PG06100 using XDA App

jesusice said:
And you said everytime you have to flash GAPPS yourself it doesn't work. And no one else is having that problem. Therefore, you are doing something wrong.
Remember: Think horses. Not zebras.
^ Shift Faced
Click to expand...
Click to collapse
since you suppose 'tis something im doing, could you supply me with a step by step guide?w

nbunn said:
since you suppose 'tis something im doing, could you supply me with a step by step guide?w
Click to expand...
Click to collapse
Sorry, BrandoKC is the man you're looking for there. He's awesome at step by step guides. I take it you tried redownloading GAPPS again?
^ Shift Faced

I have no solution for you, but want one! I've been getting the same problem all day today. I reflashed cm7 then GAPPS and couldn't log into google. It is the same GAPPS and cm7 that I flashed before with success. The GAPPS also worked with evervolv.
I went back to the saved evervolv rom and had to reauth to my google account for some reason. However, I STILL couldn't log in!
I had to eventually go all the way back to my stock backup in order to get access again. (it didn't ask, was already there)

germancarsrock said:
I have no solution for you, but want one! I've been getting the same problem all day today. I reflashed cm7 then GAPPS and couldn't log into google. It is the same GAPPS and cm7 that I flashed before with success. The GAPPS also worked with evervolv.
I went back to the saved evervolv rom and had to reauth to my google account for some reason. However, I STILL couldn't log in!
I had to eventually go all the way back to my stock backup in order to get access again. (it didn't ask, was already there)
Click to expand...
Click to collapse
This is what i did, and it worked! i cant guarantee it, but hey if it works then yay! if you have downloaded the roms and GAPPS on your computer, delete them, delete ALL traces of CM7 and also GAPPS or Evervolv if thats what you are using. Also, delete ALL traces of GAPPS and the roms on your phone/sdcard. Then, redownload a new rom and a new GAPPS.. then of course get them onto your sd card. then boot into recovery, make sure your using CWM 3!! then wipe data, wipe the cache, and also wipe the dalvik cache Andvanced>wipe dalvik cache. once its all wiped, flash the rom. STAY IN RECOVERY, and flash GAPPS without ever booting, flash it right after the rom installation is complete. then, reboot, enter your info and hope it works. PLEASE let me know how this works out, im eager to help you.!!!
Did this help? Hit the Thanks button!

[Q] How to update paranoid android through GooManager

Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!

Go read the first post of the paranoid android rom under android original development. Don't flash things until you read the instructions. Cache is wiped by the rom, and you need gapps with a new install.
Sent from my Nexus 7 using xda app-developers app

delonicdevil said:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Click to expand...
Click to collapse
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].

mvmacd said:
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
Click to expand...
Click to collapse
and one more thing, flash a new kernel ONLY after the first reboot.

Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
thanks alot!

Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
OH..I didn't knew it. Thanks!

I am not getting on how to do that
Hi,
Can any one post link to forum?
I am using paranoid android and in goomanager its showing new update available..!
after downloading zip what to do next?
If any one can put screenshot or list step it would be much helpful..
Thanks in advance...
Balaji_NEXUS said:
OH..I didn't knew it. Thanks!
Click to expand...
Click to collapse

Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This actually makes no difference, aside from making the process more time consuming. The few and far between anecdotes that led to this practice are a cum hoc ergo propter hoc fallacy. Without a doubt, it does not hurt anything, but it also yields no real benefit over flashing in the same recovery session.

Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format

Wilks3y said:
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Click to expand...
Click to collapse
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus

Pirateghost said:
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks

Wilks3y said:
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Click to expand...
Click to collapse
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus

Pirateghost said:
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?

Wilks3y said:
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Click to expand...
Click to collapse
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus

Pirateghost said:
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok great.
Appreciate that

[Q][HELP]Compiled CM10.2 for official unsupported device, but cannot boot up.

I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!

lackyking said:
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
Click to expand...
Click to collapse
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.

simms22 said:
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
Click to expand...
Click to collapse
I tried, but also stopped on the first screen of manufacture logo.

lackyking said:
I tried, but also stopped on the first screen of manufacture logo.
Click to expand...
Click to collapse
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?

simms22 said:
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
Click to expand...
Click to collapse
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.

lackyking said:
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
Click to expand...
Click to collapse
youre not the only one that the latest cm code isnt booting up on.. http://forum.xda-developers.com/showthread.php?t=2435980

[Request] Stock G4 H815 FW ZIP

Howdi Folks,
Anybody fancy cooking a TWRP flashable ROM for stock LG G4 from Source... Kinda buggered mine, cant change the DPI back... LG Keyboard crashes along with a load of other apps xd....

fkofilee said:
Howdi Folks,
Anybody fancy cooking a TWRP flashable ROM for stock LG G4 from Source... Kinda buggered mine, cant change the DPI back... LG Keyboard crashes along with a load of other apps xd....
Click to expand...
Click to collapse
Have you tried changing it back over ADB? Or maybe while in recovery?

hendusoone said:
Have you tried changing it back over ADB? Or maybe while in recovery?
Click to expand...
Click to collapse
Unfortunately the device has been fact reset by accident, however the DPI remains as is, USB Debugging isnt available
Trying to go through TWRP, but i cant get it to boot into recovery

fkofilee said:
Unfortunately the device has been fact reset by accident, however the DPI remains as is, USB Debugging isnt available
Trying to go through TWRP, but i cant get it to boot into recovery
Click to expand...
Click to collapse
Ooh, that's rough. I got into the stock recovery by doing this:
http://forum.xda-developers.com/g4/help/how-boot-stock-recovery-t3123751
barcodelinux said:
1. Power off
2. Press and hold the Vol - and Power button until the LG boot screen appears.
3. Release the Power button ONLY. Do not release the Vol - button.
4. After 1 second, press and hold the power button again. You should see the white recovery screen.
Use the Vol+/- to navigate and Power to select.
Click to expand...
Click to collapse
That might get you into TWRP.

hendusoone said:
Ooh, that's rough. I got into the stock recovery by doing this:
http://forum.xda-developers.com/g4/help/how-boot-stock-recovery-t3123751That might get you into TWRP.
Click to expand...
Click to collapse
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop

fkofilee said:
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop
Click to expand...
Click to collapse
Huh, /system should be remountable as rw. The command should be something like this:
adb shell
mount -o remount,rw /system
Once you do that, you should be able to adb pull your build.prop, edit it, then adb push the fixed version.

fkofilee said:
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop
Click to expand...
Click to collapse
I got system to mount rw by going into TWRP with it connected via usb doing
adb shell
mount /system/
you should now be able to write to system

Nope... Win 8.1 and 7 both having issues. Can I ask a favour, can someone create me a Flashable Build.prop?

fkofilee said:
Nope... Win 8.1 and 7 both having issues. Can I ask a favour, can someone create me a Flashable Build.prop?
Click to expand...
Click to collapse
Here u go

Dude you are lege!!!!

fkofilee said:
Dude you are lege!!!!
Click to expand...
Click to collapse
Opps, use this. Other was for 560DPI

Arh it didnt work, i think it was the first zip that i flash that i created myself, Think it might have broken the Firmware xd
I have a working recovery so its not a complete loss, Ill just wait until the release the appropriate firmware files or a custom ROM ;p
Unless you have any other ideas ... But beyond that, think there isnt much else I can do

fkofilee said:
Arh it didnt work, i think it was the first zip that i flash that i created myself, Think it might have broken the Firmware xd
I have a working recovery so its not a complete loss, Ill just wait until the release the appropriate firmware files or a custom ROM ;p
Unless you have any other ideas ... But beyond that, think there isnt much else I can do
Click to expand...
Click to collapse
I can make an slim rom from the system i have available, should run. Hopefully .

DocRambone said:
I can make an slim rom from the system i have available, should run. Hopefully .
Click to expand...
Click to collapse
Are you sure sure sure? , If pos that would be awesome. Slim would be great

fkofilee said:
Are you sure sure sure? , If pos that would be awesome. Slim would be great
Click to expand...
Click to collapse
It have to wait until tomorrow tho.
Did you check the TWRP backup you made?
There should be an system.image , approx 4 GB in size. Can you restore that?

DocRambone said:
It have to wait until tomorrow tho.
Did you check the TWRP backup you made?
There should be an system.image , approx 4 GB in size. Can you restore that?
Click to expand...
Click to collapse
What... Is... this... Backup.... Thing....?
No sadly i didnt do one before changing the DPI in the build prop. To be fair I was at work so too many things going on... Normally I do
Tomorrow is awesome, If you want to that is
I have my note 4, Works a treat. For the mean time im not so bother about it. I can get the ROM on via MTP through recovery so not really an issue
Thanks for the help.

Can't get rid of the Unfortunately Google Play Services has stopped notification, Play Store isn't working anymore, tried "everything" (removing updates, removing Google account, downloading fresh Play and Services, etc.(no factory reset yet though) (factory reset done and now in bootloop mode)) so a flashable system zip would be awesome! :good:
Solved :good:

How to get back my stock keyboard?

Yes i know i made a really stupid decision and huge mistake. I tried to install an update to my kayboard application and it installee it but it keeps force closing. Is there any way to get my stock keyboard back? I dont want to flash my stock image and go trough that process all over again so is there any way?
Thank you in advance

Currently i am using gboard but i really like my stock touchwiz keyboard

Ragazzza said:
Yes i know i made a really stupid decision and huge mistake. I tried to install an update to my kayboard application and it installee it but it keeps force closing. Is there any way to get my stock keyboard back? I dont want to flash my stock image and go trough that process all over again so is there any way?
Thank you in advance
Click to expand...
Click to collapse
Which Android version? I can share it later.

#Henkate said:
Which Android version? I can share it later.
Click to expand...
Click to collapse
Wow really? Thank you man , and what is the process of installing it? And thanks again i really appreciate it

Ragazzza said:
Wow really? Thank you man , and what is the process of installing it? And thanks again i really appreciate it
Click to expand...
Click to collapse
I have uploaded stock Samsung keyboard (Marshmallow) here: https://www.androidfilehost.com/?fid=817550096634741640 . Let me know if you can install it as normal.
If you cant and you are not rooted, let me know.

#Henkate said:
I have uploaded stock Samsung keyboard (Marshmallow) here: https://www.androidfilehost.com/?fid=817550096634741640 . Let me know if you can install it as normal.
If you cant and you are not rooted, let me know.
Click to expand...
Click to collapse
I installed it as normal apk, but it keeps force closing, yes i have root, what can i do now?
I even tried putting it in system/app/keyboard folder and putting right permissions but i still get force close :crying:

Ragazzza said:
I installed it as normal apk, but it keeps force closing, yes i have root, what can i do now?
I even tried putting it in system/app/keyboard folder and putting right permissions but i still get force close :crying:
Click to expand...
Click to collapse
Go to system/app/app/SamsungIMEv3_SYSTEMUID_XT9/ and remove the .apk. Then put the apk you have downloaded in that folder and set correct permissions ( take a look at other apk permission for example). Then go to recovery, wipe cache & dalvik cache and then reboot.
Let me know if you still have problems.

#Henkate said:
Go to system/app/app/SamsungIMEv3_SYSTEMUID_XT9/ and remove the .apk. Then put the apk you have downloaded in that folder and set correct permissions ( take a look at other apk permission for example). Then go to recovery, wipe cache & dalvik cache and then reboot.
Let me know if you still have problems.
Click to expand...
Click to collapse
Ok i`ll try that, but i forgot to mention that i deleted arm folder for this apk, could that cause problems like this?

Ragazzza said:
Ok i`ll try that, but i forgot to mention that i deleted arm folder for this apk, could that cause problems like this?
Click to expand...
Click to collapse
Yeah it could be.
I have made a flashable zip containing the whole folder.
Here it is: https://www.androidfilehost.com/?fid=745425885120703393 .
Go to TWRP, mount /system and then flash this zip. Then wipe cache & dalvik-cache and reboot.
I made the flashable zip quick, hopefully you wont have issues lol.

#Henkate said:
Yeah it could be.
I have made a flashable zip containing the whole folder.
Here it is: https://www.androidfilehost.com/?fid=745425885120703393 .
Go to TWRP, mount /system and then flash this zip. Then wipe cache & dalvik-cache and reboot.
I made the flashable zip quick, hopefully you wont have issues lol.
Click to expand...
Click to collapse
WORKING LIKE A ****ING CHARM
you saved me from using stupid Google keyboard, thank you very much! thank you for your effort i really appreciate that
Thank you once again really nice zip, everything went trough smoothly!

Here is the ss, all working fine after going trough every feature

Please, can U answer me: I do not have phone with me right now, cuz it is friends phone, i did installed above Stock Nougat 7.1.1 Rom which name is Odyssey Nougat Rom on J5 2016 FN. Now, my friend like that Rom but he doesn't like Samsung Keyboard port from N8... He need keyboard like it was on Stock Rom or one which looks like Xperia Phonepad keyboard. I tried everything, installed Xperia apk keyboard, but nothing works. Keyboard shows on System/Language and Keyboard settings but can not be activated.... That is shorter story Any help would be really appreciated. Thank U very much. Just in case, ill post this post on some other treads or/and on separate thread as well.

I finally downloaded the .apk for my Samsung J5 2016 (later a whole folder, because I realised that it was removed; TWPR closes ) but I can't install it Paidverts.apk that I've installed the same way (not from Play store) works...
What (else) can I do? Thanks for your help.