[Q] Looking for some assistance - Sprint Samsung Galaxy S III

I have a Samsung S3 L710 on Virgin Mobile.
I've been running a Kitkat ROM; Conquest Singularity; for a very long time and wanted a change. I wanted to try out a ROM running Lollipop.
This is were my issues have started.
I updated to the latest TeamWin recovery and so far have clean flashed 3 different ROMS.
1 ROM the PAC ROM did not stay on the phone long at all because it was having trouble staying connected to my wifi. Wasn't on long enough to see if it has the same problem as the other ROMs listed below.
The other 2 ROMs I've tried, Liquid Smooth and currently on the phone OctOS. Both these ROMs will I think randomly reboot. (I'll get to "randomly" part in a bit.)
One thing I've done that I know is not recommended, is using TiB to replace data on a new flash. My question here is, if you have information in some apps that can not be saved in anyway way, how would one do this without using TiB?
Now onto the random reboots. I know most happened when I was playing Ingress on both ROMs. Ingress uses a lot of resources and being on for a while gets the phone pretty warm. Not sure if it's overheating the phone causing it to be unstable or what.
I have not adjusted any kernel CPU settings on any ROM that I've installed. Everything is left stock. Not sure if the developer has the settings overclocked from an install and maybe this is making the phone unstable.
Basically I'm frustrated to why I seem to be the only person getting reboots, and I know that from what is written no one will have any ideas why. I'm just venting. Now that I've been playing with LP ROMs the past few days, I'd like to keep one on the phone working properly.

Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out

lvpre said:
Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out
Click to expand...
Click to collapse
Well that might explain it.
Haven't tried CM yet because most the ROM's required TWRP recovery and CM takes a different one.
I tried flashing AICP, but the Gapps didn't flash. Said wrong ROM or something. I only had the one Gapps on my internal storage so I flashed the OctOS instead. Just downloaded the Gapps listed on the AICP page. May try flashing that one now. Just so sick of reinstalling all my apps..... :silly:
As for TiB. I'm good then. I never do any system apps. I must have misunderstood about that. Been a long time since I've flashed anything.

Here's how I flashed aicp on my phone, using the modified TWRP that's made specially for Virgin/boost d2spr made by Lrs121. 1. Flash the latest aicp nightly. 2. Flash latest banks gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps. 3. Flash APN fix: http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/ 4. Boot into ROM, and reboot into recovery as soon as it boots up. 5. Reflash the ROM and gapps (but don't wipe anything this time).
That should get you up and running, with LTE and the APNs configured properly.

Thanks all for the help.
Been running the 7/3 build for a few days now without any problems. May flash the 7/7 ver 10 build very soon.
Powered_By_Linux
I tried the APN fix on a Kitkat ROM some time ago and did not help. Found 8SMS messenger with the added line fix and was able to get my MMS messages then. May try the APN fix in the order that you suggested and see if I can go back to the Handscent messenger. I like that app better the 8SMS but was not able to get MMS messages.
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.

elgecko said:
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.
Click to expand...
Click to collapse
Make a backup of AICP. Then you'll have to flash back to a TouchWiz ROM, update PRL, then flash the AICP backup you made. Your updated PRL will stick.
You can also use a PRL from the PRL thread.
http://forum.xda-developers.com/showthread.php?p=35576100
Flash a ROM like Wicked X or Tribute (you don't need your MSL). Download the PRL you want from the many listed in the thread, extract from zip, rename the PRL "TEST.prl" (without quotes), place on your internal SD, open your dialer and press ##DATA# to enter the hidden menu, tap View, scroll down to PRL Write, tap, and select. Your phone will reboot and you'll have yourself the PRL of your choosing.
Some people have good results from using these PRLs while others do not. Personally, I'm on Boost and have been running Sprint PRLs for years lol.
Hope this helps :thumbup:
EDIT......
NOTE- REMEMBER TO FACTORY RESET, WIPE CACHE, DALVIK CACHE, AND WIPE YOUR INTERNAL SD BEFORE RESTORING YOUR AICP BACKUP AFTER EITHER DOING A PRL UPDATE OR FLASHING THE ONE OF YOUR CHOOSING.
Sent from my SPH-L710 using Xparent Purple Tapatalk 2

Related

[Q] Black screen after phone call on CM10.0.0. d2att

I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.

[Q] Synergy Rom Help

Hi guys, I have some noobish questions for you. After reading around and searching, I just cant seem to find an answer.
I installed Synergy Rom with Ktoonsez kernel yesterday and while the Rom and kernel have been one of the best set ups I have ever used on my GS3 (Tmobile) I have two issues.
1. I have very little data. It comes, it goes. If any, the signal is extremely weak. Am I supposed to flash a radio, is this safe, I have never done this before so i'm not sure.
2. When installing the rom, I opted to use the stock android messenger vs the touchwiz one. I am having some issues sending MMS messages and was wondering if there was a fix for this somewhere or if it required a reflash.
I posted in here because I figured it is not a rom related issue, yet just me not knowing how to address these problems.
Any help is appreciated!
-------------------
Edit: I believe I may have just figured something out. I realized I had a sprint recovery on my phone, so when installing the rom I believe that the installer thinks my phone is the sprint variant. Would this have anything to do with signal issues or MMS issues for that matter. Before reinstalling everything I wanted to see if anybody knew if it would fix the problem. Like I said before, I do get signal, its just not extremely strong.
Twisted Tom said:
Hi guys, I have some noobish questions for you. After reading around and searching, I just cant seem to find an answer.
I installed Synergy Rom with Ktoonsez kernel yesterday and while the Rom and kernel have been one of the best set ups I have ever used on my GS3 (Tmobile) I have two issues.
1. I have very little data. It comes, it goes. If any, the signal is extremely weak. Am I supposed to flash a radio, is this safe, I have never done this before so i'm not sure.
2. When installing the rom, I opted to use the stock android messenger vs the touchwiz one. I am having some issues sending MMS messages and was wondering if there was a fix for this somewhere or if it required a reflash.
I posted in here because I figured it is not a rom related issue, yet just me not knowing how to address these problems.
Any help is appreciated!
-------------------
Edit: I believe I may have just figured something out. I realized I had a sprint recovery on my phone, so when installing the rom I believe that the installer thinks my phone is the sprint variant. Would this have anything to do with signal issues or MMS issues for that matter. Before reinstalling everything I wanted to see if anybody knew if it would fix the problem. Like I said before, I do get signal, its just not extremely strong.
Click to expand...
Click to collapse
First, I recommend TWRP Recovery. You can obtain this by installing goo manager from the Play Store. To install, open goo manager, hit the menu key, select 'Install OpenRecoveryScript'. This will install TWRP recovery. Go into your recovery and make a NAND backup. Then wipe data/delvik/cache/system. Now, install Synergy and select Tmobile. Next, what I did, was did a full installation. Yes, this installs everything but you can use root browser (or some other root file manager) and fine tweak the ROM with what you do not want. I had a similar issue but I had NO data/signal/service...nothing. Hope this helps. Just in case, make sure you know how to flash back to stock, should something go wrong. Good luck!
phoenix98 said:
First, I recommend TWRP Recovery. You can obtain this by installing goo manager from the Play Store. To install, open goo manager, hit the menu key, select 'Install OpenRecoveryScript'. This will install TWRP recovery. Go into your recovery and make a NAND backup. Then wipe data/delvik/cache/system. Now, install Synergy and select Tmobile. Next, what I did, was did a full installation. Yes, this installs everything but you can use root browser (or some other root file manager) and fine tweak the ROM with what you do not want. I had a similar issue but I had NO data/signal/service...nothing. Hope this helps. Just in case, make sure you know how to flash back to stock, should something go wrong. Good luck!
Click to expand...
Click to collapse
I appreciate the help but I can not seem to get my phone to be recognized as a tmobile device. I do not see an option to select tmobile anywhere when flashing.
Thanks
For anybody else having this issue, I just found my problem...
I installed twrp to my device yet was still having the same issue. I realized that while I was installing twrp, the device was still reading as a sprint variant because I was on the flashed rom that detected my device that way in the first place. I flashed a recovery via odin specifically for my tmobile s3 and got right to where I needed to be. All issues fixed and rom is running perfectly! :good:
Twisted Tom said:
I appreciate the help but I can not seem to get my phone to be recognized as a tmobile device. I do not see an option to select tmobile anywhere when flashing.
Thanks
Click to expand...
Click to collapse
I had the same problem with my d2tmo with Slim and Syn. Both use a single rom for both AT&T and T-Mobile since the devices are very similar. I had to use Build.Prop Editor to change the values in the build.prop file to change from AT&T to T-Mobile values. However doing so will cancel out OTA updates and will have to update manually. I ended up going back to CM 10.1 nightly builds (slim/syn is based off cm anyways) and changed my LCD density in the build.prop and added a majority of the mods Slim/Syn uses.
Sent from my SGH-T999 using xda app-developers app

Virus???? Idk but phone is messed up

Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work

[Q] Can't Last One Day with a Custom ROM

Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!

LG G3 from FreedomPop, marshmallow or rom?

So i bought a FreedomPop LG G3 on sale and i ended up activating it to FreedomPop and i rooted it, and im wondering if i can install Marshmallow or cygn on it, my concern is.. before i bought the LG G3 i had a first Gen MOTO G from TextNow with there own unique ROM and when i installed lollipop on it, since the phone has no sim card the phone lost connection to TextNow and was basically useless outside the house so i had to ask TextNow to send me their unique Rom which they did and after installing it everything came back to normal.
now my lg g3 has a sim card slot, and came with sprint apps on it and showing sprint on lockscreen and everything. calls can be made from the android call app but texts messages are only available through FreedomPop text app.
i asked FreedomPop to unlock my phone and they said no problem doing it for me but i ended up not doing it since i do want to stay with them but then i want a different ROM.
so my questions are:
1.is there a way to backup an stock rom that came with the device so i can restore it just like i did on my TextNow incase i lose connection like before?
2.is there a way to backup FreedomPop like apps and restore it after changing the rom? will they work after installing them?
3.should i install a different rom?
4.anyone had an experience with such "locked" phones or even FreedomPop phone and can tell me how did it work for him?
shayo said:
So i bought a FreedomPop LG G3 on sale and i ended up activating it to FreedomPop and i rooted it, and im wondering if i can install Marshmallow or cygn on it, my concern is.. before i bought the LG G3 i had a first Gen MOTO G from TextNow with there own unique ROM and when i installed lollipop on it, since the phone has no sim card the phone lost connection to TextNow and was basically useless outside the house so i had to ask TextNow to send me their unique Rom which they did and after installing it everything came back to normal.
now my lg g3 has a sim card slot, and came with sprint apps on it and showing sprint on lockscreen and everything. calls can be made from the android call app but texts messages are only available through FreedomPop text app.
i asked FreedomPop to unlock my phone and they said no problem doing it for me but i ended up not doing it since i do want to stay with them but then i want a different ROM.
so my questions are:
1.is there a way to backup an stock rom that came with the device so i can restore it just like i did on my TextNow incase i lose connection like before?
2.is there a way to backup FreedomPop like apps and restore it after changing the rom? will they work after installing them?
3.should i install a different rom?
4.anyone had an experience with such "locked" phones or even FreedomPop phone and can tell me how did it work for him?
Click to expand...
Click to collapse
If it has sprint apps it is probably an ls990; check in "about phone" settings to make sure. So basically follow the ls990 thread(s) to see how to get recovery on it... http://forum.xda-developers.com/sprint-lg-g3 . Since you have root already installing a recovery should be a simple process via flashify or autorec apps - but you need to absolutely make sure you install the correct recovery file with the bump exploit or you may softbrick and have to restore with a PC. (bump is an lg g3 exploit needed for our device as we don't have a true bootloader unlock)
Re #1: if/when you put TWRP recovery on your phone you can make a backup of your freedompop stock ROM so you can restore it if you need to.
Re #2: since you're rooted you can backup all of your apps and their data with titanium or something similar. I use titanium pro because it allows you to make a zip file you can flash in TWRP while flashing your ROM, gapps, etc. & it restores your app data too; super convenient time saver. As far as will the freedompop apps work on a different ROM - they should; trying to restore them and see if they work might be the best way to go there. As long as you have a ROM backup you can restore - why not give em a try?
Re #3: that's subjective and up to you. Some people prefer stock features(especially the camera) and some xposed mods to get some extra tweaks, some people prefer custom ROMs with tons of features and the newest Android version. Again, that's on you to decide. BTW, if you do go custom ROM there are decent camera ports available that come close to stock quality.
Re #4: I have not, but I'm guessing you may need to take note of your APN settings before you change ROMs as they may be unique to freedompop & could mess up your data/text if they are not set right. That seems to be the biggest issue with people using different carriers.
Good luck & hope you enjoy your G3
LS990ZVC
Hey and thanks for your reply, yes my phone is the ls990ZVC (by the way on phone settings under brand it says "sprint" and not FreedomPop)
Q1.what do you mean by get recovery? you mean a costume recovery program on the devices main boot in-case of a problem that will replace the original recovering stock program?
Q#1. the thread you posted is for unlocking the phone? what benefits do i get from it? will i lose the 4G LTE speed like it says on the thread if i do it?
Q#2.i dont care much about camera features and also not looking for a lot of tweaks all i look for is to keep my ram and cpu power low and there for available at all time so basically having the phone act and react as fast as possible. can i achieve that with one of the different roms or having stock marshmallow installed?
Q#3. where do i get my APN settings?
Q#4. I think i know the answer to this but ill ask anyway, having TWRP recovery can save my device from softbrick right?
startswithPendswithOOH said:
If it has sprint apps it is probably an ls990; check in "about phone" settings to make sure. So basically follow the ls990 thread(s) to see how to get recovery on it... http://forum.xda-developers.com/sprint-lg-g3 . Since you have root already installing a recovery should be a simple process via flashify or autorec apps - but you need to absolutely make sure you install the correct recovery file with the bump exploit or you may softbrick and have to restore with a PC. (bump is an lg g3 exploit needed for our device as we don't have a true bootloader unlock)
Re #1: if/when you put TWRP recovery on your phone you can make a backup of your freedompop stock ROM so you can restore it if you need to.
Re #2: since you're rooted you can backup all of your apps and their data with titanium or something similar. I use titanium pro because it allows you to make a zip file you can flash in TWRP while flashing your ROM, gapps, etc. & it restores your app data too; super convenient time saver. As far as will the freedompop apps work on a different ROM - they should; trying to restore them and see if they work might be the best way to go there. As long as you have a ROM backup you can restore - why not give em a try?
Re #3: that's subjective and up to you. Some people prefer stock features(especially the camera) and some xposed mods to get some extra tweaks, some people prefer custom ROMs with tons of features and the newest Android version. Again, that's on you to decide. BTW, if you do go custom ROM there are decent camera ports available that come close to stock quality.
Re #4: I have not, but I'm guessing you may need to take note of your APN settings before you change ROMs as they may be unique to freedompop & could mess up your data/text if they are not set right. That seems to be the biggest issue with people using different carriers.
Good luck & hope you enjoy your G3
Click to expand...
Click to collapse
Anyone?
shayo said:
Hey and thanks for your reply, yes my phone is the ls990ZVC (by the way on phone settings under brand it says "sprint" and not FreedomPop)
Q1.what do you mean by get recovery? you mean a costume recovery program on the devices main boot in-case of a problem that will replace the original recovering stock program?
Q#1. the thread you posted is for unlocking the phone? what benefits do i get from it? will i lose the 4G LTE speed like it says on the thread if i do it?
Q#2.i dont care much about camera features and also not looking for a lot of tweaks all i look for is to keep my ram and cpu power low and there for available at all time so basically having the phone act and react as fast as possible. can i achieve that with one of the different roms or having stock marshmallow installed?
Q#3. where do i get my APN settings?
Q#4. I think i know the answer to this but ill ask anyway, having TWRP recovery can save my device from softbrick right?
Click to expand...
Click to collapse
Hey...sorry I missed the notification that you responded...my bad.
Recovery - TWRP recovery which allows you to backup your current ROM, wipe your device, and install ROMs. You have to have it installed if you want to run any custom ROMs. It is imperative that you use the correct file or you may bork all your software, softbrick, and re-flash on a PC. If you are unsure on how to install TWRP then read, read & ask questions in the appropriate forums - & watch youtube videos if you need guidance on how to install it.
The link I posted was for your device. You can search in the threads for anything from ROMs, TWRP, root, kernels, and troubleshooting if you get stuck.
Stock marshmallow is pretty quick & there are some pure AOSP or basic CM builds available that may suit your needs...just have to sample for yourself to see what's best.
APN settings: settings, cellular networks, access point names; if you see a feedompop apn(or anything that isn't sprint) write down the fields, or take a screenshot and email it to yourself for reference.
Having TWRP recovery saves you from your mistakes. Once you get it installed you can make backups that you can always restore if you experiment with new ROMs or tweaks, etc. It is the backbone of flashing and modifying your phone.
Again, sorry for leaving you hanging. I'll pay closer attention to my notifications in the future
startswithPendswithOOH said:
Hey...sorry I missed the notification that you responded...my bad.
Recovery - TWRP recovery which allows you to backup your current ROM, wipe your device, and install ROMs. You have to have it installed if you want to run any custom ROMs. It is imperative that you use the correct file or you may bork all your software, softbrick, and re-flash on a PC. If you are unsure on how to install TWRP then read, read & ask questions in the appropriate forums - & watch youtube videos if you need guidance on how to install it.
The link I posted was for your device. You can search in the threads for anything from ROMs, TWRP, root, kernels, and troubleshooting if you get stuck.
Stock marshmallow is pretty quick & there are some pure AOSP or basic CM builds available that may suit your needs...just have to sample for yourself to see what's best.
APN settings: settings, cellular networks, access point names; if you see a feedompop apn(or anything that isn't sprint) write down the fields, or take a screenshot and email it to yourself for reference.
Having TWRP recovery saves you from your mistakes. Once you get it installed you can make backups that you can always restore if you experiment with new ROMs or tweaks, etc. It is the backbone of flashing and modifying your phone.
Again, sorry for leaving you hanging. I'll pay closer attention to my notifications in the future
Click to expand...
Click to collapse
So i went with liquid smooth rom and after having some issues with titanium backup restoring apps i tried a few things and ended up having all system apps crashing on boot (dialer etc...) so i restored back to stock rom and everything works fine but now when i wanted to go back to liquid smooth TWRP says i cant and that the install files might be incomplete, actually it says that way about gapps too.. why is that? also having the problems i just mentioned with the rom, does that mean the rom is not stable.. or it is something i did? should i even try going back to that rom? i mean i kind of liked it in the 2 hours i got to test it before everything crashed. i went throught the link you sent me and eventually figured out that there is a rom section on top of the page where i can actually see the roms which i didnt realize that before, seems like restoring function on TWRP works great but i wish there was a way to just know which rom would work best for my phone in terms of performance which is what im looking for.
shayo said:
So i went with liquid smooth rom and after having some issues with titanium backup restoring apps i tried a few things and ended up having all system apps crashing on boot (dialer etc...) so i restored back to stock rom and everything works fine but now when i wanted to go back to liquid smooth TWRP says i cant and that the install files might be incomplete, actually it says that way about gapps too.. why is that? also having the problems i just mentioned with the rom, does that mean the rom is not stable.. or it is something i did? should i even try going back to that rom? i mean i kind of liked it in the 2 hours i got to test it before everything crashed. i went throught the link you sent me and eventually figured out that there is a rom section on top of the page where i can actually see the roms which i didnt realize that before, seems like restoring function on TWRP works great but i wish there was a way to just know which rom would work best for my phone in terms of performance which is what im looking for.
Click to expand...
Click to collapse
ended up having all system apps crashing on boot
My guess is maybe you included system apps in your titanium backup? They are the ones listed in red; you don't want to include any system apps in your app restore/update.zip because they may be incompatible with the ROM you are flashing. So unless you read in the liquid smooth thread of other users having issues, I would doubt the ROM itself caused things to crash.
As far as the TWRP error about incomplete files...I'm not quite sure what that means. But you can take a screenshot while in TWRP(vol down + power) and post it up here to better explain the issue.
If you want to try liquid again try a fresh download of the ROM and fresh download of gapps(make sure you're downloading the correct gapps - LP & MM use different ones). If you run into problems with crashes again, try and flash just the ROM by itself to help determine if the errors are caused by the ROM or the gapps you're using.
I like liquid smooth...used to use it on my galaxy nexus back in the day. There are lots of good ones out there, itjust depends what you like. I usually use Tesla(aosp), but aokp and turbo are both really nice too. If you prefer CM based ROMs there are a ton of them too. Pick your poison.
So to clarify: it sounds like you did everything right - except don't restore system apps with titanium, make sure your gapps are compatible with your ROM, and have fun flashing

Categories

Resources