I need a real and very specific answer here please that is for my specific device only. I will tag this post properly.
My Device: Samsung Galaxy Tab 2 10.1 WiFi, GT-P5113. Screenshots attached.
I need advice on getting my Tablet updated from CyanogenMod 10.1 to 10.2. Yes there are lots of entries here about this issue, but they are flooded with all sorts of different devices, 60 or more pages, little of it is for my specific device. I have ClockworkMod Rom Manager installed, tried to update manually to the cm-10.2-20131207-NIGHTLY-p5100.zip and gapps-jb-20130813-signed.zip. Booting to recovery gives me the option to flash a zip file, I choose the cm-10.2 zip. This is not like Safe Strap where I can also choose the gapps. When I tried to flash the zip, I get a system 7 error, no update.
In Settings/About Device is the update section, and the same cd10.2 update is available. But it tells me it will put me into manual mode, I see no way to update the gapps, so I give up. I did this same update with my Droid Razr Maxx and it did work, had to change the Settings, More, Mobile Networks, Network Mode, and choose CDMA + LTE/EvDo to get my phone back, but it worked. I wanted to try to update by Settings, but ended up in Safe Strap, so I choose the ROM zip and added the gapps zip. I cleared the caches and did a factory reset, and it worked, but I had to setup the entire thing all over again, huge PITA! Now, in this forum somewhere, instructions say to flash the rom and gapps, did not say factory reset was necessary. Anyway, it is done on the phone, took a while to setup, switched back and forth from stock to 10.2 until I was comfortable enough with 10.2 to run it all the time.
But this Samsung GT-P5113 is a totally different animal. I wade my way through 60 pages of posts, finding out that some stuff does not work, but the worst thing is that root is gone! Losing root here for me would be a disaster, I have no way of restoring it in CM10.2 that I know of.
Has anyone actually updated a Samsung Tab 2 10.1 to CM10.2 successfully? How did you do it? Method and apps please? Links appreciated. Will I lose root? Must I factory reset or can I update and keep my accounts?
Somebody please address this very one specific device to make it perfectly clear for those of us that have it, have root, moderate experience, and need/want to get this done. Since the GT-P5113 is the same for Gt-P5100, this thread will cover the entire GT-P51xx line. Somebody please help so I can get this done without wrecking or bricking my device. I love Linux and use it often to root or update my phone, at least I do not need drivers for Windows but will accept whatever you can offer with gratitude. Thank you guys!
...well, it looks like the screenshots did not upload or at least do not work for me, have to give images in post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
problem with rooting gtp5113
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.
chongfl said:
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.
Click to expand...
Click to collapse
chongfl,
What exactly do you need, buddy? My tablet is now running on CyanogenMod ROM 10.2 so I did get it to work and it is real nice. There is an option in ClockworkMod ROM Manager under "Recovery Setup" to choose CWM ROM Manager (Which does not work for this update.) OR TWRP. I selected TWRP over CWM ROM Manager and I was able to perform the update. Then go back with CWM and install the gapps package. I like it and it worked for me.
But if you want help, you have to be very specific as to what your issue is, what make/model device, and what you have or have not done and what happened. Otherwise myself or anyone else cannot help you unless we know what your issue is.
Oh wait a minute, your post title says lost root. So what happened, you updated, got the update done, and now do not have root anymore? Are you sure? You can look for the su binary, superuser app, busybox file, or if you want to make it real easy, go to the Play Store and download a "Root Checker". This free app will tell you if the phone is rooted or not. I think there are many versions of root checker,. but here is Root Checker at the Play Store.
Use an app like that to find out if you really lost root or just cannot find it. And then tell us what you found, what you need, make and model of the device, version of Android you are running. (I have 4.3.1 now and have to update my signature.), and what ROM you installed. Okay?
If my post helps you in any way, please click the big "Thanks" button under my name on the left.
Same question
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!
johnf84 said:
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!
Click to expand...
Click to collapse
What say John.
You said you have the GT-P5113! Okay, so you have to use the GT-P5110 file. Now I can help. Gee, I have been spending all my time on the phone with CM11 because it is really exciting and "a whole new world on an entirely new level". I might update my tablet with you since it has been a while and there might be a later package for me. I will then go to CM11.
Here is a quote from the instructions page for your ROMS (Click this line to visit page.).
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
You know, I have spent all my time updating CM10.2 tp CM11 on my phone that I haven't updated the tablet yet. Kind of a dumb thing, the phone is important for communication and I got a monthly bill with it. So it would have made MUCH more sense to update the Tablet first, then do the phone. But I stubled on a really active thread, over 150 posts, about my phone, the update to CM11, that I read it and got interested. Plus, I was watching for updates to CM10.2 and when I saw there was an update and I got excited, ready to go, until....
...I saw the "update" was not to another CM10.2, but to CM11. Now THAT is a totally different animal. I have been ROMing and doing computers long enough to know a major version change means BIG update and usually means "Clean Install". I stopped dead in my tracks to read up first.Good thing too, because there were not very many updates for 10.2, only a few, never "stable" and then they went directly to CM11. Since CM10.1 and CM10.2 were both Jellybean versions, CyanogenMod did not waste a lot of time on CM10.2. I count 5 updates for CM10.2 and no more. Because Jellybean is "old school", CM11 is Kit Kat and totally different. A LOT different. Matter of fact, I cannot find anymore CM10.2 files on the CM website. They dropped it for CM11. 10.1 & 10.2 were mostly the same anyway, not much of a difference, CM10.2 developing to stable did not seem worthwhile anymore because Android is now taking a different direction and a very welcome one. Very slick, very smooth, totally different and agressive memory management. No more 20-30 apps running all the time, fighting for that precious memory. CM11 puts things to sleep pretty quick when they are not used, there are kernel modules now in something called the Xposed Framework, LOTS of them that let you customize the entire system, how it works, overclocking, almost anything you want.
Check for yourself, here are the pages for the GT-P5110, they do not make a rom for GT-P5113 because they are essentially the same but for the IR blaster so you can use it for a remote to control your TV or something like that.
Instructions Page
Download Page
This quote explains the difference between the two models and why they do not make a special rom for the GT-P5113.
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
There are no CM10.2 updates anymore. They dropped it. I have 5 on my device but the updates were easy because they were not a big deal, it was pretty much the same thing. Nothing special for updating. So, for you, the next big update would be CM11 and you take the very latest one they have, get the right gapps, and there is a special kernel called the "JBX" kernel you can apply that will allow all sorts of upgrades to the core of the system like tweak memory, CPU speed, sleep, battery use, governors for the CPU, color balance for the screen.
You need to find the right thread to read and follow to upgrade the GT-P5113 to CM11, read it, take notes, save pages that are guides, ask questions, and READ. Then gather your stuff and get ready to try. You will need a different Recovery Environment to install with too, like TWRP instead of CWM. Because you have to flash not only the rom, but the gapps as well and if you choose, and you should, the jbx kernel with it. ClockworkMod does not do "multiple zips", at least I don't think it does. I had to change inside of CWM to TWPR recovery mode just to get my last updates done.
Alright I found it. This is where we have to move the discussion to. Since you cannot update to CM10.2 because it is no longer supported and was dropped, you move on to CM11. You need the instruction page, with downloads, shows you where to get the files, the recovery tools you can use, plus 49 pages of discussion about it. They give a list of recovery tools, CWM is listed but "CWM 6.0.4.4 or newer (or recoverys based on it" is the only one supported. If I were you and I will be you shortly, I would probably use TWRP. I am using in on my phone in Safe Strap and it gives 6 slots to install roms into, a LOT of features, backups, restores, wipes, and can install more than one zip at a time.
Here is the page you want:
[ROM][P51xx][4.4.2]CyanogenMod 11 (CM11)
Since I have spent all my time updating the phone to CM11, I have not worked on the tablet yet nor picked a recovery yet. I will probably use TWRP, this one.
TWRP 2.6 - Samsung Galaxy Tab 2 10.1 (p5100 or p5110)
It is a LOT different than ClockworkMod Rom Manager and it is nice. Here is a whole page of recoveries you can use for this on XDA.
Now read, read, ask questions, and READ.
You can get the jump on me if you want, I already bookmarked the page and will be doing my tablet soon. Don't take this lightly and spend a week or two reading, asking questions, googling on Kit Kat, and get ready for this. I can tell you it is super cool and WAY worth it. At first you will be overwhelmed when you install the right stuff and all the things you can configure. But it will become clear and this is the best, BY FAR!
You have to really read up on this. The Droid Razr has over 150 pages in the thread so a LOT of people have done it and got over the bugs and are finally enjoying it in all of it's glory. Not sure how far along the Samsung Tablet is with Kit Kat so reading up is a must. You are not missing anything with CM10.2, it is only CM10.1, warmed over with a little extra icing on the same cupcake. CM11 is a serious upgrade.
If you want to see what I have been doing with my Droid Razr Phone, plus learn A LOT about CM11, how it works, what was/is wrong with it, how it is now, read this thread. It is over 225 pages already!
Okay man, I will see you over on the CM11 tablet page. If you found this post helpful, please click the Thanks button. See you on the other side, John! :good:
Related
I just made the switch from BlackBerry to Android and the Relay seems like a good fit for me since I really can't stand touchscreen keyboards. I already unlocked the phone per the forum sticky since I'm on AT&T and it was a priority.
I *think* I want to install Cyanogenmod 10.2 (I'm a fan of using stable builds). When I look over the installation instructions, I'm a bit cornfused on step one:
There is an Important Note instructing users to install bootloader and radio firmware. How do I do that? The zip files it links to don't include any instructions or links to any instructions.
openletter said:
I just made the switch from BlackBerry to Android and the Relay seems like a good fit for me since I really can't stand touchscreen keyboards. I already unlocked the phone per the forum sticky since I'm on AT&T and it was a priority.
I *think* I want to install Cyanogenmod 10.2 (I'm a fan of using stable builds). When I look over the installation instructions, I'm a bit cornfused on step one:
There is an Important Note instructing users to install bootloader and radio firmware. How do I do that? The zip files it links to don't include any instructions or links to any instructions.
Click to expand...
Click to collapse
It pretty much means update to the latest ota available...which is T699UVBMC5 if you don't you'll have issues with signal and such...last I heard 10.2 had very rapid battery drain and stability issues but its possible they may be fixed but idk...most stable would be cm11 in terms of cyanogenmod but all my users say my latest carbon ROM is the most stable ROM available for relay as they go back to that if any issues arise in my other ROMs or teamapexq roms. Liquidsmooth ROM that I have has a lot of tweaks and mods and is fast and smooth...it gets updated the most as it is official and there is an ota within the ROM that whenever I release you can update it straight from phone without really having to do anything
REV3NT3CH said:
It pretty much means update to the latest ota available...which is T699UVBMC5 if you don't you'll have issues with signal and such...last I heard 10.2 had very rapid battery drain and stability issues but its possible they may be fixed but idk...most stable would be cm11 in terms of cyanogenmod but all my users say my latest carbon ROM is the most stable ROM available for relay as they go back to that if any issues arise in my other ROMs or teamapexq roms. Liquidsmooth ROM that I have has a lot of tweaks and mods and is fast and smooth...it gets updated the most as it is official and there is an ota within the ROM that whenever I release you can update it straight from phone without really having to do anything
Click to expand...
Click to collapse
I'm having a hard time finding an install guide for anything other than CM. For carbon, I'm guessing it's located at vp-zp.com/snuzzo/roms/carbonrom/apexqtmo/kk/ ? Even that I got from googling and then backtracking links from a blog post, as the carbon webpage doesn't seem to have a Relay ROM listed.
To be honest, as a total n00b at this, I'm having a hard time pulling all the pieces together to understand the various different abbreviations, projects, download sources, etc. My goal is simply a nice stable build that is maintained, updated to support major features, but without adding issues, such you as mentioned there may be battery life issues in CM.
openletter said:
I'm having a hard time finding an install guide for anything other than CM. For carbon, I'm guessing it's located at vp-zp.com/snuzzo/roms/carbonrom/apexqtmo/kk/ ? Even that I got from googling and then backtracking links from a blog post, as the carbon webpage doesn't seem to have a Relay ROM listed.
To be honest, as a total n00b at this, I'm having a hard time pulling all the pieces together to understand the various different abbreviations, projects, download sources, etc. My goal is simply a nice stable build that is maintained, updated to support major features, but without adding issues, such you as mentioned there may be battery life issues in CM.
Click to expand...
Click to collapse
i've been running the M7 snapshot of CM11 for about a month now. my only complaint about battery isn't really the rom's fault - if i'm watching a lot of netflix or youtube, the battery goes down faster. that's not really a surprise though.
i'm still pretty new to the relay though i've had a couple other androids before this one. but i suggest you use TWRP (Team Win Recovery Project) instead of CWM (clockworkmod) for your recovery. it's got a gui and is a bit easier to use when flashing roms and doing wipes and stuff.
bsically the process is to boot your phone into download mode, flash twrp, then reboot the phone into twrp, wipe everything, then flash CM and gapps (if you want google apps like gmail, play store, etc). then wipe cache/dalvik/factory reset (because some roms are unstable if you simply flash without doing the second wipe). no need to try to inject SU (superuser) or anything since pretty much all custom roms are already rooted. there are other posts that go into more detail but this should about cover it.
Gibson99 said:
i've been running the M7 snapshot of CM11 for about a month now. my only complaint about battery isn't really the rom's fault - if i'm watching a lot of netflix or youtube, the battery goes down faster. that's not really a surprise though.
i'm still pretty new to the relay though i've had a couple other androids before this one. but i suggest you use TWRP (Team Win Recovery Project) instead of CWM (clockworkmod) for your recovery. it's got a gui and is a bit easier to use when flashing roms and doing wipes and stuff.
bsically the process is to boot your phone into download mode, flash twrp, then reboot the phone into twrp, wipe everything, then flash CM and gapps (if you want google apps like gmail, play store, etc). then wipe cache/dalvik/factory reset (because some roms are unstable if you simply flash without doing the second wipe). no need to try to inject SU (superuser) or anything since pretty much all custom roms are already rooted. there are other posts that go into more detail but this should about cover it.
Click to expand...
Click to collapse
Where can I download TWRP for the Relay?
openletter said:
Where can I download TWRP for the Relay?
Click to expand...
Click to collapse
search for it in the relay forum - it has its own thread, i think in the dev sub-forum. instructions to install it are the same as cwm, just use the twrp file instead of cwm.
Gibson99 said:
search for it in the relay forum - it has its own thread, i think in the dev sub-forum. instructions to install it are the same as cwm, just use the twrp file instead of cwm.
Click to expand...
Click to collapse
Thanks - I was just discovering that forum when you replied. I had looked right passed it initially since there isn't usually anything for me in dev forums for other projects I use.
Q&A for [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart
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:
Xoom cm11
Im currently running cm11 on xoom. Chrome freezes lots. Is there a fix or workaround.
eric1212 said:
Im currently running cm11 on xoom. Chrome freezes lots. Is there a fix or workaround.
Click to expand...
Click to collapse
At one point in time (around May) people were having issues with any version of Chrome newer than or including V34. People were reverting back to V33. I don't know if it has been resolved as I went back to using the stock browser.
I dug around - http://forum.xda-developers.com/showpost.php?p=52506042&postcount=920 - this post has/had a link to Chrome V33. I cannot vouch for the link. I ended up getting V33 out of a PAGapps package that I had backed up from the beginning of March.
How do I side load chrome v33. I am unable to do so. I keep getting the error , app not installed.
Xoom, EOS kitkat., EX2.1
The CM11 install messed up for me, could I please get some help at the thread I posted on this? Thanks! Just wish this ROM would work for me..
I have the same issue with Chroma and Opera -both crashing my Xoom (Everest, [4.4.4] CyanogenMod 11.0 ). When i tried to kill chrome, it kills also my battery - discharging takes about 4h from 100% to 0%.
Now I installed Chrome v32 and works fine
Frequent Freezes of Wingray requiring Reboot
In Aug-Sept 2014, there was a discussion in the thread: [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart, related to Frequent Freezing of Wingray requiring Reboots (see posts 595, 597, 599, 600, 611 and 615). I have been experiencing the same (or very similar) issues for several months. I have an MZ604 with Wingray and have been taking the monthly updates regularly since they have become available; I initially installed CyanogenMod about 7 months ago. I have been running with Xposed and Wakelock Terminator as described in http://forum.xda-developers.com/showthread.php?t=2697893.
The freezes almost always (with one exception) happen when the XOOM is sleeping; the exception was a crash that happened once while I was using the device, but it might be a different issue. Freezes were happening about once/day, but in the past few weeks had increased to almost every time I put the XOOM to sleep. The only way to recover from a Freeze is to completely reboot the device by holding both the power button and the Volume button simultaneously for several seconds. Freezes usually seemed to be accompanied with a significant battery reduction, so I suspect something was coming to life, using a lot of battery for a while and then killing the XOOM. My Battery Monitoring app would never keep data through one of these freezes, so it was useless in helping me understand what came to life, used the battery and then caused the crash.
For some reason, this week the XOOM has stayed alive for an entire battery cycle. I recharged it 4 or 5 days ago, and used it according to my usual pattern of 3 or 4 times per day for anywhere from 15 minutes to an hour each time. The battery went down by about 15-20% per day at a pretty consistent rate. I put it back on the charger this morning with 16% battery left. After the very frequent freezes prior to this week, I was very surprised to see it stay alive for a full 4-5 day period. For the rest of you who were experiencing these freezes/crashes, did your device start working without freezes this week too?
Hi ,
I'm new here, and I can't find answer by searching.
How can I change my lock screen orientation?
Thanks!
Which GAPPS for CM11 ?
Hi all,
just flashed cm-11-20140912-UNOFFICIAL-1551+0200-everest.zip on my MZ601, trying to get some of the google apps working. In my previous tests, with EOS-full_everest-20141110.083307.zip the chrome browser ( either beta than normal ) used to hang, and so it does google maps.
I've flashed pa_gapps-modular-full-4.4.4-20141110-signed.zip but I have the same behavior with maps ( crash when zooming ) and I suspect also the hang on chrome ( not tested yet ).
I have read on the thread <url> http://forum.xda-developers.com/showthread.php?p=56740906&highlight=maps#post56740906 </url> that on the latest version maps crash but seem to be working on some previous release.
So the question: which version should I install to get a working maps and ( eventually ) chrome ?
Thanks in advance
Pigi
Changelog
Hi!
Where I can find the latest changelog for this new version of CM11 for XOOM?
Thanks.
Pigi_102 said:
Hi all,
just flashed cm-11-20140912-UNOFFICIAL-1551+0200-everest.zip on my MZ601, trying to get some of the google apps working. In my previous tests, with EOS-full_everest-20141110.083307.zip the chrome browser ( either beta than normal ) used to hang, and so it does google maps.
I've flashed pa_gapps-modular-full-4.4.4-20141110-signed.zip but I have the same behavior with maps ( crash when zooming ) and I suspect also the hang on chrome ( not tested yet ).
I have read on the thread <url> http://forum.xda-developers.com/showthread.php?p=56740906&highlight=maps#post56740906 </url> that on the latest version maps crash but seem to be working on some previous release.
So the question: which version should I install to get a working maps and ( eventually ) chrome ?
Thanks in advance
Pigi
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=57207242
Sent from my GT-I9505 using XDA Free mobile app
Xoom Battery Issues with [ROM][4.4.4] CyanogenMod 11.0 - Wingray - bigPar
Gentlemen,
After flashing with this rom (http://forum.xda-developers.com/showthread.php?t=2596566) my xoom started dying in less than 24 hours(even with wifi off).
With the original rom it would last several days in stand by mode.
Any clues?
thx
Problem
com.android.systemui and Googles services Constantly restarts and makes tablet totally unusable.
change googles app???
affs said:
com.android.systemui and Googles services Constantly restarts and makes tablet totally unusable.
change googles app???
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=57188808
Mobile data not working
Hey everyone, my mobile data isn't working because when I flashed I lost my IMEI, for more details please look at my posts here http://forum.xda-developers.com/showthread.php?t=2596566&page=69
Thanks for your help.
-Mr_IceSlice
New guy here, i just installed the omni everest build for the xoom following these instructions http://forum.xda-developers.com/showthread.php?t=2593414
Everything works as expected except my verizon 3g i have explored all available settings and rebooted and reflashed several times. It registers verizon signal but under status it says network type unknown and status as disconnected. Is there something im missing? The tablet was stock before and all mobile signals worked as they should
Thanks!
Thanks for the guide mate.
At first, I had user issues with the TWRP. TWRP asked me to enter a password during initial boot. I just hit cancel. It then could not do any wipe per instructions on this page (page 1) including Advanced Wipe, Mount cache, etc. Perhaps, I was a bit lazy reading every word.
So I skipped this process and went ahead and flashed the [ ClockworkMod Recovery ], I't s a very nice familiar Interface during my Droid X days. The TWRP is also now quite familiar to me since I used it to install [ CyanogenMod Crombi-kk on my Asus TF700T ] (sloww device! My Xoom is faster!!! Believe it!) Anyhow the whole install including the ROM was a breeze. However, I noticed that the version says 4.2.2 or something like that. I wanted 4.4.4.
So here I was, back again.
Anyway, I re-flashed back the recovery to TWRP then decided to just go ahead and format the data (IIRC, that option is available)
Guess what, it worked! Installed the ROM and done! =)
Oh BTW, I also installed the PA_GAPPS. I don't remember where I got the link from, but I'll try to edit this if I find it.
PHOTOS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second Install after wiping out 4.2.2
4.4.4
No 3g or 1x fallback
Been having this issue with every big part ROM i have installed. Verizion 4g service or nothing. Something is not right with the baseband.
need to big partition my xoom 601
halo house am new here, you guys are really doing a great job(kudos). i have rooted my xoom, but having prob on how to big partition my xoom. pls i really need u guys assistance if there is a video to it pls send me the link. thanks
Bug?
I got this rom to run just fine, and most things seem to work well.
The biggest issue I am having with the latest posted CM11 with BigPart is with Plants vs. Zombies 2 which wont display anymore. I have tried a new install and restoring the backup from the old nightly CM 10.1 and nothing works.. Flashed this ROM to my second Xoom to verify the issue, noticed a handful of games that launch to a glitched or black screen. Thoughts?
Would hate to back-date as everything ELSE is running faster than it has in a while.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
TOP TIP "For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed." Thanks go to tobitege for this.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
+1. I also flashed the latest official CM nightly, booted it and checked if everything was working and then flashed the latest unofficial Temasek's rom. Everything works fine.
Cheers
@zaphodbeeb: thanks for having created this!
This morning I tested an extended version of the CM-12 flashable zip containing more partitions of the current nightlies.
First test brought me a jackpot in that it flashed without an error message, but soft bricked my phone (black screen, no adb nor fastboot), but power button rebooted in a special mode "HUSB_BULCK" (viewable in device manager). Takin' up the challenge, so after plenty of searching/reading and multiple tries to install the right drivers, I got it going through Color OS installation with special phone flashing tool, then flashing X44 again, unlocking, custom recovery+rooting... that was (deserved) fun!!
Though in the first moments it scared me s***tless!
Long story short, totally agree to just flashing the full nightly and directly clean on top any LP rom you want, if you want to be sure to have it right.
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
cam30era said:
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
Click to expand...
Click to collapse
I dirty flashed SlimSaber-bacon-5.0.2-20150110 build on top of SlimSaber-bacon-5.0.2-20150102 and then flashed alpha modem everything works fine.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
That weird baseband version is the correct one, no worries.
radium22 said:
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
Click to expand...
Click to collapse
Good idea. Done. Now this really is the end of my contribution on this subject.
zaphodbeeb said:
Good idea. Done. Now this really is the end of my contribution on this subject.
Click to expand...
Click to collapse
So first flash the 3rd zip (cm12 nightly)
Then dirty flash the main Rom or whats the next step?
Thank you
The full nightly should be flashed first, then wipe clean in recovery and install your actual rom (or restore).
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
losthilien said:
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
Click to expand...
Click to collapse
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
I went for number 3. Did a backup of my temasek ROM. Did a full wipe and installed cm nightly. Had full signal and thought great, this is the right modem. Restored my temasek and signal is gone again.
Any idea why? Did I restore too much of my temasek? Boot, system and data.
Thanks
It might just need another reboot after initial restore to reconnect.
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
VQ30DE said:
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
Click to expand...
Click to collapse
Not sure what to tell you. I have no WiFi problems. SlimLP ROM
So I just recovered from a hard brick with a dead battery.... it was brutal. I'm looking to do things more carefully going forward. I'd like to keep CM11S as primary. But obviously I want lollipop asap. If I backup CM11S nandroid... wipe clean, flash CM12 nightly for the modem and such, and then clean wipe and restore CM11S to primary from nandroid... will the modem changes that CM12 nightly made persist? I'd like that.... then I could flash some lollipop roms as secondaries and benefit from the modem changes that cm12 made?
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
tobitege said:
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
Click to expand...
Click to collapse
Top Tip man. I like.:good: I'll include in the OP.
timmaaa said:
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
Click to expand...
Click to collapse
You will notice the subtle message added to my sig also, using simple large letters for those with limited reading abilities.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SinfulROM 2.0
Some History
Some of you may remember me, some of you may not. I was around these parts when the S5 first came out and we were waiting for Root access to use ROMs. I released a ROM called BoxxiRoms, but to be honest, it wasn't too good and there were problems with it. I since kind of left, upgraded to 5.0 via someone else's ROM and left it at that.
Then I got bored with 5.0. Too many things I enjoyed with KitKat just didn't work at all with 5.0. I'm huge on Battery Conservation (as you can see from a post linked in my Signature) and I've always wanted to put out the best damn battery life for this phone that's honestly possible.
Well, I'm back. I've learned a lot since my first ROM release and I'm here to keep to my promise of the best damn battery life and the best experience you can have on your Verizon G900V S5.
Code:
Your warranty is void, and i'm not responsible for any bricking. It's frankly difficult to brick an android device, so I don't think you need to worry about it.
Now that that's out of the way... I've been using this rom for 2 weeks straight to make sure its working just right for release. I started out on a personal built of beta 0.1 and now I'm up to 2.0, which is all for you guys.
Features
Ultimate Debloating (thanks to @elliwigy for the starting base. I went further with it and got it to 450 megs at its base.)
All apps Added are Uninstallable like normal apps
Themable through the Launcher (will custom theme soon)
Great Battery Life
4K Video Recording (through the Camera App added)
My Additions
Smart Launcher 2
Textra (instead of Stock SMS app)
Chrome Beta (instead of Standard Chrome)
Matrik (hacked Kik client with TONS of awesome features)
PAW Server (a nice little server app with plugins available. Will have tutorials with this soon)
Apollo Music Player
OGYoutube (a better youtube app)
MyRoll Gallery (better than Stock gallery and smaller size)
Open Camera App (instead of Stock camera)
XAPK Installer (for use with XAPK files from apkpure)
Pixel Battery Saver (the BEST way to get the best battery life)
SQLite3
BusyBox'd
Rooted with Superuser installed
Future Addons
Pre-Dark-Theme
More built in apps
More Tweaks for Battery Life
Free RAM
This is with Textra, Matrik and PAW Server all open and running.
Eww... Why NCG 4.4.2 KitKat?
Things like Pixel Battery Saver didn't work on 5.0 or later. Also, I had some real crap battery life on 5.0. With my current rom as is with Pixel Battery Saver always running on level 4, I go from 100% at 9am to about 30% at 9PM with some heavy use at work (a lot of down time for Trivia Crack). Overall, I fell 4.4.2 is the BETTER option for the S5.
INSTALLIf there's a better way to install this, let me know, I'm severely outdated obviously as you'll read below
This has ONLY been tested and installed by this method on a G900V
1.) Flash back to NCG Kernel so you can access SafeStrap (download below)
2.) Advanced Wipe Data/Cache/Dalvik/System
3.) Flash the Rom ZIP file
4.) Boot into Android! (first boot may take an extra minute or so. if it takes longer, LET ME KNOW)
Current IssuesNone that I know of. Let me know if you find anything.
DOWNLOAD
ROM
DIRECT LINK (my personal website server)
AndroidFileHost Mirror
Direct Link (BASE ROM No Edits)
NCG Kernel
DIRECT LINK (my personal website server)
AndroidFileHost Mirror
credits
Honestly, with how much downloading and tweaking I've done, I'm not entirely who all the people are to thank for this ROM so far.
Lots more to come soon!
XDA:DevDB Information
SinfulROM, ROM for the Verizon Samsung Galaxy S 5
Contributors
KaptinBoxxi, elliwigy
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: NCG
Based On: Extreme Syndicate
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-01-14
Created 2016-01-15
Last Updated 2016-01-25
dude this is such great news for me. I loved KK and have hated LP since it was released. You are the f'in man for making another KK rom!
wouldn't it be better to go back to NCG rescue .tar and re-root and then flash this? I dont think it'l work the way you described coming backwards from LP. At least it never worked that way before unless yours does something different i dont know about.
here's a link to Jrkruse's "rooting and firmwares" page. the rescue tar is there.
Safestrap Flashable Firmwares
It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest
KaptinBoxxi said:
It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest
Click to expand...
Click to collapse
i tried it your way from the Jrkruse BOK3 stock rooted rom and it bootlooped. Then fresh from rescue tar and it worked perfect. I wish someone else would get in here and compare methods!
I'll modify the instructions when I get home tonight. Maybe I just got lucky haha
twrp install, no prob
For clarification, Are we able to use this ROM if we rooted from jrKruse's Thread to get root on OK3 phones? I was thinking we could only use Lollipop 5.0 TW based Roms,
Thanks..
I'll give it a whirl...
I hate LP too, fav rom's been Beans NE9 rom but it hasn't beet touched in like a year, I'm excited to see what you brought
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
damagi123 said:
wouldn't it be better to go back to NCG rescue .tar and re-root and then flash this?
Click to expand...
Click to collapse
This would be my preferred method too, total restore to NCG with Odin, root, busybox, safe strap, full wipe, wipe both cache's, flash this gem, bingo... No chance for gremlins lol
damagi123 said:
i tried it your way from the Jrkruse BOK3 stock rooted rom and it bootlooped. Then fresh from rescue tar and it worked perfect. I wish someone else would get in here and compare methods!
Click to expand...
Click to collapse
KaptinBoxxi said:
I'll modify the instructions when I get home tonight. Maybe I just got lucky haha
Click to expand...
Click to collapse
abovenbeyond said:
I hate LP too, fav rom's been Beans NE9 rom but it hasn't beet touched in like a year, I'm excited to see what you brought
This would be my preferred method too, total restore to NCG with Odin, root, busybox, safe strap, full wipe, wipe both cache's, flash this gem, bingo... No chance for gremlins lol
Click to expand...
Click to collapse
Install Kit Kat Roms On All Bootloaders
Edit: I updated the method and added new firmware zips ran into some hardware issues these fixed the problem
This method should work for All Bootloaders Without having to wipe data on Internal storage
Download This one NK2_Firmware_No_Bootloaders_V3.zip should work for all Kit Kat Roms. This is a 4.4.4 Version I tested it on 4.42 Version and it worked fine . If you want to use a differen versions, all Version listed below
Reboot To Safestrap Wipe cache, system, data, dalvik cache then flash above zip
Go back and Wipe cache, system, data
Install Kit Kat Rom
Reboot to system and go through setup.
Remember when using Kit Kat Roms there is no reason to flash kernel in safestrap as you are all ready running kit kat kernel. Also do not use Lollipop Safestrap on kit kat roms you can reach safestrap by simply rebooting rom and choosing safestrap recovery when dialog comes up
If you want to use zip that matches firmware of rom a full list can be found [URL="http://forum.xda-
I updated the install instructions. Sorry it took me longer than expected to do so. I had plans yesterday and wasn't home until literally now.
An actual update about the rom itself
I'm restarting my conversion of the Kali Nethunter conversion to the S5 this week, so keep an eye out for an updated ROM IF you're interested in that sort of thing
jrkruse said:
Install Kit Kat Roms On All Bootloaders
Click to expand...
Click to collapse
Thanks so much for doing that. that's great
Once I boot the SuperSu binary won't update..reboot and no go..any suggests/
I'm gonna manually update it in my next release but frankly it doesn't honestly need to be updated to work correctly
Some news:
If you're looking into making your own Slimmed Down NCG Rom, I'll be uploading and posting my base rom tonight when i get home from work. Base rom I'm uploading is 497 megs. Great starting base for anyone wanting to get into making their own roms. I'll have tutorials as well.
KaptinBoxxi said:
I'm gonna manually update it in my next release but frankly it doesn't honestly need to be updated to work correctly
Some news:
If you're looking into making your own Slimmed Down NCG Rom, I'll be uploading and posting my base rom tonight when i get home from work. Base rom I'm uploading is 497 megs. Great starting base for anyone wanting to get into making their own roms. I'll have tutorials as well.
Click to expand...
Click to collapse
Just a question. Why not do NI2 or NK2 build so VOLTE will work. Was the battery life not as good. I know that's your ultimate goal
So far, everything has worked fine. I don't even know what VOLTE is tbh lol. I still get 4G on this ROM, so it's not something I even thought about
KaptinBoxxi said:
So far, everything has worked fine. I don't even know what VOLTE is tbh lol. I still get 4G on this ROM, so it's not something I even thought about
Click to expand...
Click to collapse
If you enable HD calling on your Verizon plan it allows Volte or video calling and HD calling and Visual Voice mail. Once enable the old voice mail method does not work so you wont get any notifications or any thing without the Visual Voicemail apk wich require VOLTE or HD calling. This feature was first available on NI2 build. For example If I wanted to use your rom as a daily driver I would have to call Verizon and disable Advanced Voicemail so I would be able to receive voice mail notifications. Then if I went back to Lollipop I would have to reactivate it. Thats the only reason I asked. I know thats the one thing people ask the most about in the international roms like Phoenix is that it does not support VOLTE and how do they get voicemail working
Thank you gentlemen.
Thanks for bringing us back to KK. been running great for the past 24 hours then i flashed the NCG zip acciddentally and broke the whole mess. Wiped everything and went back to oding anf the rescure.tar and all is well again. A few questions though.
Before i screwed up i noticed...
1. I was consistently losing wifi settings, ( seem to remember this from KK)
2. Quick Pic doesnt seem to be able to set different wallpaper for lock screen and home screen, is this a KK vs LP thing?
3. Baseband if BOG3 is that what it should be?
Thanks again
jrkruse said:
If you enable HD calling on your Verizon plan it allows Volte or video calling and HD calling and Visual Voice mail. Once enable the old voice mail method does not work so you wont get any notifications or any thing without the Visual Voicemail apk wich require VOLTE or HD calling. This feature was first available on NI2 build. For example If I wanted to use your rom as a daily driver I would have to call Verizon and disable Advanced Voicemail so I would be able to receive voice mail notifications. Then if I went back to Lollipop I would have to reactivate it. Thats the only reason I asked. I know thats the one thing people ask the most about in the international roms like Phoenix is that it does not support VOLTE and how do they get voicemail working
Click to expand...
Click to collapse
Oh... I never had any of those voice mail or HD calling features, that's why I didn't know about it.
JeffersonDavis said:
Thanks for bringing us back to KK. been running great for the past 24 hours then i flashed the NCG zip acciddentally and broke the whole mess. Wiped everything and went back to oding anf the rescure.tar and all is well again. A few questions though.
Before i screwed up i noticed...
1. I was consistently losing wifi settings, ( seem to remember this from KK)
2. Quick Pic doesnt seem to be able to set different wallpaper for lock screen and home screen, is this a KK vs LP thing?
3. Baseband if BOG3 is that what it should be?
Thanks again
Click to expand...
Click to collapse
I based this off of ExtremeSyndicate v1.5 which was based on NCG. I had the wifi issue at first, but realized I just never flashed back to the NCG Files which actually had control over all that. Once I had all the NCG files properly set, I didn't have issues at all. When it comes to the Wifi, I've always had issues with this phone (no matter the rom. I was on a 5.0.1 ROM before I sat down and decided to go back to NCG), I'd get random notifications that Wifi just connected but it never actually disconnected in the first place. I'm not sure what that one is
As for the Wallpaper issue, I actually noticed that. I'm not sure why I can't set pictures. I actually put the gallery back in my personal build last night as a test and still can't set wallpapers so I'm not entirely sure what the issue is. If you use Smart Launcher's settings, you can set a wallpaper i'm pretty sure. I pretty much never change my wallpaper so it wasn't something I noticed at first
Everything should be NCG no matter what.
KaptinBoxxi said:
Oh... I never had any of those voice mail or HD calling features, that's why I didn't know about it.
I based this off of ExtremeSyndicate v1.5 which was based on NCG. I had the wifi issue at first, but realized I just never flashed back to the NCG Files which actually had control over all that. Once I had all the NCG files properly set, I didn't have issues at all. When it comes to the Wifi, I've always had issues with this phone (no matter the rom. I was on a 5.0.1 ROM before I sat down and decided to go back to NCG), I'd get random notifications that Wifi just connected but it never actually disconnected in the first place. I'm not sure what that one is
As for the Wallpaper issue, I actually noticed that. I'm not sure why I can't set pictures. I actually put the gallery back in my personal build last night as a test and still can't set wallpapers so I'm not entirely sure what the issue is. If you use Smart Launcher's settings, you can set a wallpaper i'm pretty sure. I pretty much never change my wallpaper so it wasn't something I noticed at first
Everything should be NCG no matter what.
Click to expand...
Click to collapse
Having the latest baseband is always a good idea. It should affect the rom performance in any way.
---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------
I ran this rom for a couple of days. I must say the battery life is good
KaptinBoxxi said:
It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest
Click to expand...
Click to collapse
what jrkruse was saying about you trying to go to NI2 with this rom is important for almost everyone on this forum since we've all upgraded to volte so our vvm wont work.
also titanium backup isnt recognizing root at all. no matter what I try. probably because of the supersu binary problem
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.