[DOWNGRADE][WARNING]Google Wallet FC - Nexus S General

I updated Tuesday to GWK74 and set up the wallet app to play with it. Flashed back to CM7 (full wipe) for a while.
Then I went back to GWK74 using the OTA update flashed over a fresh flash of the 2.3.5 ota that I was prompted to download. With stock recovery. Google wallet FC. Won't set up the pre-paid card. FC.
Right now I've locked my bootloader and it is flashed with the GWK74 and it still is FC'ing at setup. On the phone with the google wallet people trying to fix it.
So, if you flash the GWK74 update think twice about going back to a 2.3.5 rom.
Code:
W/OTA_STATUS_SCANNING_SERVICE( 1888): Checking status on Google Prepaid Card
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
V/GoogleAnalyticsTracker( 1888): HTTP Response Code: 200
I/SIMPLE_SOAP_CLIENT( 1888): Sending the following request: <?xml version="1.0"
encoding="UTF-8"?><pppactmgnt><pppStatusRequest partnerId="GOOG_MB" mpin="xxx" c
uid="xxx" muid="xxx" cplc="xxx" audit="xxx"></pppStatusRequest></pppactmgnt>
I/SIMPLE_SOAP_CLIENT( 1888): Received response: Status: SUCCESS, response code 0
000, response message: SUCCESS, chip status: PERSO_COMPLETE, chip response code:
3200, chip response message: The card account information was issued already in
to the Customer Secure Element
I/ProvisioningLifecycleTransitionManagerImpl( 1888): OtaLifeCycle change from PR
OVISIONING_INFLIGHT to PROVISIONED for card Google Prepaid Card
I/ProvisioningLifecycleTransitionManagerImpl( 1888): doNewlyProvisionedActions,
isPresent: false
I/ProvisioningLifecycleTransitionManagerImpl( 1888): Scheduling SECURE_ELEMENT_S
CANNING_SERVICE_INTENT...
I/ForegroundProvisioningService( 1888): Provisioning successful for Google Prepa
id Card
I/ForegroundProvisioningService( 1888): Provisioning complete notification
I/ForegroundProvisioningService( 1888): Stop foreground provisioning service.
I/PinProtectedServicesManagerImpl( 1888): mSecureElementManager.enablePayments f
ailed: com.google.android.apps.wallet.secureelement.SecureElementAppletFileNotFo
undException: ControllerAppletImpl: SELECT A0000004762010 expected=0x9000: statu
sWord=0x6a82 (File Not Found): statusWord=0x6a82 (File Not Found)
D/NfcService( 1052): NFC-EE routing ON
D/NfcService( 1052): NFC-C discovery ON
D/NfcService( 1052): NFC-EE routing ON
D/NfcService( 1052): NFC-C discovery ON
E/OTA_STATUS_SCANNING_SERVICE( 1888): **** All credentials are in final state. U
nregistering from periodic status checks.
E/WrappedCredential( 1888): Mismatched state for credential. OtaLifeCycle:PROVI
SIONED SecureElementState:ABSENT
W/dalvikvm( 1888): threadid=41: thread exiting with uncaught exception (group=0x
40015560)
E/AndroidRuntime( 1888): FATAL EXCEPTION: IntentService[SecureElementScanningSer
vice]
E/AndroidRuntime( 1888): java.lang.NullPointerException
E/AndroidRuntime( 1888): at com.google.android.apps.wallet.services.secur
eelement.SecureElementScanningService.forceGetUpdatedStatus(SecureElementScannin
gService.java:270)
E/AndroidRuntime( 1888): at com.google.android.apps.wallet.services.secur
eelement.SecureElementScanningService.updateModelForMismatchedCredentials(Secure
ElementScanningService.java:251)
E/AndroidRuntime( 1888): at com.google.android.apps.wallet.services.secur
eelement.SecureElementScanningService.doWork(SecureElementScanningService.java:2
19)
E/AndroidRuntime( 1888): at com.google.android.apps.wallet.util.WakefulIn
tentService.doOnHandleIntent(WakefulIntentService.java:128)
E/AndroidRuntime( 1888): at com.google.android.apps.wallet.services.Walle
tIntentService.onHandleIntent(WalletIntentService.java:66)
E/AndroidRuntime( 1888): at android.app.IntentService$ServiceHandler.hand
leMessage(IntentService.java:59)
E/AndroidRuntime( 1888): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 1888): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1888): at android.os.HandlerThread.run(HandlerThread.ja
va:60)
W/ActivityManager( 109): Force finishing activity com.google.android.apps.wal
letnfcrel/com.google.android.apps.wallet.entrypoint.EntryPointActivityGroup
V/RenderScript_jni( 447): surfaceCreated
V/RenderScript_jni( 447): surfaceChanged
D/dalvikvm( 1888): GC_EXTERNAL_ALLOC freed 1615K, 47% free 4927K/9287K, external
14473K/14681K, paused 404ms

There's also other issues with going from 2.3.5 to 2.3.7. Back and forth.
http://forum.xda-developers.com/showthread.php?t=1271221
Sent from my Nexus S 4G using xda premium

I just restored my nandroid of 2.3.7 and I am getting no force closes and nfc is working. NFC just stops working when I restore my CM7 backup. I never unrooted or took the ota. I just flashed BuglessPete's stock rooted rom.
Sent from my Nexus S 4G using xda premium

I have flashed back and forth (rooted stock and cm7) four or five times since yesterday without any issues.....wallet is cool but I can't go without cm settings.
ahhhhh...........gone todash..............

pitmaster said:
I have flashed back and forth (rooted stock and cm7) four or five times since yesterday without any issues.....wallet is cool but I can't go without cm settings.
ahhhhh...........gone todash..............
Click to expand...
Click to collapse
I haven't tried going back yet to see if Wallet works after going back and forth. I'm going to assume since the last 2 posters have had no issues I'm not going to have one going back. Not that I am going back as I too kept CM7 over 2.3.7 with Google Wallet. Hopefully by the end of the weekend we can get come CM7 2.3.7 action. The stock Nexus I have here hasn't gotten the OTA yet so I'm not eager right now, lol.
I figured am I going to use the phone more or wallet. Went with the phone and stayed CM7.

I did it for the free 10 bucks Then right back to CM7 I went.
Sent from my Nexus S 4G using xda premium

I have issues. I actually ported over the 2.3.7 rom for the GSM. Got everything working to the point of adding the Google prepaid card but then it errored and couldn't add a card. Probably extra security in the rils. But after flashing back to cm7 nfc no longer works. It kind of sucks because there is no official 2.3.7 for the GSM phones yet but I'm thinking about trying to backport some of those rils to see if I can fix nfc.
Sent from my Nexus S using xda premium

I flashed 74 then did a full wipe of everything and have been playing with miui 1.9.16 and haven't had problems with anything so far. It's using 2.3.5.
I don't know for sure, I'm just guessing, but flashing roms on top of each other isn't a good idea. Wouldn't that make it more likely to break or create conflicts with things?

I just got this email from google.
Hi Jason,
Thanks for your patience.
Please be aware that unauthorized operating systems or rooted devices may have limited or compromised functionality. Such device configurations are not supported by Google Wallet and may expose security risks. We strongly discourage use of the Google Wallet app on such devices.
Appreciate your understanding. Feel free to let us know if you have any additional questions.
Sincerely,
Swathi The Google Wallet Team
Sent from my Nexus S 4G using xda premium

So I rooted and wallet just FC. I unroot back to 2.3.4 upgrade up the ladder and wallet FC. Tried many things tonight and I can't get it back

apreichner said:
I have issues. I actually ported over the 2.3.7 rom for the GSM. Got everything working to the point of adding the Google prepaid card but then it errored and couldn't add a card. Probably extra security in the rils. But after flashing back to cm7 nfc no longer works. It kind of sucks because there is no official 2.3.7 for the GSM phones yet but I'm thinking about trying to backport some of those rils to see if I can fix nfc.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
so even after doing a complete wipe it still doesn't work anymore? that's really scary.

rican408 said:
So I rooted and wallet just FC. I unroot back to 2.3.4 upgrade up the ladder and wallet FC. Tried many things tonight and I can't get it back
Click to expand...
Click to collapse
Are you on sprint?
Sent from my Nexus S 4G using xda premium

Yes I am on sprint... so even after going back completely to stock it doesn't work..

rican408 said:
Yes I am on sprint... so even after going back completely to stock it doesn't work..
Click to expand...
Click to collapse
Did you odin?
Sent from my Nexus S 4G using xda premium

rican408 said:
Yes I am on sprint... so even after going back completely to stock it doesn't work..
Click to expand...
Click to collapse
Which stock rom did you go back to? Because your nfc is only gonna work on 2.3.7.
Sent from my Nexus S 4G using xda premium

david279 said:
Which stock rom did you go back to? Because your nfc is only gonna work on 2.3.7.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
well NFC should work before 2.3.7, just not google wallet.

I did not Odin. I used one click stock which returns the phone to 2.3.4 and wipes all including SD card. Then the phone upgrades to 2.3.5 then 2.3.7...

derekwilkinson said:
well NFC should work before 2.3.7, just not google wallet.
Click to expand...
Click to collapse
No. Once you update to 2.3.7 nfc will no longer work on older versions.
Sent from my Nexus S 4G using xda premium

rican408 said:
I did not Odin. I used one click stock which returns the phone to 2.3.4 and wipes all including SD card. Then the phone upgrades to 2.3.5 then 2.3.7...
Click to expand...
Click to collapse
Did wallet work before you rooted?
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Did wallet work before you rooted?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it did work before rooting. Has to be something on the nfc chip itself sensing a state it doesn't like. I know the evo when there were GPS problems switching between certain roms, we had to use dialer code gpsclrx to clear info on the chip and get it working again. Anything like that for nfc?

Related

G2 Gingerbread OTA starts today

I found this on T-Mobile's G2 Support Community:
http://support.t-mobile.com/docs/DOC-1809
"On July 27, T-Mobile G2 devices will begin to receive an Over-The-Air (OTA) update to Android 2.3.3 (Gingerbread). The update will roll out to customers in waves over the coming weeks.
The update provides the following enhancements and improvements.
New features:
Android 2.3.3 (Gingerbread)
Tell HTC
Google Books added
Notification bar color scheme is changed to black
New battery indicator, phone, and web icons
Color-coded network icon and signal indicator added. Green when connected to Google servers. Grey when not connected.
Pressing the power key while on a call disables the proximity sensor
Fixed or improved issues:
Wi-Fi calling improvements
New SMS and email notification improvements
Improvements to sending MMS from the Gallery
Your phone will show a notification when you have received the update. Alternately, to check if your phone has the update, follow these steps:
From Home screen, press the Menu key.
Tap Settings.
Tap About Phone.
Tap System Updates.
Important: Do NOT call T-Mobile to receive the update before September 1. The timeline for receiving the OTA cannot be expedited. T-Mobile cannot manually push the software to customers who ask to receive it.
Software upgrades at retail stores
Beginning August 5, you will be able to go to a T-Mobile retail store to update your T-Mobile G2, T-Mobile myTouch 3G Slide, and T-Mobile myTouch 4G to the most recent software version. This helps if you have not gotten the Over-The-Air (OTA) update or if you cannot perform the USB tethered update.
If the OTA or tethered update fail, here is what to expect at the retail store:
Updating at the store can erase all the data on the device. The SD card will not lose data.
Back up your data, synchronize your contacts to Google or T-Mobile Backup, and write down the names of all the applications you will want to re-install.
The update can take up to 30 minutes to complete.
The update requires that your phone has over 50% battery life at the store.
The rep at the retail store will:
Remove your personal SD card.
Insert a software update SD card.
Wait for the update to download and install on the device.
Remove the software update SD card.
Insert your personal SD card again."
Excited for 2.3 - stock is fantastic. The only issue remains that I need root to run VPN Connections for work. So close! Thanks for posting.
If you get the OTA and are reading this (or have read it), please post back your region and when you got the OTA.
thanks!!
Yay for you stock people! Will give you guys a nice fresh device.
Sent from my T-mobile G2 using Tapatalk
I just want the modem because my gf keeps complaining about poor signal and wonky wifi signal on cm7
Sent from my SPH-D700 using XDA App
this will be my first android phone getting a OTA update, some questions.
-If my phone is rooted, will I need to root again?
-Will all the system settings revert to default?
thanks
Can anyone confirm whether or not this is the same update that was leaked in May?
I am running Build 2.13.531.8 CL56018.
diehardfan said:
this will be my first android phone getting a OTA update, some questions.
-If my phone is rooted, will I need to root again?
-Will all the system settings revert to default?
thanks
Click to expand...
Click to collapse
YES u will lose root and have to wait for a new way to to change the hboot.....u will still have ur system settings if ur on stock rom...
Thank you for sharing.
Sent from my T-Mobile G2 using XDA Premium App
kitila said:
YES u will lose root and have to wait for a new way to to change the hboot.....u will still have ur system settings if ur on stock rom...
Click to expand...
Click to collapse
What other ROMS can someone rooted run that will defeat/prevent download and loss of root?
Are ROMS based on the .5 and .8 leaks safe? Or do we need CM or miui?
x6369x said:
Can anyone confirm whether or not this is the same update that was leaked in May?
I am running Build 2.13.531.8 CL56018.
Click to expand...
Click to collapse
I'd love to hear this as well. SO...nobody so far has actually gotten this update? Really? When you do, like somebody else said, post where you are please.
kingston73 said:
I'd love to hear this as well. SO...nobody so far has actually gotten this update? Really? When you do, like somebody else said, post where you are please.
Click to expand...
Click to collapse
The location of the person never mattered, it's completely random based on EMEI or some such.
I am just waiting for someone to post the direct link so I can manually update the G2 my wife inherited from me.
i was about to say the same thing, location DOES NOT matter in the least. I think it's partly first-come, first served based on check-in (*#*#CHECKIN#*#* to force it) and also IMEI based too. But most importantly, I also would like to see the manual update ZIP, as well as the version.
Don't worry about rooting 2.3.3 we've already done that, and it's great that the G2 is seeing a update for those stock users
I want to stay rooted with my GB CM nightly. It is really close to perfection, and now since Netflix is working smooth as butter, there is no reason to change. Since im running the latest nightly, would I see something that I would click to download?
Sent from my HTC Vision using XDA Premium App
lawalty said:
I want to stay rooted with my GB CM nightly. It is really close to perfection, and now since Netflix is working smooth as butter, there is no reason to change. Since im running the latest nightly, would I see something that I would click to download?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
???
If you aren't on stock you won't get the update. CM strips out the ability to receive otas, would get a lot of bricks if they didn't.
Sent from my T-mobile G2 using Tapatalk
[hfm] said:
The location of the person never mattered, it's completely random based on EMEI or some such.
I am just waiting for someone to post the direct link so I can manually update the G2 my wife inherited from me.
Click to expand...
Click to collapse
The rom has been in the dev forum since 05/10. The full pc10img for stock users is over there somewhere too.
Can someone please direct me to the stock 2.2 ROM I'm on my phone and its pain in the but searching, thank you.
I wanna see if I can get the update.
Edit: found it and flashed but still no OTA.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
The rom has been in the dev forum since 05/10. The full pc10img for stock users is over there somewhere too.
Click to expand...
Click to collapse
Really? You have a link to some proof this OTA rollout started today is the exact same image as that leaked one?
I'd like to see that pls.
zkid2010 said:
Really? You have a link to some proof this OTA rollout started today is the exact same image as that leaked one?
I'd like to see that pls.
Click to expand...
Click to collapse
No I can't provide proof of that. Sorry. But I have read in a few places that they were the same.
Sent from my HTC Vision using XDA Premium App

Me, wallet, cm7 and 2.3.7

I'm having issues starting nfc in cm7. It won't start.
Well I decided to try out the 2.3.7 update yesterday and use the google wallet. Everything worked well, I used my 10 dollars at McDonalds. So I nandroid back to the latest cm7 nightly and nfc won't turn on. I checked out the logcat and it has a bunch of errors saying "download firmware" and "can't download firmware". I went back to
2.3.7 and nfc works again. The logcat for 2.3.7 had a bunch lines saying secure nfc enabled, etc.
So I'm guessing my nfc on cm7 won't work correctly till 2.3.7 are released. Anybody else seeing this behavior?
I will try to post detailed locate, later.
Sent from my Nexus S 4G using xda premium
Just a thought: Kernel? I know that some versions of Trinity kernels disabled NFC for some testing...
I'm using petes kernel in cm7. It worked before using cm7 nightly. I'm thinking 2.3.7 injected some kind of security into the nfc chip that 2.3.5 can't read because it works perfect on 2.3.7.
Sent from my Nexus S 4G using xda premium
i think 2.3.7 unlocks access to what they're calling the 'Secure Element' chip which Google Wallet uses to store your credit card data (and keep it separate from the phone's internal memory making it harder to hack). so like you said, i assume it's a security thing in 2.3.7
Here's a pastebin of my nfc enabled on 2.3.7
http://pastebin.com/qw9Dtgca
Sent from my Nexus S 4G using xda premium
I can confirm nfc no longer works on cm7 after flashing stock 2.3.7
Sent from my Nexus S 4G using xda premium
I posted else where but I figured I'd drop a line here. Same issue here. NFC won't turn on. Wasn't worried about it previously as I just assumed it changed some of the settings for the NFC and obviously didn't change back when flashed to CM7. IE Anything under 2.3.7 after 2.3.7 would not have compatible NFC software in the background.
And, as you said going back to 2.3.7 it works fine.
Has anyone else had the problem from the other thread I saw? Where Google Wallet is FCing on them after flashing back and forth?

aurora ics data connection problem

I have updated the last one, 1.11 version of aurora ics, and 3g data connection wont work. Service provider is Saunalahti, wich works in Elisa's network. I've enabled data in roaming and still not working. There was another fix for Saunalahti in this version, but I haven't noticed any difference. Please help me fix this 3g issue.
Did you try these commands in local ssh?:
su
setprop persist.opl.enabled 0
setprop persist.pnn.enabled 0
I got 3G working with those commands but if I wanted to boot phone, i had to boot it several times before it connects again, so now i'm back to stock Froyo. Hope that dzo will get his awesome rom working with Saunalahti
n1nj44 said:
Did you try these commands in local ssh?:
su
setprop persist.opl.enabled 0
setprop persist.pnn.enabled 0
I got 3G working with those commands but if I wanted to boot phone, i had to boot it several times before it connects again, so now i'm back to stock Froyo. Hope that dzo will get his awesome rom working with Saunalahti
Click to expand...
Click to collapse
And if that also fails, make sure you flashed official gingerbread on your device, I had a similiar issue in Estonian Elisa network. I realized that I had .32 froyo instead of .35 gingerbread. Yet I haven't found any way to root the latest one yet, if you want, I can upload the one I have working.
Sent from my Huawei Ideos X5 using xda premium
Moved To Q&A​
Please post all questions in the Q&A section​

[Q] Signal Loss after Kernel Change

Hello XDA Developers,
I was trying to install a custom ROM on my Galaxy S4 deivce (SPH-L720). I successfully flashed the ROM through CWM. I installed the Google Edition ROM that was somewhere in the forums under Android Development.
But after reading the thread, it seemed that many people were have success with a kernel known as "AGAT".
After about 4-5 minutes of using the ROM, my signal and LTE went away, so I decided to flash that kernel as well. However, now I don't get any signal on any ROM. I flashed the stock kernel through Odin (I was trying to see if that would work), but no luck yet.
Any advice or tips?\
===================================================
UPDATE:
I restored it to the stock firmware and used TriangleAway. I took it to the Sprint store and the guy fixed it up for me in about 30 seconds.
Ya he probably just updated the prl and profile.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Re activation
Sent from my SPH-L720 using Tapatalk 4 Beta
miketucky350 said:
Re activation
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup re activation was only way sprint tech over phone could fix it, if you know the dial code you can try it yourself...I also tryd the google edition rom with custom kernel which is what caused all this network lost, not even my stock rom nandroid back up could help me
Edit: heres the dial code for reactivation youl get data working again##72786#
Sent from my SPH-L720 using xda app-developers app
gotablunt said:
yup re activation was only way sprint tech over phone could fix it, if you know the dial code you can try it yourself...I also tryd the google edition rom with custom kernel which is what caused all this network lost, not even my stock rom nandroid back up could help me
Click to expand...
Click to collapse
Do you know how to install the AGAT kernel? I really want Google Edition, but I will wait if I have too.
You have to install the kernel right after flashing the rom...then wipe dalvik/cache and fix permissions. Worked great for me..
Sent from my SPH-L720 using xda premium
Does it matter whether it is on my sd card or if the kernel is located in my internal storage?
Sent from my SPH-L720 using xda premium
It doesnt matter
Sent from my SPH-L720 using XDA Premium HD app
question
gotablunt said:
yup re activation was only way sprint tech over phone could fix it, if you know the dial code you can try it yourself...I also tryd the google edition rom with custom kernel which is what caused all this network lost, not even my stock rom nandroid back up could help me
Edit: heres the dial code for reactivation youl get data working again##72786#
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
hi, this same thing happened to me and I've gone to 3 different sprint stores and none of them knew what I was talking about. my question is, how do you use the dial code you mentioned if the phone has no network connection? I've tried to go back and flash different rom's but nothing has worked. I'm using TWRP, AGAT 4.0, and the stable google rom. any help would be appreciated, I'm currently without a phone.
secretredfoxx said:
hi, this same thing happened to me and I've gone to 3 different sprint stores and none of them knew what I was talking about. my question is, how do you use the dial code you mentioned if the phone has no network connection? I've tried to go back and flash different rom's but nothing has worked. I'm using TWRP, AGAT 4.0, and the stable google rom. any help would be appreciated, I'm currently without a phone.
Click to expand...
Click to collapse
You're not *actually* calling anyone. It's sort of like command prompt for your PC. But instead of command prompt you use the dial pad It WILL work and it takes less than 30 seconds.
secretredfoxx said:
hi, this same thing happened to me and I've gone to 3 different sprint stores and none of them knew what I was talking about. my question is, how do you use the dial code you mentioned if the phone has no network connection? I've tried to go back and flash different rom's but nothing has worked. I'm using TWRP, AGAT 4.0, and the stable google rom. any help would be appreciated, I'm currently without a phone.
Click to expand...
Click to collapse
Try and dial ##72786#
I believe that's the dial code.
Sent from my SPH-L720

Triforce rom phone not reading cell tower ids

Hey all. I have Triforce rom 3.0 and loving it. I also have the MF9 ODIN full update. Im trying to use tasker or LLAMA for location triggers <ie to turn on off wifi if im home not home> my phone workds great data and phone but these programs cant read cell tower location. No matter where I am it has cell tower as -1. So these programs wont work . It worked before on the force rom 2.3. Any suggestions?
Sent from my SPH-L720
GeneticJim said:
Hey all. I have Triforce rom 3.0 and loving it. I also have the MF9 ODIN full update. Im trying to use tasker or LLAMA for location triggers <ie to turn on off wifi if im home not home> my phone workds great data and phone but these programs cant read cell tower location. No matter where I am it has cell tower as -1. So these programs wont work . It worked before on the force rom 2.3. Any suggestions?
Sent from my SPH-L720
Click to expand...
Click to collapse
Please let me know if you found a solution for your current issue. Thanks!
ghaedo said:
Please let me know if you found a solution for your current issue. Thanks!
Click to expand...
Click to collapse
I did not find any solutions so with this small issue and the need for random battery pulls I flashed the stock rooted MF9 and all is good again.
Sent from my SPH-L720
GeneticJim said:
I did not find any solutions so with this small issue and the need for random battery pulls I flashed the stock rooted MF9 and all is good again.
Sent from my SPH-L720
Click to expand...
Click to collapse
Thank you for your feedback.
I had a rooted SPH-L720 with the hotspot mod and decided to upgrade to tri force ROM 3.1
my speed went from 7-14 Mbps down and 6-11 Mbps up to 0.19 - 0.41 Mbps down and about the same for upload and half the time when I do a speed test it says network communication error. I backed up my phone before updating the ROM but get an error message when trying to restore back to the original version I wonder if we're having similar problems?
DellS7 said:
I had a rooted SPH-L720 with the hotspot mod and decided to upgrade to tri force ROM 3.1
my speed went from 7-14 Mbps down and 6-11 Mbps up to 0.19 - 0.41 Mbps down and about the same for upload and half the time when I do a speed test it says network communication error. I backed up my phone before updating the ROM but get an error message when trying to restore back to the original version I wonder if we're having similar problems?
Click to expand...
Click to collapse
i was getting the same thing i think it is from the towers being upgraded and there is a new version that upgrades to android 4.3 on triforce 4.0. also before you go to the new rom make sure to upgrade your radio (mja). you can get it from this link
http://forum.xda-developers.com/showthread.php?t=2338919

Categories

Resources