So I'm running fission, not entirely happy with it. Terrible battery life, and at least once a day my phone stops receiving texts until I restart it.
My problem is, I accidentally flashed an older recovery, and probably cannot use the backup of stock that I made with recovery version 3.0
What do I do?
Simply flash SBF and start over. Make sure you wipe everything after SBF flash or phone won't work properly. If you plan to stay stock, do not flash "stock" deodexed/rooted versions from Fission/others. They are neither better nor faster than stock rom. Simply freeze the unwanted stuff. Unless you plan to play with themes/etc. Then you will need deodexed rom. Not having original stock rom will prevent you from updating using official Motorola updates though. Your call.
i actually messed with it yesterday. i was able to flash my stock backup made with clockwork recovery 3.0, using 2.5.3
so everything is all better.
Hello, this is my first time posting on the forums here.
Recently I flashed the latest version of MIUI on my Verizon Galaxy s3. I decided that I preferred my previous rom; Jelly Bean's Build 10, and I restored it to my phone. After restoring the rom, I got a message saying that I was roaming, even though I am still in the same area where service has been working flawlessly. The first thing I tried to do was change the network type under network settings to LTE/CDMA but that choice was already selected. Thinking that I had no other options, I restored the stock rom that I had backed up on my device and I got the same issue. Thinking I could just send the phone back to Verizon, I unrooted the phone using the built in unroot tool in SuperSu Pro. I am now unrooted, but forgot to reflash the stock recovery (I am still using TWRP). I am just wondering what I should do about the issue, and if I were to send it back to verizon, would they be able to tell that I have a custom recovery. Sorry for being a noob and any help would be much appreciated.
Update: I rolled back to my rooted stock ROM and I used triangle away to reset the custom flash counter. I have also reflashed the stock recovery onto my device. Even though my phone appears to be unmodified I still have the same issue.
Sent from my SCH-I535 using xda app-developers app
there are SOOO many threads about how to fix the roaming issue it's not even funny....
^^^^^what he said!
This happened to me and what I had to do was ODIN to stock ICS rom and enter the code to reprovision sim. Google/forum search is your friend.
This is why Verizon locks down their phones! People who are not willing to search for a way to fix something that they screwed up is unacceptable. The bad thing is this phone is completely fixable with very little effort! Some people should not be allowed to flash anything!
I've dealing with so many issues ever since the DroidX so if there is one thing I've learned is there is ALWAYS a fix you may just need to do a little search if you can't find the resources your looking for on any of forums a simple google search will help you out.
So, I'm buying this to replace my evo 4g and I was wondering how I would go about using a custom ROM for this and having the apns and data working correctly.
I plan to activate it on Ting.
To be a bit clearer, I want to use a custom ROM and I want to be sure that it'll work. So first, can anyone on Ting confirm that they're running a custom ROM (preferably KitKat) with no problems?
And I assume I'd have to activate the phone first, then install a custom ROM. Would I have any problems doing that? Would the apns be messed up? Or should everything be fine as long as I activate the phone and update everything on stock before installing a ROM? Reason I ask is because I know some Roms don't allow the *#*# thing needed to activate a phone on a new network.
Thanks!
I am using mine on Ting. I had used my first Q as unrooted stock JB, which worked pretty well for a year, but then it reached a near--bricked state where it wouldn't boot past the yellow Sprint screen. I couldn't resolve this in a timely fashion, so wound up buying a second Q which runs stock ICS, but failed to download the stock JB update.
In the meantime, I unlocked both phones' bootloaders, and tried a few kItkat ROMs on my original phone before settling on CM 10.2, which is a JB ROM. I then switched my Ting activation (back) to this phone. The lack of #*# commands isn't really a problem with respect to re-activation, but it is a problem with respect to PRLs and (perhaps) APNs. I recommend Ting activation and a PRL update prior to installing your custom ROM.
Like others, I would like to learn about a stable kitkat ROM where bluetooth, wifi, and phone data/sms/calling all work reliably. My other primary requirement is the ability to play DRM'd downloaded Amazon Prime Music, which didn't work on the kitkat ROMs I tried, but does work on my JB ROM.
Sent from my XT897 using Tapatalk
Before I post in the CM forum, thought I would try here first.
I am a very experienced flash/mod user and have never had a "brick" issue in many years of tinkering with dozens of devices. I have been using Cyanogen and AOSP roms since 2008.
Today, I thought I would try a CM12 build on an XT1031(cdma) knowing that even though CDMA is not operational, CM builds are unified anyway. I figured it wouldnt be like flashing a GSM ROM onto a CDMA device. Well, I guess I was wrong...
It appears that CM12 builds are indeed GSM specific, and though the ROM installed and ran correctly, it seems to have corrupted both wifi and cellular radio at very deep level.
I fastboot flashed back to 4.4.2 stock, and it boots fine. Wifi connects and grabs an IP but doesn't transfer data, and cellular stays as a black triangle. It seems to grab MIN and phone# and has correct MEID.
Eventually, after 60-120 seconds the phone will crash and reboot.
I have tried flashing stock radios from the thread here, and have also tried several other falcon stock and CM11 roms. They all exhibit the same behavior...boot fine, no networks, and crash after a minute or two.
I find it hard to believe that flashing a ROM would physically damage BOTH wifi and cellular radios. One or the other I could understand. But this seems like a deeper problem at a base level of the phone...below ROM or firmware.
Is it possible that changes were made at at the /persist level? Is there any way to reflash the /persist partition with a stock image?
I have access to bootloader and recovery (currently TWRP). Any suggestions are greatly appreciated.
I really just want to get wifi working... plan on using it wifi-only anyway. But it would probably be good for the community to document the problem and see if we can figure out what caused it and if it is fixable or "brick-worthy"
Thanks!
Sent from my XT1028 using XDA Free mobile app
Got it fixed.
I didn't notice, but the CM12 build automatically upgraded the bootloader to 41.13. I was not able to fastboot flash the motoboot.img and boot.img files because they were the wrong version. Once I flashed it with a 4.4.4 version of motoboot.img and boot.img, I was able to flash the system partition back to 4.4.4 stock and it is working 100%.
So, if you are reading this and are in a similar situation with "preflash validation failed" or other "downgrade" errors, check your bootloader version. If it is 41.13, you will need to manually flash 4.4.4 images.
Now, I am just stupid enough to try this again...this time with a custom modem/radio image
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.