Related
Hello XDA Dev. I, Azeem, come to you guys with a problem and I need you all's help on solving it. Here's the story.
I was previously on Cyanogenmod 10.1.3 Stable for my phone and decided to try out the new 9-28 nightly of CM 10.2. However, when installing the rom, I rebooted in to recovery after installing it, gapps 4.3, and ajk 4.9 AOSP, but it got stuck at the Samsung logo and I could not enter recovery mode anymore nor could I boot to the homescreen. Knowing using odin to go back to stock would fix the issue, I did just that, and booted to the homescreen. Btw, I odined back to ICS 4.0.4 since I couldn't find an Odin-able tar file for Jellybean UCMD8 (if you know of any, please tell and link it to me). Anyway, I went and installed Mobile Odin to my phone and the N.E.A.K kernel ( http://forum.xda-developers.com/showthread.php?t=1614150 ) for the ICS stock ROM, booted into recovery, wiped data, cache, and dalvik cacke, installed Cyanogenmod 10.2 nightly, gapps 4.2, went to advanced, and clicked reboot into recovery.
Next thing I knew, guess what? It was back to being stuck on the damn samsung logo and I couldn't boot into recovery, yet again! I went and though why not give it another try, so I redid all the procedures I had done prior, but this time flashed the 10.1.3 stable, AND IT HAPPENED AGAIN! I was like wtf! That leads me to the question. Is there anything I can do to prevent this from happening again? I really like cyanogenmod and would love to go back, but I don't want to repeat all of this a 4th time. Thanks for your help in advance!
EDIT: Nevermind. I got UCMD8 Cooked to work, but I am scared to flash 10.1.3/10.2 because I don't want to have to deal with doing all that I did in OP again. However, I really want CM 10.1.3/10.2 back. A dilema.
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
creepyncrawly said:
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
Click to expand...
Click to collapse
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
azeem40 said:
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
Click to expand...
Click to collapse
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
votinh said:
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
Click to expand...
Click to collapse
I fixed the issue by doing the OP things and just restoring nandroid backup.
Dear colleagues,
I'm facing a very frequent problem with flickering/rolling screen after unlocking on my P7510 Table (Europe version).
I just upgraded for the first time from original Samsung ROM directly to "[KK4.4]Omni ROM". I'm running the latest CWM 6..... There is no flickering/rolling on CWM screen. There is no problem with the Omni rom, everything works fine (Wifi, ...).
However after switching the screen Off/On flickering/rolling appears what makes table unusable.
I spent hours reading post regarding this issue but found nothing useless.
Please help.
For those that fall in the same troubles I'm posting a step by step guide how to fix this problem
- boot into downloading mode
- flash stock rom (P7510XWMPE_P7510OXXMPB_XEZ) using Odin1.85 (PDA option)
- flash CWM (ClockworkMod_Recovery_v5.5.0.4_P75xx.tar) in the same way
- reboot (stock ROM boots up) and attach tablet to computer through USB
- copy A1 kernel(A1-p4-1.9-3G-cm.zip), SU package(UPDATE-SuperSU-v1.85.zip), CM ROM (cm-10.2-20131028-DiamondROM-p4wifi.zip) and GAPPS(gapps-jb-20130813-signed-4.3.zip) to android root directory
- reboot table into CWM
- install software from SD card in following order: A1 kernel, SU package, CM ROM, GAPPS
- reboot (CM boots up)
- install ROM manager from PlayStore and update CWM (currently 6.0.3...)
There was one additional thing. When I was trying to install CM ROM an error ocured (getprop ...). So I had to manually edit updated-script file and remove first line (assert ...). Then CM ROM was installed with no problem.
Same Issue
Hi,
i have the same issue here. Tried with OmniRom and with Nameless Rom. Both boot up okay but after screen lock and unlock the screen is scrambled.
Your solution is to install a CM10.2 Rom (which is Jelly Bean). Is there also a solution for KitKat?
Currently i tried omni-4.4.4-20140620-p4wifi-HOMEMADE.zip and nameless-4.4.4-20141019-p4wifi-HOMEMADE.zip. Flashed the bootloader from http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41 . Any recommondations to work around the lock/unlock issue?
car_42 said:
Hi,
i have the same issue here. Tried with OmniRom and with Nameless Rom. Both boot up okay but after screen lock and unlock the screen is scrambled.
Your solution is to install a CM10.2 Rom (which is Jelly Bean). Is there also a solution for KitKat?
Currently i tried omni-4.4.4-20140620-p4wifi-HOMEMADE.zip and nameless-4.4.4-20141019-p4wifi-HOMEMADE.zip. Flashed the bootloader from http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41 . Any recommondations to work around the lock/unlock issue?
Click to expand...
Click to collapse
I don't have the same issue but I am not sure if it's because I am using Nova Launcher. Anyway, you can try the following configuration and see if this problem goes away (copied from http://forum.xda-developers.com/showthread.php?t=2716016):
Go to developer settings:
Activate "Force GPU rendering"
Active "Disable HW-overlays"
I like this KK rom better than the CM10.1 JB Rom.
Hi dookie23,
thanks for your reply. I just tried it, and it did not work.
My issue is not, that the content in the video memory is wrong, but the video memory is not rendered correctly to the screen. To get an impression, have a look at http://forum.xda-developers.com/showthread.php?t=1680738
Obviously the graphic HW is not initialized correctly when resuming... I have no clue, why this happens with my tablet.
I know the solution to this problem. This is caused by the bootloader. The way to fix this, only confirmed on GT-P7510 on Nameless 4.4.4 rom.
You need to download this file and flash it via ODIN under 'BOOTLOADER'.
Link: http://droidbasement.com/galaxy/roms/cm9/p4wifi/
Look for 'US_LPL_4.0.4_bootloader.zip' in that link. Make sure you extract the zip file of course for the tar file to flash for bootloader.
The tar file should be called: '4.0.4_bootloader.tar'
benjamen50 said:
I know the solution to this problem. This is caused by the bootloader. The way to fix this, only confirmed on GT-P7510 on Nameless 4.4.4 rom.
You need to download this file and flash it via ODIN under 'BOOTLOADER'.
Link: http://droidbasement.com/galaxy/roms/cm9/p4wifi/
Look for 'US_LPL_4.0.4_bootloader.zip' in that link. Make sure you extract the zip file of course for the tar file to flash for bootloader.
The tar file should be called: '4.0.4_bootloader.tar'
Click to expand...
Click to collapse
BUMP, in case you didn't get my reply.
---------- Post added at 11:14 AM ---------- Previous post was at 11:14 AM ----------
car_42 said:
Hi dookie23,
thanks for your reply. I just tried it, and it did not work.
My issue is not, that the content in the video memory is wrong, but the video memory is not rendered correctly to the screen. To get an impression, have a look at http://forum.xda-developers.com/showthread.php?t=1680738
Obviously the graphic HW is not initialized correctly when resuming... I have no clue, why this happens with my tablet.
Click to expand...
Click to collapse
BUMP again
Hi Benjamen50,
thanks a lot -i tried your solution that did the job. Now i can use the tablet again. I am using Omnirom and this works fine as well (i did not try nameless rom).
thanks so much!
I've had the same problem on my p7500. Installed the nameless 4.4.4 rom, worked fine until the screen went into sleep mode or when I pressed the on/of button. I flashed the bootloader as you suggested and "bam !" It all works fine. Thanks so much !
Q&A for [ROM][4.4.4][YP-G70] Carbon ROM For Galaxy Player 5 [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Encryption possible on Carbon ROM 4.4.4 for the YP-G70?
I have installed and love the Carbon ROM 4.4.4 (10012014 version) on my YP-G70. Problem: When I try to encrypt the Android logo appears (green droid) as a splash screen with no text at all, and encryption does not start. In fact nothing is happening and it is possible to return to normal use. The forum will not yet let me post links but the symptoms are identical to a thread on forum.cyanogenmod.org where the problem is diagnosed as the filesystem cannot extend into the last 16 Kbytes of the partition where the crypto footer is kept. However, when I followed this line I soon concluded that following the advised solution (subtract few Kbytes (more than 16) off the /data partition and redo the partition) does not work for me because LVM is implemented in this ROM and my data partition is therefore /dev/lvpool/data (and does not appear with the ~ # cat /proc/partitions command anyway).
I've googled and not found a way round this. Can anybody help me? If it is not possible to encrypt in this ROM, I've also read (another link I can't post) on github where Meticulus discusses reverting to a pre LVM ROM. Any suggestions on what sort of compatible recent ROM I could try that would contain a kernel not use LVM? This seems to be a pretty obscure subject and I much appreciate any help.
Thanks
Kevinc25 said:
I have installed and love the Carbon ROM 4.4.4 (10012014 version) on my YP-G70. Problem: When I try to encrypt the Android logo appears (green droid) as a splash screen with no text at all, and encryption does not start. In fact nothing is happening and it is possible to return to normal use. The forum will not yet let me post links but the symptoms are identical to a thread on forum.cyanogenmod.org where the problem is diagnosed as the filesystem cannot extend into the last 16 Kbytes of the partition where the crypto footer is kept. However, when I followed this line I soon concluded that following the advised solution (subtract few Kbytes (more than 16) off the /data partition and redo the partition) does not work for me because LVM is implemented in this ROM and my data partition is therefore /dev/lvpool/data (and does not appear with the ~ # cat /proc/partitions command anyway).
I've googled and not found a way round this. Can anybody help me? If it is not possible to encrypt in this ROM, I've also read (another link I can't post) on github where Meticulus discusses reverting to a pre LVM ROM. Any suggestions on what sort of compatible recent ROM I could try that would contain a kernel not use LVM? This seems to be a pretty obscure subject and I much appreciate any help.
Thanks
Click to expand...
Click to collapse
I can't say much about device encryption; never tried it and don't want to. However I can say a couple things about LVM that might help you.
LVM was not implemented until KitKat, so any custom ROM before KitKat will not have LVM
The LVM binary is located at /lvm/sbin/lvm and if I remember correctly there are commands you can issue to resize an lvm partition (Google the lvm man page if you want to try it) and (if indeed that is the actual problem)
Good luck
Meticulus said:
I can't say much about device encryption; never tried it and don't want to. However I can say a couple things about LVM that might help you.
LVM was not implemented until KitKat, so any custom ROM before KitKat will not have LVM
The LVM binary is located at /lvm/sbin/lvm and if I remember correctly there are commands you can issue to resize an lvm partition (Google the lvm man page if you want to try it) and (if indeed that is the actual problem)
Good luck
Click to expand...
Click to collapse
I just wanted to say thanks for this. I went back to your Slim Bean ROM and tried to change the partitions per the research I had done but after much work only succeeded in soft bricking the device. Anyway, I wanted to let you know I ended up in exactly the same situation as the guy in this thread you responded to forum.xda-developers.com/showthread.php?t=2609692 with an inability to re-flash your slim bean or carbon (status 7 errors in CWM and failure to mount/format sdcard, data and emmc) in spite of having the exact fdisk partition table as his. I followed the steps you suggested in that thread including going back to stock and eventually, like the poster, ended up with Android System Recovery <3e> and a bunch of failed to mount cache errors. I kept trying to reflash Entrophy512's Daily Driver in Odin but to make matters worse the device wasn't charging - just getting hot - so it was cycling and I think preventing a good flash of anything. Eventually I did get that flashed and the device began charging properly, then booted to Samsung stock. However, it still wouldn't recognize the internal storage sdcard and wouldn't mount or format it. Attempts to flash your slim bean still failed with status 7 errors.
So, like that poster, I then tried flashing CM (I used CM9 figuring the older the better). Lo and behold, that flashed and when it booted there was a pause while it said "preparing sdcard", then when it finished I had my 5GB internal storage back. Then I was able to flash your Slim Bean and Carbon as usual - completely repaired.
To get to the point, I just thought you might be interested to know that there do seem to be times when a flash of CM may repair some partition related matters, I have absolutely no idea why, but thought it might help you to know... As for encryption, I may consign that one to the long term list for now (CM didn't seem to allow that either)!
Most importantly, thanks again for all the great work, websites, forum help and quick responses!
Kevin
compass
For me, everything is working fine. Only compass is not working. Any idea what could be the reason?
About BCMON
Do Bcmon supported this device because it has a broadcom chipset. I already installed bcmon.apk , open it and enabled monitor mode, freezes for like 10 seconds and it doesnt work. It stays in enable monitor mode also the Wi.Fi doesnt turn on now when I open "monitor mode", need to restart to fix the problem. Anyway the bug has to do with the rom compatibility ? or the device of broadcom ? Can you fix this please ?
The latest build had great battery life.
Sent from my One using Tapatalk
Whick kernel to use ??
Can u please tell me that which kernel do we have to use with your carbon rom build CARBON-KK-UNOFFICIAL-20141022-1740-venturi.zip . i currently have rj's custom kernel v 14 and when i tried to flash it my player got stuck in infinite bootloop . The only thing i can acces now is cwm recovery and Download mode. Can you please reply and also tell how can i exit the bootloop. Thank you very much. Also, i have SGP 5.0 with physical home button so i guess its the internation version only.
I always use the kernel provided with the ROM, it's tested and tried by the developer.
Sent from my One using Tapatalk
I might be a little late to the party, but did you wipe the cache partition, perform a factory reset, wipe Dalvik cache, and then install the latest stable Carbon build? The kernel that the newest stable Carbon build, Nutella Kernel, is unified with the build, so flashing it is like a 2 - in - 1 flash. Remember to get the latest Mini Modular Package version of PA GApps for 4.4.x!
================================
• Samsung Galaxy Player 5 (YP-G70USA)
> Carbon ROM 4.4.4
- Nutella Kernel included with ROM
*Carbon ROM/Nutella Kernel by Meticulous Development team; visit their site at http://www.meticulous a development.com/
Could your EGL_BAD_ALLOC error be due to a mismatch between the driver version and the gralloc library version. Building against the correct version may solve the problem
clovis123 said:
Could your EGL_BAD_ALLOC error be due to a mismatch between the driver version and the gralloc library version. Building against the correct version may solve the problem
Click to expand...
Click to collapse
I don't think so, both gralloc and the graphics blob are not built, they are prebuilt.
factory restore from carbon mod
I did the Carbon mod and it seems buggy to me so i wanna go back to the factory settings and sell the player
I have galaxy player 5.0 . I cant get odin to recognize the player . I downloaded the samsumg drivers many times still wont see it . debugging is off . I cant find setting to see it the player is in Kies mode in this CARBON MOD . >
If I could get a tutorial or link to restore to factory rom I would appreciate it TY
Oh and I did find the factory rom page . just no instructions on how to make it work.
mib2000123456 said:
I did the Carbon mod and it seems buggy to me so i wanna go back to the factory settings and sell the player
I have galaxy player 5.0 . I cant get odin to recognize the player . I downloaded the samsumg drivers many times still wont see it . debugging is off . I cant find setting to see it the player is in Kies mode in this CARBON MOD . >
If I could get a tutorial or link to restore to factory rom I would appreciate it TY
Oh and I did find the factory rom page . just no instructions on how to make it work.
Click to expand...
Click to collapse
If you go back through the previous few posts you will see that I did various experiments trying to get the player encrypted and at various stages had to get back to stock from some really nasty positions. I had to be really really persistent with Odin then - I had the device apparently power cycling so it was not awake long enough to work I guess. I just had to try over and over. Also you may like to try installing the Dr Wondershare (recovery file tool) on your just because this will install different drivers for the device which worked better for me: the tool is a free download/install, you only pay if you need the recovery aspects so it's worth a try. Obviously if odin doesn't work put in download mode (hold voldown and then power on)... Good luck. I got through it and reflashed Carbon (I'm now using the player as a remote control for Foobar2000 and Windows Media Center on my HTPC).
Kevinc25 said:
If you go back through the previous few posts you will see that I did various experiments trying to get the player encrypted and at various stages had to get back to stock from some really nasty positions. I had to be really really persistent with Odin then - I had the device apparently power cycling so it was not awake long enough to work I guess. I just had to try over and over. Also you may like to try installing the Dr Wondershare (recovery file tool) on your just because this will install different drivers for the device which worked better for me: the tool is a free download/install, you only pay if you need the recovery aspects so it's worth a try. Obviously if odin doesn't work put in download mode (hold voldown and then power on)... Good luck. I got through it and reflashed Carbon (I'm now using the player as a remote control for Foobar2000 and Windows Media Center on my HTPC).
Click to expand...
Click to collapse
ok the main issue I have is I tried to do a factory reset and erased cache and all that and rebooted into a soft BRICK lol .. took me 2 days of googlin to find one-click unbrick and to learn how to use ubuntu and it worked the first try . It rebooted like normal . Now the issues after all this .. The data cable will not recognize the player to download anything . AND the cable will not charge the player unless I reboot it with cable installed. ALSO if I power down all the way and hook the data cable up the player reboots instead of staying powered off and charging.
Ill look into Dr wondershare . see if that helps any .. Thanks Ed
---------- Post added at 07:35 PM ---------- Previous post was at 07:27 PM ----------
mib2000123456 said:
ok the main issue I have is I tried to do a factory reset and erased cache and all that and rebooted into a soft BRICK lol .. took me 2 days of googlin to find one-click unbrick and to learn how to use ubuntu and it worked the first try . It rebooted like normal . Now the issues after all this .. The data cable will not recognize the player to download anything . AND the cable will not charge the player unless I reboot it with cable installed. ALSO if I power down all the way and hook the data cable up the player reboots instead of staying powered off and charging.
Ill look into Dr wondershare . see if that helps any .. Thanks Ed
Click to expand...
Click to collapse
ok I just downloaded the software and it cant find the player .. There has to be a setting on the player like in the original for it to see the connection
Which ROM
Hi
I have tried various CARBON KK Roms, but every time I attempt to flash the update using CWM-based recovery v5.0.2.7, I get the following:
Installing: /sdcard/CARBON-KK-UNOFFICIAL-XXXXXXXX-XXXX.zip
Finding update package...
Opening update package...
Installing update...
This package is for "YP-G70,venturi,venturi_usa" devices; this is a "herring".
E:Error in /sdcard/CARBON-KK-UNOFFICIAL-XXXXXXXX-XXXX.zip
(Status 7)
Installation aborted.
I have GALAXY S WiFi 5.0 device
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2