Related
exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
crazyg0od33 said:
exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
Click to expand...
Click to collapse
Flash a new ROM clean. Hey at least you got past soff finally. Good chance your nandroid is corrupt. Just download a new ROM and flash it. Perhaps a bad download on the other one or perhaps you have an outage near you.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
Flash a new ROM clean. Hey at least you got past soff finally. Good chance your nandroid is corrupt. Just download a new ROM and flash it. Perhaps a bad download on the other one or perhaps you have an outage near you.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
my nandroid is fine - immediately loaded up 4g no problem. I'm now on the GPE and it's working better. may have been a bad install. May flash to an AOSP tomorrow though since it's got more customization than the GPE rom...
crazyg0od33 said:
my nandroid is fine - immediately loaded up 4g no problem. I'm now on the GPE and it's working better. may have been a bad install. May flash to an AOSP tomorrow though since it's got more customization than the GPE rom...
Click to expand...
Click to collapse
That's good to hear. Hopefully the rest of those having issues get them worked out.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
That's good to hear. Hopefully the rest of those having issues get them worked out.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
yeah I'm flashing LiquidSmooth right now, best I've tried so far (havent tried CM 10.2 yet, may do that next) but We'll see if this one runs better for me now
crazyg0od33 said:
exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
Click to expand...
Click to collapse
I am having the exact same problem, except i dont have a nandroid of Stock ROM because a i bought the phone with everything done, and no nandroid of the stock system.
I am currently on a Stock rom (http://forum.xda-developers.com/showthread.php?t=2485319)
Deodexed and debloated.
But i have tried every ROM out there for the Verizon model.
Im upset about it, cuz i was so excited to get off the Gnex and on to something new,
but no 4G just sucks :\
Can someone please help?
Thanks
collinjm01 said:
I am having the exact same problem, except i dont have a nandroid of Stock ROM because a i bought the phone with everything done, and no nandroid of the stock system.
I am currently on a Stock rom (http://forum.xda-developers.com/showthread.php?t=2485319)
Deodexed and debloated.
But i have tried every ROM out there for the Verizon model.
Im upset about it, cuz i was so excited to get off the Gnex and on to something new,
but no 4G just sucks :\
Can someone please help?
Thanks
Click to expand...
Click to collapse
flash back to a sense rom, it should reset the LTE signal (did for me) and then flash another AOSP if you want an AOSP rom
crazyg0od33 said:
flash back to a sense rom, it should reset the LTE signal (did for me) and then flash another AOSP if you want an AOSP rom
Click to expand...
Click to collapse
I am on stock rom, no LTE still
I am on Vzw :\
I have run into this problem before going from sense to AOSP on the One, the Rezound also suffered from this. I have done this multiple times for both devices with 100% success, unfortunately a full wipe is required.
-Change your custom recovery to the stock recovery
-Factory reset from H-Boot, I usually do this twice
-This at least for me clears up data issues, and for some reason only factory reset from H-Boot seems to work. Custom recoveries do not clear the affected radio caches
lancasterv3 said:
I have run into this problem before going from sense to AOSP on the One, the Rezound also suffered from this. I have done this multiple times for both devices with 100% success, unfortunately a full wipe is required.
-Change your custom recovery to the stock recovery
-Factory reset from H-Boot, I usually do this twice
-This at least for me clears up data issues, and for some reason only factory reset from H-Boot seems to work. Custom recoveries do not clear the affected radio caches
Click to expand...
Click to collapse
Thats what i am unsure of, I dont know how to do this.
I have flashed a Radio RUU and custom roms on recovery on
this phone. But the phone already had all this done.
Pointing me in the right direction would be Super helpful
Thanks
collinjm01 said:
Thats what i am unsure of, I dont know how to do this.
I have flashed a Radio RUU and custom roms on recovery on
this phone. But the phone already had all this done.
Pointing me in the right direction would be Super helpful
Thanks
Click to expand...
Click to collapse
The radio RUU is just that only the Radio's, if you have received this handset with most of the work done (S-Off) I would assume it had not been factory reset from Hboot after doing this. I had read that the S-Off process could affect data and it was good practice to factory reset from Hboot after completing S-Off. All that being said I have always been on a Sense ROM when doing this, as a warning back up anything you cherish...... for this wipes **INTERNAL STORAGE!!**
Go to Zarboz's decrypted RUU
http://forum.xda-developers.com/showthread.php?t=2437436
-Download either .08 or the .10 DECRYPTED RUU
-Unzip it and find the recovery signed.img file
-Replace your custom recovery (CWM, TWRP) with the above recovery.
-Go to Settings>Power> Deselect the fast-boot option.
-Reboot into HBoot
-Select Factory Reset from the options
-Let it do its thing, when the One boots up do not worry about setting up accounts or anything because you are going to boot back into HBoot and do another factory reset, again uncheck fast-boot. I know this seems like overkill but considering you have already gone through all of this why not just wipe it again for good measure.
-Once all of this is done push your custom recovery
-Flash away and enjoy.
-Now this method will not help if you have fried your SIM card by doing a tower update (*228).
lancasterv3 said:
The radio RUU is just that only the Radio's, if you have received this handset with most of the work done (S-Off) I would assume it had not been factory reset from Hboot after doing this. I had read that the S-Off process could affect data and it was good practice to factory reset from Hboot after completing S-Off. All that being said I have always been on a Sense ROM when doing this, as a warning back up anything you cherish...... for this wipes **INTERNAL STORAGE!!**
Go to Zarboz's decrypted RUU
http://forum.xda-developers.com/showthread.php?t=2437436
-Download either .08 or the .10 DECRYPTED RUU
-Unzip it and find the recovery signed.img file
-Replace your custom recovery (CWM, TWRP) with the above recovery.
-Go to Settings>Power> Deselect the fast-boot option.
-Reboot into HBoot
-Select Factory Reset from the options
-Let it do its thing, when the One boots up do not worry about setting up accounts or anything because you are going to boot back into HBoot and do another factory reset, again uncheck fast-boot. I know this seems like overkill but considering you have already gone through all of this why not just wipe it again for good measure.
-Once all of this is done push your custom recovery
-Flash away and enjoy.
-Now this method will not help if you have fried your SIM card by doing a tower update (*228).
Click to expand...
Click to collapse
Dude you are freaking amazing!!!
Funny thing, i used Flashify to to flash the img
file and rebooted the system, it showed
a phone with a loading bar, it did its thing,
then rebooted, went into the OS and 4G
is working!
Thank you so much man!
Flashify eliminates pushing ,a great tool. If you have Flashify and also Meenova SD card reader you never have to mess with adb and fastboot again. Two great tools.
sent from my HTC One
collinjm01 said:
Dude you are freaking amazing!!!
Funny thing, i used Flashify to to flash the img
file and rebooted the system, it showed
a phone with a loading bar, it did its thing,
then rebooted, went into the OS and 4G
is working!
Thank you so much man!
Click to expand...
Click to collapse
no problem i am glad this took care of it for you.
Sent from my HTC6500LVW using Tapatalk
jbh00jh said:
Flashify eliminates pushing ,a great tool. If you have Flashify and also Meenova SD card reader you never have to mess with adv and fastboot again. Two great tools.
sent from my HTC One
Click to expand...
Click to collapse
I used flashify for it, I love that app
Sent from my HTC6500LVW using xda app-developers app
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
latrotoxin1986 said:
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
iamterence said:
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
I'm not sure how root would pertain to this issue. I'll give Stocktimus a try, but I tried engine's other stock ROM's a month or so back and had the exact same issue.
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
AFschizoid said:
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
The phone is activated, but trying to run the activation in settings causes reboot. Receives phone calls no problem. Just downloaded Stocktimus O and same thing. No data, crash on PRL update or Profile update, crash on WiFi activation. I really don't understand what's going on...
Yeah I've not had that issue and I've flashed back and forth from stock based to aosp and vice versa. Might be your efs got screwed up. Try lgnpst or LG flash tool (I prefer the latter because it takes it to an 'out of the box' state, activation required ) and try activating again
Sent from my Optimus G using Tapatalk
That has happened to me before going from an AOSP rom to one of the available stock roms. Don't remember which one.
But I remember flashing the TWRP recovery. I was on Philz Touch Clockworkmod.
And then performed all the required wipes and reset then flashed Stockimus-D and viola, no FC's. no reboots. No more problems.
If problems persist used TeenyBins via LGNPST
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
latrotoxin1986 said:
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
Click to expand...
Click to collapse
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
engine95 said:
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
Click to expand...
Click to collapse
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
latrotoxin1986 said:
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
Click to expand...
Click to collapse
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
engine95 said:
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
Click to expand...
Click to collapse
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
latrotoxin1986 said:
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
Click to expand...
Click to collapse
I had the reboot issue when it connected to data too when flashing back and forth from cm/aosp ROMs to stock. What resolves the issue for me is to use TWRP and go to advanced wrote and wipe everything EXCEPT internal. I used to have that issue all the time when using cwm recovery but philz recovery also seems to be ok when flashing back and forth hope this helps!
Sent from my LG-LS970 using XDA Premium 4 mobile app
Hey everyone,
Greetings from Jamaica!
I've had my e980 OGP for about 2 months now
When I got it, it was running the 10p firmware. After a while, I realized that i'm having random mobile network drops, sometimes I get a good signal, sometimes I don't, sometimes it goes and comes. I was advised to flash a custom rom, I rooted using the VROOT method, installed freegee from the play store and flashed cwm. I then flashed cm11. When I flashed cm11, it worked perfectly! after about 5-10 mins of first-time-use setting up, it froze, then started rebooting, after that it randomly rebooted constantly for the remainder of that day. after trying various custom roms, I decided to flash back to stock, but I flashed the kit kat stock firmware using the Flash Tool and the TOT file. Once v20g was up and running, the reboots stopped, but the signal issues came back, I'm clueless as to what would cause my issue, but I'm confident I can get some answers from the geniuses here, so plz, help a brotha out?
Any help? :fingers-crossed:
YOu could try changing the modem/baseband, there are a few floating around that you could flash.
luisoman2000 said:
YOu could try changing the modem/baseband, there are a few floating around that you could flash.
Click to expand...
Click to collapse
Ok Thanks much. Is there a possible diagnosis for the random reboots in cm11? maybe a custom kernel could fix, or is there a flashable version of the e98020g kernel that I could flash on cm11 to make it... stop rebooting I guess? I'm kinda noob with this phone
blazin876 said:
Ok Thanks much. Is there a possible diagnosis for the random reboots in cm11? maybe a custom kernel could fix, or is there a flashable version of the e98020g kernel that I could flash on cm11 to make it... stop rebooting I guess? I'm kinda noob with this phone
Click to expand...
Click to collapse
Dunno, i don't use AOSP based roms, prefer the stock look.
Any fixes?
I realize that no matter which custom rom I try, I still end up with random reboots. @madmack is there anything that could be done to stop the reboots? I tried flashing that stock kernel you made for kitkat onto PacMan but i'm stuck at the LG Logo. Any help? Please?:crying::crying::crying:
blazin876 said:
I realize that no matter which custom rom I try, I still end up with random reboots. @madmack is there anything that could be done to stop the reboots? I tried flashing that stock kernel you made for kitkat onto PacMan but i'm stuck at the LG Logo. Any help? Please?:crying::crying::crying:
Click to expand...
Click to collapse
Any Ideas?
blazin876 said:
Any Ideas?
Click to expand...
Click to collapse
When you install custom roms, do you make a complete wipe of your system,including factory reset?
blitzkriegger said:
When you install custom roms, do you make a complete wipe of your system,including factory reset?
Click to expand...
Click to collapse
Using CWM, I wipe data/factory reset + Wipe Cache + Wipe Dalvic Cache
Use hacked twrp and make sure you wipe it clean ..completely clean. Install ROM .. Gapps.. And boot up ... Run build m8 or m9 cm.... But I run stock kk due to deep sleep issues for a lot of our Roms... Some get deep sleep and some don't ... But stock kk is where its at for me
2SHAYNEZ
Since day one I had this , well..., phone, I had signal drops to-noservices.
AT&T and rogers, I barely use this phone, since I had it, only problems.
To double-down on what Shayne said, wipe SYSTEM as well, when jumping between AOSP/LG sources or JB and KK. Have you altered preferred network or APN at all? Leaving the defaults delivers the best stability if you're on AT&T. Finally, if you click settings--> mobile data --> menu, there are background data/auto-sync data options buried in there.
Sent from my Nexus 7 using Tapatalk
JCred said:
To double-down on what Shayne said, wipe SYSTEM as well, when jumping between AOSP/LG sources or JB and KK. Have you altered preferred network or APN at all? Leaving the defaults delivers the best stability if you're on AT&T. Finally, if you click settings--> mobile data --> menu, there are background data/auto-sync data options buried in there.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ok, Thanks for the tips, I just flashed the most recent CM11 release using all the directions I got here so hopefully it works. I'm in Jamaica and so I dont have access to AT&T lol. CM11 gives perfect stability as it relates to mobile network tho...
[EDIT] I still get random reboots, apparently less frequent tho
Thanks for xda members bofiana and Shehwaz for tinkering around and finding the fix!!
So the issue is how some members are reporting that their G3's after Lollipop installed via Autoprime's lollipop zip, stock lollipop untouch zip via twrp and KDZ, or pretty much and Lollipop upgrade; LTE is not sticking after reboot,standby for a couple hours, lost connection, airplane mode, and etc.. LTE would always switch back to gsm/wcdma by itself after rebooting,standby for a couple hours, lost connection, airplane mode, and etc.. Even after KDZ,TOT,TWRP restore stock zip to other firmwares like 10c,10m,10r, and 20b the issue is still present. Weirdly enough the only way to get LTE to stick was to flash BlissPop 2.3 rom. Once Blisspop was installed LTE would always stick and never switch back to wcdma/gsm! Here are my steps and the steps of bofiana and Shehwaz to get LTE back to stick.
Make sure you are rooted and have TWRP recovery installed before proceeding!
1.) Go get the Blisspop 2.3 rom, no need for Gapps, Put that rom on your EXTERNAL SD card
2.) Go to TWRP recovery and Backup your current rom (cache and efs is not needed so don't put a check mark on those) to your EXTERNAL SD card and reboot back to recovery
3.) Once back in TWRP recovery fctory wipe and advance wipe everything except for the EXTERNAL SD card since the BLisspop rom is on that and also your backup
4.) Then install Blisspop 2.3 rom
5.) Once booted into Blisspop 2.3 you will noticed in Mobile Network Setting that LTE is selected and even after a reboot LTE is still selected
6.) Once that is confirmed boot back into TWRP and restore your backup from before
7.) Once restore is finish go the mobile network settings and confirmed that LTE is selected by default if that is the case reboot your G3 again and check again to see if LTE is still selected and if it is the LTE switching problem is now fixed!!!!
NOTE:
If you want a clean install you do not need to backup your current rom, instead download the 20b stock untouched zip and just flash that after flashing Blisspop. Remember flashing the 20b untouched stock rom will get rid of TWRP and Root so if you want TWRP and root remember to do that after.
Also this fixed worked for us and I can't guarantee that it will work for all Lollipop LTE issues, but this is pretty safe bet to try if you are experiencing the LTE switch issues and no harm in trying!
Links:
Blisspop 2.3 rom: (By the way any version of Blisspop will work as I just tested out some of the latest Builds and LTE is still good)
http://forum.xda-developers.com/tmobile-lg-g3/development/rom-1-11-15-t3000137
Untouched Stock 20b zip:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
vel0city said:
Thanks for xda members bofiana and Shehwaz for tinkering around and finding the fix!!
So the issue is how some members are reporting that their G3's after Lollipop installed via Autoprime's lollipop zip, stock lollipop untouch zip via twrp and KDZ, or pretty much and Lollipop upgrade method besides OTA (which is stil no go yet); LTE is not sticking after reboot,standby for a couple hours, lost connection, airplane mode, and etc.. LTE would always switch back to gsm/wcdma by itself after rebooting,standby for a couple hours, lost connection, airplane mode, and etc.. Even after KDZ,TOT,TWRP restore stock zip to other firmwares like 10c,10m,10r, and 20b the issue is still present. Weirdly enough the only way to get LTE to stick was to flash BlissPop 2.3 rom. Once Blisspop was installed LTE would always stick and never switch back to wcdma/gsm! Here are my steps and the steps of bofiana and Shehwaz to get LTE back to stick.
Make sure you are rooted and have TWRP recovery installed before proceeding!
1.) Go get the Blisspop 2.3 rom, no need for Gapps, Put that rom on your EXTERNAL SD card
2.) Go to TWRP recovery and Backup your current rom (cache and efs is not needed so don't put a check mark on those) to your EXTERNAL SD card and reboot back to recovery
3.) Once back in TWRP recovery fctory wipe and advance wipe everything except for the EXTERNAL SD card since the BLisspop rom is on that and also your backup
4.) Then install Blisspop 2.3 rom
5.) Once booted into Blisspop 2.3 you will noticed in Mobile Network Setting that LTE is selected and even after a reboot LTE is still selected
6.) Once that is confirmed boot back into TWRP and restore your backup from before
7.) Once restore is finish go the mobile network settings and confirmed that LTE is selected by default if that is the case reboot your G3 again and check again to see if LTE is still selected and if it is the LTE switching problem is now fixed!!!!
NOTE:
If you want a clean install you do not need to backup your current rom, instead download the 20b stock untouched zip and just flash that after flashing Blisspop. Remember flashing the 20b untouched stock rom will get rid of TWRP and Root so if you want TWRP and root remember to do that after.
Also this fixed worked for us and I can't guarantee that it will work for all Lollipop LTE issues, but this is pretty safe bet to try if you are experiencing the LTE switch issues and no harm in trying!
Links:
Blisspop 2.3 rom:
http://forum.xda-developers.com/tmobile-lg-g3/development/rom-1-11-15-t3000137
Untouched Stock 20b zip:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
I am trying this method...
Worked for me, but i didn't do an advance wipe just a factory reset on step 3. When i loaded blissrom, it defaulted to 3g so i changed it to LTE.
Rebooted into recovery and restored the lollipop backup . LTE is now the default and working after rebooting. Thanks :highfive:
Thanks for mentioning me! I was getting really annoyed at the fact LTE wouldn't stick because I use Skype in the car a lot to speak to my S.O. and it would keep defaulting back to 4G whenever we hit a dead zone. I got mad and decided to try to see if going back to 10C fixed the issue and to no avail it didn't. I then went to blisspop rom and saw that it was working fine so then I was like let me try going to 20B now and see how that goes and voila it worked. Thanks for tinkering around some more and giving people a better answer than I did. You're doing the community a huge favor and I really appreciate it.
gaby04 said:
Worked for me, but i didn't do an advance wipe just a factory reset on step 3. When i loaded blissrom, it defaulted to 3g so i changed it to LTE.
Rebooted into recovery and restored the lollipop backup . LTE is now the default and working after rebooting. Thanks :highfive:
Click to expand...
Click to collapse
Hey glad it worked out for you!! Yeah this LTE issue was a headache!
Shehwaz said:
Thanks for mentioning me! I was getting really annoyed at the fact LTE wouldn't stick because I use Skype in the car a lot to speak to my S.O. and it would keep defaulting back to 4G whenever we hit a dead zone. I got mad and decided to try to see if going back to 10C fixed the issue and to no avail it didn't. I then went to blisspop rom and saw that it was working fine so then I was like let me try going to 20B now and see how that goes and voila it worked. Thanks for tinkering around some more and giving people a better answer than I did. You're doing the community a huge favor and I really appreciate it.
Click to expand...
Click to collapse
No problem man it was you who found it out first! So it was only right for me to give you the credit. Hopefully my thread will be make it easier for others in the community to find the fix.
vel0city said:
Thanks for xda members bofiana and Shehwaz for tinkering around and finding the fix!!
So the issue is how some members are reporting that their G3's after Lollipop installed via Autoprime's lollipop zip, stock lollipop untouch zip via twrp and KDZ, or pretty much and Lollipop upgrade method besides OTA (which is stil no go yet); LTE is not sticking after reboot,standby for a couple hours, lost connection, airplane mode, and etc.. LTE would always switch back to gsm/wcdma by itself after rebooting,standby for a couple hours, lost connection, airplane mode, and etc.. Even after KDZ,TOT,TWRP restore stock zip to other firmwares like 10c,10m,10r, and 20b the issue is still present. Weirdly enough the only way to get LTE to stick was to flash BlissPop 2.3 rom. Once Blisspop was installed LTE would always stick and never switch back to wcdma/gsm! Here are my steps and the steps of bofiana and Shehwaz to get LTE back to stick.
works for me now, xda is great . T-mobile tech support sucks.
Make sure you are rooted and have TWRP recovery installed before proceeding!
1.) Go get the Blisspop 2.3 rom, no need for Gapps, Put that rom on your EXTERNAL SD card
2.) Go to TWRP recovery and Backup your current rom (cache and efs is not needed so don't put a check mark on those) to your EXTERNAL SD card and reboot back to recovery
3.) Once back in TWRP recovery fctory wipe and advance wipe everything except for the EXTERNAL SD card since the BLisspop rom is on that and also your backup
4.) Then install Blisspop 2.3 rom
5.) Once booted into Blisspop 2.3 you will noticed in Mobile Network Setting that LTE is selected and even after a reboot LTE is still selected
6.) Once that is confirmed boot back into TWRP and restore your backup from before
7.) Once restore is finish go the mobile network settings and confirmed that LTE is selected by default if that is the case reboot your G3 again and check again to see if LTE is still selected and if it is the LTE switching problem is now fixed!!!!
NOTE:
If you want a clean install you do not need to backup your current rom, instead download the 20b stock untouched zip and just flash that after flashing Blisspop. Remember flashing the 20b untouched stock rom will get rid of TWRP and Root so if you want TWRP and root remember to do that after.
Also this fixed worked for us and I can't guarantee that it will work for all Lollipop LTE issues, but this is pretty safe bet to try if you are experiencing the LTE switch issues and no harm in trying!
Links:
Blisspop 2.3 rom:
http://forum.xda-developers.com/tmobile-lg-g3/development/rom-1-11-15-t3000137
Untouched Stock 20b zip:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
gaby04 said:
Worked for me, but i didn't do an advance wipe just a factory reset on step 3. When i loaded blissrom, it defaulted to 3g so i changed it to LTE.
Rebooted into recovery and restored the lollipop backup . LTE is now the default and working after rebooting. Thanks :highfive:
Click to expand...
Click to collapse
VoLTE working ?
sasidhar79 said:
VoLTE working ?
Click to expand...
Click to collapse
yeah Volte is now working for me, it wasnt working before.
But i believe there are some requirements for VoLTE to work. Im not sure how accurate these articles are, but both have to be on the same network (T-Mo to T-Mo) and calling partner both have to have VoLTE-compatible phones.
https://www.yahoo.com/tech/apple-t-mobile-and-verizon-have-all-in-their-98352646864.html
https://www.yahoo.com/tech/wait-volte-doesnt-work-between-carriers-98414563869.html
gaby04 said:
yeah Volte is now working for me, it wasnt working before.
Click to expand...
Click to collapse
Quick question how do you know if VoLTE is working? I mean I know I have it enabled in the settings but when making a call is there an indication that it is active?
vel0city said:
Quick question how do you know if VoLTE is working? I mean I know I have it enabled in the settings but when making a call is there an indication that it is active?
Click to expand...
Click to collapse
When making a call, check the 4g LTE icon. if it switches to the 4g icon then that means it is not using VoLTE. If the icon stays on 4g LTE, it should be using VoLTE.
gaby04 said:
When making a call, check the 4g LTE icon. if it switches to the 4g icon then that means it is not using VoLTE. If the icon stays on 4g LTE, it should be using VoLTE.
Click to expand...
Click to collapse
Gotcha sweet yeah VoLTE is definitely working on my end too!
Its a no-go for me. Couldn't even get blisspop to stick on LTE ... Only thing I could think of that could be preventing it is that I have zero cell coverage here at the house while attempting. I'll report back tomorrow after I give it a go at the office (where I have very good LTE coverage)
mjfrank said:
Its a no-go for me. Couldn't even get blisspop to stick on LTE ... Only thing I could think of that could be preventing it is that I have zero cell coverage here at the house while attempting. I'll report back tomorrow after I give it a go at the office (where I have very good LTE coverage)
Click to expand...
Click to collapse
Yeah that could be the issue. Also if I may ask which method did you use to update to lollipop?
I tried on both my backup of autoprime's zip compilation and my lg support kdz...no go for both :/
mjfrank said:
I tried on both my backup of autoprime's zip compilation and my lg support kdz...no go for both :/
Click to expand...
Click to collapse
What I did that helped, because I was in the same position as you is that I KDZ'd back to 10C and then rooted via stumproot and installed Blisspop and then I KDZ'd back to 20B and my issue was gone.
mjfrank said:
I tried on both my backup of autoprime's zip compilation and my lg support kdz...no go for both :/
Click to expand...
Click to collapse
Either do what Shehwaz said or you can just kdz with 20b and restore back to stock lollipop. After that root and install twrp, then install Blisspop. Don't restore from your backup from a previous rom. Make sure when you are in Blisspop that LTE stays before flashing stock 20b again. I'm pretty sure that will fix your issue.
Also when you switch to LTE manually does it stay? This method is for those who can at least get their LTE on and stay on when using it, but have it go away either from rebooting or after a long sleep period. If you can't get LTE via manually selecting you have a different issue and this fix might not work.
After flashing blisspop, do I clean flash 20b stock or just flash without wiping?
Papote3 said:
After flashing blisspop, do I clean flash 20b stock or just flash without wiping?
Click to expand...
Click to collapse
Just wipe it to be certain, also before you flash the stock 20b make sure in Blisspop that your LTE is sticking.
vel0city said:
Gotcha sweet yeah VoLTE is definitely working on my end too!
Click to expand...
Click to collapse
VoLTE started to work after the blisspop LTE fix. So both problems are related.
Sent from my LG-D851 using XDA Free mobile app
vel0city said:
Just wipe it to be certain, also before you flash the stock 20b make sure in Blisspop that your LTE is sticking.
Click to expand...
Click to collapse
OK, reporting back:
Clean flash Blisspop (wipe everything but ExtSD)
After trying everything to tick the "LTE bug” in bliss, it never lost LTE (good sign)
Went back to TWRP
wiped everything again except for ExtSD
Flashed 20b Untouched ROM, then SuperSU, then TWRP
after successful boot of 20b, LTE stuck no matter what I tried.
THANKS GUYS, this is awesome
Going to do some more testing tomorrow, but it looks promising
Also, VoLTE didn't work on my first call, but that's probably bc its not activated in my area (Puerto Rico)