Background: My GS3 was rooted and running ICS 4.0.1 and TWRP recovery nearly since the day I got it--stock Tochwiz ROM for the main reason of being able to tether and run Google Wallet. Everything was working great, but I completely restored the phone to stock (no root, stock recovery, phone wiped) with the intention of installing the latest OTA, Jelly Bean 4.1.1 (and then subsequent 4.1.2 which was pushed down a few days ago) and then re rooting and re installing TWRP recovery.
Issue: After closely following the steps outlined here to root my GS3, unlock bootloader and install TWRP, everything seemed to work fine, until Google Wallet installation gave me an error that NFC was disabled. When going to my settings to correct this (Settings>Wireless and network>More settings) I noticed I had absolutely NO NFC SETTINGS. I already tried re-flashing a fresh download, searching XDA and Google, with no luck. Any suggestions? I really miss NFC already.
Hi,
I'm new to ROMs with the Motorola Photon Q, but I have prior experience doing this with other Android devices. I'm also a longtime Linux guy, so "adb" and "adb shell" are both comfortable environments for me.
A few weeks ago my stock JB Photon Q reached a state where it would only reach the yellow "Sprint" screen during the boot process, and hang there. I fiddled a bit with the bootloader, but didn't get very far, and ordered a replacement used Photon Q. Unfortunately my newer phone came with ICS, and I when I attempt the builtin operating system JB update I encounter a message "Unfortunately, Motorola Services has stopped", followed by an indefinite "Checking for available update.* Please wait ..." So I've unlocked both phones, and began fiddling, while using the newer (ICS) one as my active phone for making phone calls, etc.
Fortunately on my older phone (the one that had the yellow screen) I've now been able to install the TWRP 2.7.1.2 Recovery, and I installed the September 26th version of the MoKee KitKat ROM, i.e. MK44.4-moto_msm8960_jbbl-140926-RELEASE.zip. In principle I'd rather use a blessed CyanogenMod version, but am concerned about some of the recent Wifi (and to a lesser extent, Bluetooth) problems that I've read about.
Overall, my primary goals are a stable environment and being able to store Amazon Prime DRM'd files on my SD card, symlink them from the primary storage, and be able to play them using the Amazon Music app. Thanks in advance for your recommendations regarding stable ROMs.
[ on my MoKee KitKat phone, the Amazon app is crashing on most of the DRM'd files that I downloaded from the Amazon Music app, even though I haven't moved them to the SD card or done anything tricky like that ]
My question now is: if I install the same TWRP recovery on my newer phone, will I then be able to install the stock JB image? I've researched to see whether TWRP 2.7 is backwards-compatible with JB ROMs, but haven't found the answer. It would be nice to use the same Recovery when trying out different ROMs, including both JB and KitKat.
Thanks ...
Yes, TWRP should be able to handle any appropriately formed .zip. Regardless of Android version.
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I have a T-Mobile phone and I'm currently on Resurrection Lollipop (CM 12.1 based) and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now) or if you have a workaround for this.
Dowload - http://www.mediafire.com/download/1b..._930000657.apk
is not working on official at&t rom 5.0.2 FC android System
Edgardo Regazzoni said:
is not working on official at&t rom 5.0.2 FC android System
Click to expand...
Click to collapse
Does it give the same error?
Play store "connection time out" error in both Kitkat & Resurrection Remix Zenfone 5
Hi,
I upgraded my Zenfone 501CG T00J Jelly Bean 4.3 (which was working fine) to KitKat firmware WW 2.22.40.54 (OTA), after which I couldn’t connect my Play Store through Wi-Fi (Connection time out error) , though I could browse sites with my chrome browser. There was no problem with Wi-Fi router, which I checked by connecting Play store with my Zenfone 7” tab and also my laptop. Then, I tried with various steps like clearing cache, clearing data, uninstalling updates and updating again, installing an older play store apk, checking date and time, (that are available all over internet) and finally contacted Asus customer support through online chat. They suggested clearing cache and no more, and disconnected. Frustrated at their support, I decided to flash a custom ROM and installed Resurrection Remix. Still my problem persisted. Added with Play store, I was left with no GPS, FM Radio and most importantly, the Call recording feature, which I loved so much since many other phone never offered!. Also after upgrading, my model number changed to T00F from T00J. Now I’m thinking of reverting back to stock (Asus) KitKat or Jellybean.
How should I do it?
What could be the cause for the Play Store “Connection time out” error in both Stock KitKat and RR?
Any solution? Have a Great Day! Thanks in advance!!
ajith26 said:
Hi,
I upgraded my Zenfone 501CG T00J Jelly Bean 4.3 (which was working fine) to KitKat firmware WW 2.22.40.54 (OTA), after which I couldn’t connect my Play Store through Wi-Fi (Connection time out error) , though I could browse sites with my chrome browser. There was no problem with Wi-Fi router, which I checked by connecting Play store with my Zenfone 7” tab and also my laptop. Then, I tried with various steps like clearing cache, clearing data, uninstalling updates and updating again, installing an older play store apk, checking date and time, (that are available all over internet) and finally contacted Asus customer support through online chat. They suggested clearing cache and no more, and disconnected. Frustrated at their support, I decided to flash a custom ROM and installed Resurrection Remix. Still my problem persisted. Added with Play store, I was left with no GPS, FM Radio and most importantly, the Call recording feature, which I loved so much since many other phone never offered!. Also after upgrading, my model number changed to T00F from T00J. Now I’m thinking of reverting back to stock (Asus) KitKat or Jellybean.
How should I do it?
What could be the cause for the Play Store “Connection time out” error in both Stock KitKat and RR?
Any solution? Have a Great Day! Thanks in advance!!
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Here is everything you need to know
Good luck!
Resolved!!
Thanks for all those who replied!
Solution that worked for me...
1. Installed Super Su
2. Entered recovery mode via reboot options in RR
3. Flashed/Installed a file "4.44 fastboot flash.zip" that I saved in my sd card and shared by a android developer in facebook (Sid Kondekar......thanks to him).
I Couldn't share links coz I'm a newbie (<10 posts) ....sorry...
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445