Database Info

Used to be able to flash any ROM, now I have problems with every rom!

used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks

boardsportsrule said:
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
Click to expand...
Click to collapse
Find the modem cognition uses that gives you the least problems. Are you flashing to stock before each ROM?
Sent from my SAMSUNG-SGH-I897 using XDA App

Yep, back to stock & master cleared between(only once problems arised..back in the day I could just flash to what I wanted and never really had a problem. Went back to stock once when the new flash responded strangely.)
Looking at cognition, I get minimal information, I THINK it's stock radio/kernel..
http://forum.xda-developers.com/showthread.php?t=912657

Any one???

I would..check your usb plug/cable/port first..make sure it isn't bad and effecting your data transfer..Make sure your not plugged into a external port and plug into PC directly..
Re down load your roms and kernels again..keep them separate from what you have already used..
Flash back to stock..master clear delete all data on your internal and your data
Re-install everything over again..cause it sounds like something got corrupted along the way
Mac

Mac11700 said:
it sounds like something got corrupted along the way
Click to expand...
Click to collapse
Thats how I am leaning, but i dont think it's with the roms/kernels/radios i have downloaded...since I have tried so many damn copies that wouldn't make sense. also tried downloading directly to phone, eliminating the "3rd party" computer, and have used drop box in the past...
I have flashed to stock and master cleared, i could do it again, but i am tempted to go back to stock and try to exchange it for a new one due to either random shut-offs or GPS(both of which mine are effected by..) but i would like to avoid this hassle...
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?

boardsportsrule said:
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
Click to expand...
Click to collapse
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).

opcow said:
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
Click to expand...
Click to collapse
hopped back to Stock... Gonna run things here, see which problems arise, and go from there. Can you flash a different kernel onto the stock ROM? I'd assume you need a 2.1 kernel, and i don't think many are retrofitted to 2.1, but the KP1 modem is a good idea, ill let things pan out on stock and see what happens if/when i flash kp1 modem.

funny fact: fire fly made problems for me... it's based on rogers 2.2, same as cognition. that seemed odd to me.

Having problems after official 4.0.4 update via kies

I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?

cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
do a factory reset, or try the odin tar.

I would say use Odin to flash back to 2.3.5 and then take the 2.3.6 ota. If u really want the stock ics released by att you can then try to update again through kies but I would recommend a rom instead.
Sent from my Skyrocket i727 running Sky ICS

cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
I believe u can also go into standard recovery and wipe caches. I heard this can help fix fc issues. Dont do a factory reset in settigs! Can someone confirm cache clear on stock recovery or is cwm necessary. I don't want to steer him wrong.
Sent from my Skyrocket i727 running Sky ICS

Mike on XDA said:
I believe u can also go into standard recovery and wipe caches. I heard this can help fix fc issues. Dont do a factory reset in settigs! Can someone confirm cache clear on stock recovery or is cwm necessary. I don't want to steer him wrong.
Sent from my Skyrocket i727 running Sky ICS
Click to expand...
Click to collapse
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.

popcorn900 said:
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.
Click to expand...
Click to collapse
Source has not been released yet so it can't be known whether the kernels have the brick bug fix. The rule of thumb at least until source comes out is never do any wiping within ics. It will corrupt a partition (I forget which particular one) as the MMC_CAP_ERASE command is giving resulting in something like 20 0's being placed in the partition renderring it useless. If this occurres then nothing (as of now anyway) can repair the phone. No jtag, no USB jig, etc will be able to save it. Samsung was aware of the issue and probably fixed the kernels but until source is dropped better be safe than end up with a paper weight
Sent from my Skyrocket i727 running Sky ICS

popcorn900 said:
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.
Click to expand...
Click to collapse
How do u possibly think roms are bad lol and unless u are simply talking about button mods, changing signal/ battery icon, 14 toggle notification bar and a change in kernel there isn't much the average user will be able to change. Roms are so much better than stock. If u don't feel the same then u must of had difficulties with the particular rom u used or chose an unstable rom. I have had 0 problems on SeanZ Sky ICS....I highly recommend it
Sent from my Skyrocket i727 running Sky ICS

Mike on XDA said:
How do u possibly think roms are bad lol and unless u are simply talking about button mods, changing signal/ battery icon, 14 toggle notification bar and a change in kernel there isn't much the average user will be able to change. Roms are so much better than stock. If u don't feel the same then u must of had difficulties with the particular rom u used or chose an unstable rom. I have had 0 problems on SeanZ Sky ICS....I highly recommend it
Sent from my Skyrocket i727 running Sky ICS
Click to expand...
Click to collapse
that brick bug you talk of is probably non existent with the new samsung releases.
also its been very well observed that mod roms are plagued with problems fc's ect ect.
he can make his stock rom look and feel like Google ice 4.0.4 very easily.
the only thing he needs is a unsecured kernel, then he is on his way.
this is just my opinion.
i have rogers stock 4.0.4 with mohens kernel and a couple of other mods and i have my sgs2 looking exactly like a nexus and everything works as it should no fc's and other crap like that.

popcorn900 said:
that brick bug you talk of is probably non existent with the new samsung releases.
also its been very well observed that mod roms are plagued with problems fc's ect ect.
he can make his stock rom look and feel like Google ice 4.0.4 very easily.
the only thing he needs is a unsecured kernel, then he is on his way.
this is just my opinion.
i have rogers stock 4.0.4 with mohens kernel and a couple of other mods and i have my sgs2 looking exactly like a nexus and everything works as it should no fc's and other crap like that.
Click to expand...
Click to collapse
Key words here are "probably". I agree it is most likely fixed but I don't want to see someone end up with a broken phone because we think Samsung "probably" fixed their kernels.
As for the rom I have not had any fc's lag etc. You can do what you like with your phone I am just merely stating that I have been issue free with Sky ICS as have many others. There is always the chance of issues arising but following instructions and reading the thread will clear up any problems. If u do ur homework ie read and/or ask questions if u don't understand something then many of these problems people have could be avoided IMHO. People on XDA wouldn't constantly be flashing roms if they were all filled with bugs and stock were there best option. Just saying...
For the sake of this thread and helping the OP I will avoid the back and forth about custom rom vs stock as the main point here is to help the OP get his Skyrocket back up and running as it should
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks

Mike on XDA said:
Key words here are "probably". I agree it is most likely fixed but I don't want to see someone end up with a broken phone because we think Samsung "probably" fixed their kernels.
As for the rom I have not had any fc's lag etc. You can do what you like with your phone I am just merely stating that I have been issue free with Sky ICS as have many others. There is always the chance of issues arising but following instructions and reading the thread will clear up any problems. If u do ur homework ie read and/or ask questions if u don't understand something then many of these problems people have could be avoided IMHO. People on XDA wouldn't constantly be flashing roms if they were all filled with bugs and stock were there best option. Just saying...
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
well im happy you satisfied with sky ice. my point if i didn't make it clear is that mod roms use stuff from different roms and phones that don't work right with our phones and there will always be problems with it. it is easier and safer to stick with stock and build it up yourself. i have tried everything out there for my phone and hard bricked it twice and i have come to the conclusion that stock is best but for the kernel a unsecured is a must and maybe a good Governor will help.

cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
You could odin a version of Clockwork Mod onto your phone and wipe the cache and dalvik cache if you want to try saving everything. That would eliminate any concerns about the "brick bug"
Did you do the update install or the wipe install? See this post for info on the different methods.
I suggest that you do the wipe install. You will have to re-install all your apps. It will like setting your phone up when it was new. In many cases an upgrade install will have problems.
.

Thanks alot guys...i wiped data/factory reset, wiped cache, and wiped dalvik cache and flash stock first and then updated it through kies. Its finally working normally

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).

Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix

bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.

Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?

CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol

Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.

CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever

dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?

If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch

dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium

bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time

Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.

CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?

Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.

CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.

Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/

dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium

TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

[Q] Cannot acquire data connections

I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.

TheCing said:
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
Click to expand...
Click to collapse
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).

XdrummerXboy said:
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
Click to expand...
Click to collapse
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.

TheCing said:
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
Click to expand...
Click to collapse
Hmm... ML1 should be new enough.
That's a bizarre issue.
For me, I mainly get 3G. It seems as if either Verizon pulled some LTE towers near me, or my data antenna doesn't have very good contact. Maybe you're having the same issue.
Do you EVER get 4G? Or literally never?

[Q] Why am I not consistently connecting to LTE

Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!

iFrostyy said:
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
Click to expand...
Click to collapse
Are you stock? S-off? Which firmware are you on?

brholt6 said:
Are you stock? S-off? Which firmware are you on?
Click to expand...
Click to collapse
I am s-off and I am on a GPE 5.0.1 ROM.

iFrostyy said:
I am s-off and I am on a GPE 5.0.1 ROM.
Click to expand...
Click to collapse
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk

dottat said:
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.

LibertyMonger said:
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
Click to expand...
Click to collapse
If you flashed the vzw ruu you are no longer on custom firmware.

dottat said:
If you flashed the vzw ruu you are no longer on custom firmware.
Click to expand...
Click to collapse
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.

LibertyMonger said:
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
Click to expand...
Click to collapse
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.

OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!

Croak said:
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Click to expand...
Click to collapse
Think that horse was beat dead already lol
Sent from my SM-T320 using Tapatalk

dottat said:
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
Click to expand...
Click to collapse
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.

LibertyMonger said:
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
Click to expand...
Click to collapse
It was made for the gpe version phones. They weren't sold for vzw.

dottat said:
It was made for the gpe version phones. They weren't sold for vzw.
Click to expand...
Click to collapse
Yeah I think most who are using it are either lucky or do not care or notice the dropped, weak signals. I've tried everything more than once to get it working right and the results are always the same, it acts like it's the wrong firmware, cause it is lol. Some claim to have the same issues but ignore them. I need my phone to work no matter what ROM it is. Thanks for all your help bro I see you are willing to help us when in need, that is greatly appreciated. I hope users send donations your way, I sure will once i get ahead again.

Have you set your APP correctly.

So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.

kj13569 said:
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
Click to expand...
Click to collapse
When you get the red triangle, you press volume up and power to enter stock recovery. Keep practicing.

LTE drops on and off
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?

Flylowguy said:
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Click to expand...
Click to collapse
That signal drop off issue happens to me on gpe ROMs. So far all the cm12 ROMs out there have had a perfect signal with good speeds for me. I think the signal drop off issue is something to do with the gpe ROMs.
Currently running blisspop newest nightly with 4.4.4 straight from RUU.