Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
flyinjoe13 said:
Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
Click to expand...
Click to collapse
I'm pretty sure being unrooted is not a requirement. Just install this ROM and boot the phone with your SIM inserted. It should activate fine.
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
flyinjoe13 said:
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
Click to expand...
Click to collapse
Boot and HBoot are two very different things. Flashing different boot images will not affect your engineered hboot.
You definitely don't want to talk to vzw reps if you're running cm. The more tech support requests they get from users running non-official builds, the less likely they will be to ever allow phones with unlocked bootloaders on their system.
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
LTE/CDMA should be fine
simlar problem
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
I am having a similar activation problem. What did you do to fix the radio? My problem started a few days ago.
I found the RUU for just the radio and applied it. No change. I get a LTE signal but the phone doesn't know it's own number and thinks it is roaming.
I followed the steps in this thread to restore my radio: http://forum.xda-developers.com/showthread.php?p=45476579#post45476579
Unfortunately, I never was able to get the radio to work with any of the CM based ROMs so I have ended up using a stock based ROM. ViperLTE. It is an excellent ROM and works great, but I got the phone recently so that I could run CM ROMs. Had I known I was going to have so many problems, I would have waited until February when my upgrade date came up and got one of the newer phones. I guess I still can, but I'd hate to waste the money I paid for this phone so soon.
sim issue
Turns out my SIM was actually bad. When you looked in the about, the SIM id number didn't show up. It had worked under 10.2 stable for several weeks before it stopped working. It had gotten worse over a week or so. At first a reboot would fix it. I did a clean flash of CM 11 at this point. After replacing the SIM the id number showed up but still couldn't make calls.
The problem went away after restoring a CM 10.2 back that had worked. I then did a dirty flash of CM 11 over it, with the kit kat gapps. It all worked out fine. I am speculating that a clean flash of CM 11, might not work.
Related
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Messed_sensation said:
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
es0tericcha0s said:
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
Click to expand...
Click to collapse
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Messed_sensation said:
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Click to expand...
Click to collapse
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Thank you for all your help and suggestion:good:. I am now running the Android Revolution HD.
This is a huge change from my iphone 4.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Messed_sensation said:
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Click to expand...
Click to collapse
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
es0tericcha0s said:
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
Click to expand...
Click to collapse
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Messed_sensation said:
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Click to expand...
Click to collapse
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
es0tericcha0s said:
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
Click to expand...
Click to collapse
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Messed_sensation said:
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Click to expand...
Click to collapse
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
es0tericcha0s said:
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
Click to expand...
Click to collapse
I think it is my battery. I picked up an Anker and the phone is now at 20% after 21hrs. Is there a way to get Emoji to work on my phone? When people SMS me, on the lock screen they show up as a question mark in a box but when i go to read the text message there is nothing there.
Using a different keyboard will let you send Emojis, but not really sure about enabling the view from other people's messages off the top of my head, sorry. I recommend SwiftKey for a great keyboard replacement with lots of built in Emojis.
If my Droid Incredible 4G LTE is connected to Wifi, it disconnects from Cellular Data. When I leave where ever it is connected to WifI, it won't connect back to cellular data. I have to turn off Wifi, then reboot the phone. I haven't tried something like switching to Airplane mode, I will try that. Has anybody else seen this issue? The phone is on Straight Talk Veriozon network, so is using SIM card for 4G LTE and CDMA for voice.
Are you stock?
No. Probably would help to mention that. S-OFF, partitions swapped and rooted CM 1.2.1 FWIW, this was happening with CM 11.2 before the partition swap. It wasn't happening before I did S-OFF and flashed CM 11.2 but I was also living in a different location for several months. It didn't start until I moved to where I am now.
I would try to do a clean reflash and see what happens.
I will think about that but I did a clean install when I did the partition swap and flashed the new ROM. I'd rather not do that again and have to set the phone back up again.
Today it seems to be better, I moved from Wifi to out and about and it switched to LTE properly.
therreid said:
I would try to do a clean reflash and see what happens.
Click to expand...
Click to collapse
I may have to try the reflash after all. The problem's gotten worse and now as of yesterday and today a reboot of the phone isn't getting me cellular data back. This did not start until we moved to a temporary place where I get voice service but not data at home. So the phone spends a lot of time on Wifi and not in a place where it can get data. So I'm wondering if the Verizon network is somehow forgetting about the phone or somesuch. At my old house, it was connected to Wifi but the data network was always available. The phone is S-Off with a custom bootloader and recovery. Assuming I wanted to try, can I put the stock ROM back on it without undoing all that?
crokett said:
I may have to try the reflash after all. The problem's gotten worse and now as of yesterday and today a reboot of the phone isn't getting me cellular data back. This did not start until we moved to a temporary place where I get voice service but not data at home. So the phone spends a lot of time on Wifi and not in a place where it can get data. So I'm wondering if the Verizon network is somehow forgetting about the phone or somesuch. At my old house, it was connected to Wifi but the data network was always available. The phone is S-Off with a custom bootloader and recovery. Assuming I wanted to try, can I put the stock ROM back on it without undoing all that?
Click to expand...
Click to collapse
If you want to go to stock, you will have to reverse the partition swap.
therreid said:
If you want to go to stock, you will have to reverse the partition swap.
Click to expand...
Click to collapse
That part I understand. What I should have asked was "if I want to go back to the stock ROM, do I need to undo the custom recovery, relock the bootloader, go S-ON, etc? Any other ROMS besides CM I might try? That could tell me if it is the ROM or not but, again I did not have this issue until I moved to an area where I can get voice, but no data.
You should be able to remain s-off. here are the stock packages if you don't have them, http://android.cmphys.com/stock-fireball/
crokett said:
That part I understand. What I should have asked was "if I want to go back to the stock ROM, do I need to undo the custom recovery, relock the bootloader, go S-ON, etc? Any other ROMS besides CM I might try? That could tell me if it is the ROM or not but, again I did not have this issue until I moved to an area where I can get voice, but no data.
Click to expand...
Click to collapse
Thanks. I will grab a stock ROM. I really like CM 12.1 (and the swapped partitions) though. I was able to get the phone back to cellular data this morning while I was on a chat with Straight Talk. Why a reboot worked then but not the 3 other times I have no idea. I'm also wondering what happens the next time this happens if I go into APN settings and change it to one that doesn't work, then change it back.
Over looking at the stock ROM downloads I see a link to this patch:
http://review.cyanogenmod.org/#/c/93484/
The ROM I am running now was built on 05/26. I see a newer CM 12.1 ROM dated 06/12 that contains that patch so I will flash that ROM, probably next week. I'm on call this weekend and don't want to risk bricking the phone.
I'm running the 6/12 build and it seems happy. I only run my Fireball on WIFI since I switched to AT&T and have a Nexus 5 for my primary.
crokett said:
Over looking at the stock ROM downloads I see a link to this patch:
http://review.cyanogenmod.org/#/c/93484/
The ROM I am running now was built on 05/26. I see a newer CM 12.1 ROM dated 06/12 that contains that patch so I will flash that ROM, probably next week. I'm on call this weekend and don't want to risk bricking the phone.
Click to expand...
Click to collapse
wmuflyer said:
I'm running the 6/12 build and it seems happy. I only run my Fireball on WIFI since I switched to AT&T and have a Nexus 5 for my primary.
Click to expand...
Click to collapse
Ive thought about getting a new phone on a GSM network but where we are building our house I can't get a ATT signal there, so I'm stuck with Verizon.
first off i would like to say sorry if there is a thread out there discussing this. I have looked all over and didn't find what i was looking for. well i htc dev unlocked my phone and flashed recovery, root etc. when i finished i flashed a gsm rom i believe and ever since i can't make/receive calls and no text. i still have data and sprint said it shows my device as being activated. I'm at a loss please help.
thanks in advance if someone can shed some light
snugglepirate said:
first off i would like to say sorry if there is a thread out there discussing this. I have looked all over and didn't find what i was looking for. well i htc dev unlocked my phone and flashed recovery, root etc. when i finished i flashed a gsm rom i believe and ever since i can't make/receive calls and no text. i still have data and sprint said it shows my device as being activated. I'm at a loss please help.
thanks in advance if someone can shed some light
Click to expand...
Click to collapse
you need to just RUU. If you are unsure how to do this some simple searching will give you all you need but it is quite easy. Assuming you have the sprint variant just RUU The latest version.
OMJ has a wonderful RUU/Firmware/Stock Rom thread under android dev. You will find the latetst RUU there in fact its like the first one at the start of the thread: Make sure you show your thanks to him for it all
http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
As always.. please please read the instructions before doing any of this. If you use the windows RUU make sure you are running windows (duh) and have the latest HTC drivers installed on your machine first by install htc sync manager ( you can remove the sync manager program afterwards and leave the drivers installed if you want) http://www.htc.com/us/software/htc-sync-manager/
PS- it would also help a ton if you gave a bit more info such as what rom you flashed and if you flashed GSM firmware. Depending on the ROM you flashed you might just need to flash the latest firmware. Just to be safe and cover all bases just RUU.
I have already ran the RUU i know at least 6 times and it still didn't work. even goes though the whole activating handset deal. Still no actual cell service.
i flashed Android Revolution HD 14.0 once i was able too. doesn't specifically state that it's GSM but no one really said anything about it working on sprint.
i flashed the firmware via OMJ post about 3 times. all of them full, modified, and radio only. no change in the issue
when i go into the phone identity i have a LTE imsi number but my number and CDMA imsi number are all 0's idk if thats an issue. i also tried to manually reprogram it but when i enter##******# to get to MDN menu nothing happens.
thanks for the quick reply
snugglepirate said:
I have already ran the RUU i know at least 6 times and it still didn't work. even goes though the whole activating handset deal. Still no actual cell service.
i flashed Android Revolution HD 14.0 once i was able too. doesn't specifically state that it's GSM but no one really said anything about it working on sprint.
i flashed the firmware via OMJ post about 3 times. all of them full, modified, and radio only. no change in the issue
when i go into the phone identity i have a LTE imsi number but my number and CDMA imsi number are all 0's idk if thats an issue. i also tried to manually reprogram it but when i enter##******# to get to MDN menu nothing happens.
thanks for the quick reply
Click to expand...
Click to collapse
##786#, menu, reset, let it activate that should fix your phone identity stuff. I had same prob after flashing candyrom. This worked for me.
thank you sooo much. it fixed my problem like a dream.