Not sure if this pertains to 4.3 or not. I am rooted running stock 4.3 with Franco kernel and my Google wallet does not work. I try to make purchases but it always fails. Any ideas? Or suggestions? And yes I have the right card on file.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
I am currently running FraNco.Kernel R38 and was wondering how I go about updating to the newest version of android when it releases. Would I do an ota update and be fine or would I have to flash the whole ROM and lose all my stuff?
Would I be able to use cwm or twrp and restore just the data?
Still new to android and was having a hard time finding this with search.
Thank you so much!
Adam
Edit: running stock Jellybean 4.2.1
Sent from my Nexus 7 using xda app-developers app
Bump pl0x
Sent from my Nexus 7 using xda app-developers app
I've flashed the new 4.3 rom and the new radio .83 and bootloader. Everything seems to work great other than mx player which I know is currently not yet compatible. The issue I am having is Google hangouts it keep force closing. The only success I've had is restoring app and data using titanium backup and even that is only temporary. I have wiped data I've also uninstalled hangouts and reinstalled it using the playstore but no success, any ideas?
Sent from my Nexus 4 using xda premium
4.3 is currently a leak. So don't expect every app to work. And we do not know that the current hangouts supports 4.3.
I'm sure we are probably atleast a month away from anything official.
Sent from my Nexus 4 using xda premium
Judging from the board their really isnt much of a need to atleast not until the OTA update comes out or when custom roms and kernels come out for 4.3.. I mean battery life on 4.3 has been hit or miss, Rooting 4.3 is still buggy and may not work right?
I'll get it when my phones finally get the OTA I can wait to root if need be. Just as I can wait for custom roms and kernels too.
Sent from my Nexus 4 using xda app-developers app
You can use OTA rootkeeper if u dont want to lose your root
Sent from my SGH-I897 using xda premium
n205des said:
You can use OTA rootkeeper if u dont want to lose your root
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
doesnt work with 4.3
I'm trying to keep lte I tried 4.3 but couldn't get lte working until there's an all in one zip I can flash I'm hanging back
Sent from my Nexus 4 using xda app-developers app
I am waiting for the CM 10.2 merge to complete and to see what they come up with as a solution for the whole nosuid issue on the system partition.
Sent from my Nexus 4 using Tapatalk HD
Sherrillface said:
I'm trying to keep lte I tried 4.3 but couldn't get lte working until there's an all in one zip I can flash I'm hanging back
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
just flash the .33/.83 hybrid radio, download the network app (https://play.google.com/store/apps/details?id=de.mangelow.network), select lte/gsm (auto), change your apn from epc.tmobile.com to fast.t-mobile.com and enjoy.
I actually jumped on it right away, but evidently my favorite app (Podkicker Pro) needs tweeking to be compatible with it because it keeps crashing every time i open it. I went back to 4.2.2 for now but once Podkicker is updated, then I'll jump back onto 4.3. My only regret is that I'll miss the original gtalk app. So far, I am NOT a fan of Hangouts.
Chainfire's SU for the SGS4 works on our N4s. He posted it on his Google+ page. It is also referenced in the 4.3 OTA thread.
Sent from my Nexus 4 using Tapatalk 2
ph37rd said:
Chainfire's SU for the SGS4 works on our N4s. He posted it on his Google+ page. It is also referenced in the 4.3 OTA thread.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
What do i do if i get this message in cmd? says that it is not recognized as a internal or external command, operable program or batch file
Im on windows 8
Yep, I'm going to wait. I put the factory image on my Nexus 7, but I'm going to wait for Cyanogenmod to release a 4.3 build for the Nexus 4.
Waiting for mbq's BBQ ROM so I'll be waiting for the betas.
Sent from my Nexus 4 using xda app-developers app
Waiting for Halo + 4.3.
I'm not going to complain about it though in the thread because I want them to take there time and do it right.
Sent from my Nexus 4 using Tapatalk 4 Beta
I got the ota link from here and haven't looked back since. I didn't have 4g for all of 20 hours and now I am on some pure Aosp goodness from Jarjar124. No complaints from me even though I thought it would kill me to be on vanilla'sh ROMs.
Going to wait till the JellyBeer ROM updates
I jumped. I'll install PA4.3 when its dropped tho. But I really like 4.3 Improvement all around.
Waiting for PA...
Can't help with the fact that I have to sacrifice so many features from custom ROM and kernel for the "upgrade". The android version can wait.
nevermind I was gonna do it but my drivers are messed up or its windows 8 fault but cmd doesnt recognize my Nexus 4 so I'll just wait for the POT update. screw it
I am waiting for Paranoid Android to upgrade to 4.3
Sent from my Nexus 4 using xda app-developers app
Thanks in advance guys!
Sent from my Nexus 4 using XDA Premium HD app
It will. 4.3 isn't fully compatible with the LTE enabled, older radio. People are messing with hybrid radios to fix the incompatibility issues, but that's still a work in process i.e. bugs.
Sent from my Nexus 4 using xda app-developers app
cheapskate88 said:
It will. 4.3 isn't fully compatible with the LTE enabled, older radio. People are messing with hybrid radios to fix the incompatibility issues, but that's still a work in process i.e. bugs.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No bugs on hybrid radio here...
Nexus 4+ Franco + LTE
Apparently, no more bugs.
http://forum.xda-developers.com/showthread.php?p=43969514
Sent from my Nexus 4 using xda app-developers app
My OTA update said 4.3 was ready to install, but when I clicked install nothing seemed to happen. I am rooted and have TWRP installed as my recovery. Any suggestions?
And now when I check for an update, my phone says I'm up to date but I'm still on 4.2.2.
Sent from my Nexus 4 using XDA Premium HD app
Cee_Pee_Three said:
My OTA update said 4.3 was ready to install, but when I clicked install nothing seemed to happen. I am rooted and have TWRP installed as my recovery. Any suggestions?
And now when I check for an update, my phone says I'm up to date but I'm still on 4.2.2.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
You have to do it manually by use fastboot method. OTA is not gonna work when you flash the TWRP as your Recovery.
2 method: 1. fastboot flash your recovery back to stock one OTA will work. 2. Flash your N4 with fastboot to get 4.3 ROM.
I went back to the stock 4.2.2 rom and I'm not rooted anymore, but now the stock recovery doesn't work. So how can I update to 4.3?
Sent from my Nexus 4 using XDA Premium HD app
I just purchased a Nexus 4 and upon checking out the device I noticed the model number says Full JellyBean on Mako. What does this mean?
Zombienaut said:
I just purchased a Nexus 4 and upon checking out the device I noticed the model number says Full JellyBean on Mako. What does this mean?
Click to expand...
Click to collapse
Mako is the code name given for the nexus 4 device. Jelly Bean is an Android release.
Mine said: Nexus 4. Did you buy it new or used. If used and you're worried, just flash the factory stock 4.3 image which will erase everything previously.
eksasol said:
Mako is the code name given for the nexus 4 device. Jelly Bean is an Android release.
Mine said: Nexus 4. Did you buy it new or used. If used and you're worried, just flash the factory stock 4.3 image which will erase everything previously.
Click to expand...
Click to collapse
I bought it off of Craigslist. Person listed it as new, still had the plastic on it.
Sent from my Full JellyBean on Mako using xda app-developers app
Sent from my Full JellyBean on Mako using xda app-developers app
Most likely a custom rom. It doesn't look like the kernel is stock kernel to me. It's safest to do a full wipe and factory reset. You should update to 4.3 anyway, use this guide:
http://forum.xda-developers.com/showthread.php?t=2010312
eksasol said:
Most likely a custom rom. It doesn't look like the kernel is stock kernel to me. It's safest to do a full wipe and factory reset. You should update to 4.3 anyway, use this guide:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I wasn't able to update to 4.3, and my computer wasn't recognizing the phone either. However, after booting the phone into bootloader, my computer recognized it. So I unlocked it and am currently flash stock 4.3 onto it via Nexus Toolkit.
Hopefully it works out for you. However, try not to use toolkits in the future. If something goes wrong at some point you won't know what to do if you rely on toolkits. Learn the manual method of flashing.
Sent from my Nexus 4 using xda app-developers app
at4r1 said:
Hopefully it works out for you. However, try not to use toolkits in the future. If something goes wrong at some point you won't know what to do if you rely on toolkits. Learn the manual method of flashing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I know how to manually flash and all that. It's just I already had Toolkit installed and just thought it would be quicker.
Zombienaut said:
I know how to manually flash and all that. It's just I already had Toolkit installed and just thought it would be quicker.
Click to expand...
Click to collapse
10-4.
Good luck
Sent from my Nexus 4 using xda app-developers app
After a frustrating ordeal with my computer not recognizing my phone, I finally installed CyanogenMod and am loving this phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Zombienaut said:
After a frustrating ordeal with my computer not recognizing my phone, I finally installed CyanogenMod and am loving this phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, just enable USB debugging and it should recognize. If USB debugging doesn't work (it should), try installing drivers again (manually).
Don't forget to hit "thanks"