Related
I'm a total noob but thanks to XDA, and literally hours and hours of reading I was able to flash the original ics leak from DG, the latest 4.0.4 leak, install CWM touch, and successfully root my AT&T skyrocket. Thank you all! However, I am one of the few that have had better data and voice with the ucalc4 radio despite reports to the contrary. I decided to try flashing LeeC's CWM flashable ucalc4 radio after doing a backup. After flashing the zip and rebooting, i was unable to get a signal. The baseband was also listed as "unknown". I tried putting the phone in and out of airplane mode, reinserting the sim and rebooting but to no avail. Finally, I gave up and restored my backup and upon reboot, lo and behold.....under baseband it says ucalc4!!! 4-5 bars of service instead of 1. Signal Strength -85dBm 14asu (not sure what this means and didnt record settings prior to modem flash) and hspap instead of hspa under phone status!! (No LTE in my area). I'm completely dumfounded now. How did the ucalc4 modem stick, after restoring from backup.??? I would think the default ucle2 modem would have been restored (not complaining though). Sorry for being such a noob and look forward to responses such as..."Post in the right section noob" or "for cryin' out loud, do a search!!"
The radio is not backed up or restored in CWM.
Ril mismatch was your experience.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Ends said:
Ril mismatch was your experience.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. So in order to reconcile this for future reference, I would need to flash a radio with no ril, such as the ones posted in the Embryo rom thread?
pinoyscorpion951 said:
Thanks for the response. So in order to reconcile this for future reference, I would need to flash a radio with no ril, such as the ones posted in the Embryo rom thread?
Click to expand...
Click to collapse
If you're going to flash radios from different basebands. IIRC you just remove the system folder from the zip
what is the latest modem that's out for the droid charge and does anyone have an odin file for it? i'd prefer to not have to reload my phone totally just to get the latest.. currently running eclipse rom 2.0
leaveone said:
what is the latest modem that's out for the droid charge and does anyone have an odin file for it? i'd prefer to not have to reload my phone totally just to get the latest.. currently running eclipse rom 2.0
Click to expand...
Click to collapse
FP5 stock only.
so there's no installable file for just the modem then? just gotta take the OTAs and go from there?
leaveone said:
so there's no installable file for just the modem then? just gotta take the OTAs and go from there?
Click to expand...
Click to collapse
hmm... not sure. I vaguely recall someone putting the modems out somewhere, but maybe that was for FP1. maybe someone a little more experienced can chime.
sorry I could not be of any more help.
I believe I remember a patch being posted. There are no full modems for anything newer than EP4. Also, if I'm not mistaken, your signal bars will not work if you are running FP5 modems with an FP1 rom, due to the differences in the way the signal is reported.
If you ODIN the EP4 modems, there are modem updater zips you can use (CWM flashable) to go from EP4 to FP1, and then FP1 to FP5. If you are an Eclipse 2, then you are likely on FP1 (maybe anyway) and all you need is the FP1 to FP5 modem updater. That being said, if you are an FP1 build (which Eclipse 2.0 is) the signal strength reporting will be wonky when using FP5 modems. From what I understand actual connectivity isn't affected, just how the system presents the strength of that connectivity. Here is a link to it (ironically it was in the OP of the Tweaked 3 thread).
EDIT: In other words - what shrike78 said
Yup, tried all combos myself. Good.
Sent from my SCH-I510 using xda premium
Thanks guys! I am on FP1 Eclipse Rom 2.0. Whichever modem I currently had was constantly going in and out so I reflashed the newest one that I had, which was EP4, so that's what I have now. Where is this modem updater to go from EP4 to FP1? If I can get to FP1, I'll likely just stay there to avoid the signal reporting issues on FP5.
leaveone said:
Thanks guys! I am on FP1 Eclipse Rom 2.0. Whichever modem I currently had was constantly going in and out so I reflashed the newest one that I had, which was EP4, so that's what I have now. Where is this modem updater to go from EP4 to FP1? If I can get to FP1, I'll likely just stay there to avoid the signal reporting issues on FP5.
Click to expand...
Click to collapse
I'm pretty sure this is what you're looking for - lemme know if there's a problem with it.
Thanks guys! I was able to update the modem to FP1 with the tool that dwitherell linked to. My phone still does drop signal from time to time.. maybe it's just an issue in the area I live or just that the phone has had a year of use on it..
leaveone said:
Thanks guys! I was able to update the modem to FP1 with the tool that dwitherell linked to. My phone still does drop signal from time to time.. maybe it's just an issue in the area I live or just that the phone has had a year of use on it..
Click to expand...
Click to collapse
then perhaps you'll need to up it to FP5...
You can nandroid, flash factory EP4D with Odin, take both OTA's, Odin Tweaked with recovery, then restore nandroid.
Just an option
Sent from my Nexus 7 using Tapatalk 2
I'm tired of dealing with this flash ep4 stock, then update twice. I don't know how it's going to work out, but I'm trying to figure out how to pull the FP5E modems off of it. So far, all I'm getting is the LTE portion, not the CDMA portion. But then, I'm not done screwing around with it just yet. Hopefully I can figure out an odin file.
edji-x said:
I'm tired of dealing with this flash ep4 stock, then update twice. I don't know how it's going to work out, but I'm trying to figure out how to pull the FP5E modems off of it. So far, all I'm getting is the LTE portion, not the CDMA portion. But then, I'm not done screwing around with it just yet. Hopefully I can figure out an odin file.
Click to expand...
Click to collapse
The CDMA portion isn't accessible. Thank Samsung for going with VIA.
The only way there were ever full flashable CDMA modems for the Charge were because there were sources for leaks. Those sources have dried up as people have moved on to other devices.
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.
So I am on Clean Rom, the latest and last version running 4.3. I am on the ML1 firmware. I never really had this problem with the phone, but for the past few months it has been prominent. It could be the area that I am in, but other phones that I have used do not have this problem.
What could the reason or reasons be that my signal keeps getting cut off? I always disconnect from calls and etc. Could it be my radios aren't up to date? What about updating to the NEWEST firmware VRUDNE1?
Is there a way to go about this other than installing a signal booster? I have tinkered with this phone so much...it may be taking a toll on it. I used to only get bad reception with AOSP ROMS, but now even TW is having the problem.
Any suggestions or replies will be greatly appreciated.
Thanks in advance.
996 said:
So I am on Clean Rom, the latest and last version running 4.3. I am on the ML1 firmware. I never really had this problem with the phone, but for the past few months it has been prominent. It could be the area that I am in, but other phones that I have used do not have this problem.
What could the reason or reasons be that my signal keeps getting cut off? I always disconnect from calls and etc. Could it be my radios aren't up to date? What about updating to the NEWEST firmware VRUDNE1?
Is there a way to go about this other than installing a signal booster? I have tinkered with this phone so much...it may be taking a toll on it. I used to only get bad reception with AOSP ROMS, but now even TW is having the problem.
Any suggestions or replies will be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
According to this: http://forum.xda-developers.com/showthread.php?t=1788313
Just update your baseband. See if that does the trick.
So it is recommending the MF1 firmware. I am already on ML1 baseband with ML1 firmware on 4.3. Can I go back to MF1?
Also the links aren't working :/
996 said:
So it is recommending the MF1 firmware. I am already on ML1 baseband with ML1 firmware on 4.3. Can I go back to MF1?
Also the links aren't working :/
Click to expand...
Click to collapse
Yes, you are fine to flash back to MF1. I have gone from MB1 to MF1, to MF1 w/ NE1 modem on the newest CM etc and gone back to MB1. Here is a link for MF1 AIO firmware ..... https://mega.co.nz/#!RVAGHRDC!boUFGD-5jlMyBNNL9iMR5VOiu4wfQ_VjSUbwLvirGVU
Just flash in recovery.
My story sounds very similar to yours except I'm still on MF1. My reception is still fine but texts aren't working after the first one is sent.
MMS "message failed to send" when second text or later is attempted
capt730 said:
Yes, you are fine to flash back to MF1. I have gone from MB1 to MF1, to MF1 w/ NE1 modem on the newest CM etc and gone back to MB1. Here is a link for MF1 AIO firmware ..... https://mega.co.nz/#!RVAGHRDC!boUFGD-5jlMyBNNL9iMR5VOiu4wfQ_VjSUbwLvirGVU
Just flash in recovery.
Click to expand...
Click to collapse
Just saw this. I will update with my results.
Thanks for the link.
tha_toadman said:
My story sounds very similar to yours except I'm still on MF1. My reception is still fine but texts aren't working after the first one is sent.
MMS "message failed to send" when second text or later is attempted
Click to expand...
Click to collapse
Are you on AOSP?
---------- Post added at 01:26 PM ---------- Previous post was at 12:58 PM ----------
Here is MB1 in case MF1 still gives any one issues (esp AOSP).https://mega.co.nz/#!UJBgCLZS!OKAInNGl8DdUAt_6E8vVRFGyNCQO5VpGAmjFH0o8ZCM
Just flash in recovery.....
capt730 said:
Are you on AOSP?
Click to expand...
Click to collapse
Yeah, I am. CM 10.2.1 "stable" w/ MF1 on it now.
tha_toadman said:
Yeah, I am. CM 10.2.1 "stable" w/ MF1 on it now.
Click to expand...
Click to collapse
Try the MB1 aio that i just posted. There were some of us who were having issues with sending more than 1 sms/mms without having to reboot. MB1 fixed it.
capt730 said:
Try the MB1 aio that i just posted. There were some of us who were having issues with sending more than 1 sms/mms without having to reboot. MB1 fixed it.
Click to expand...
Click to collapse
That did it. After installing MB1, I wiped with TWRP, installed and it's working now. Thanks capt730!
tha_toadman said:
That did it. After installing MB1, I wiped with TWRP, installed and it's working now. Thanks capt730!
Click to expand...
Click to collapse
No problem....can be very frustrating. I am not sure if Verizon was updating/upgrading towers around me or what, or if it was just updates to the blobs/device tree for d2lte from CM, but it took a little while til they got NE1 working for everyone. On the newest CM, AICP, Masta's builds, I can run the MF1 firmware w/NE1 radio with no issues, but my gps won't find any satellites. So I have gone back to my AICP backup from 7/21 or so and I have to go back to MB1 for those builds to work.
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.