Related
[How To] rooted B&N (1.3) with market access working .... no really.....it's working.
My goal - a rooted 1.3 stock device that had full market access back the way 1.2 worked w/ market prior to the update.
I'll preface this by saying I've tried nearly everything from almost every post in XDA in the last month, but I still had no market access and had to side-load all my apks. I get the feeling that there are quite a few of us that tried manulNooter and various forms of tweaks but are still w/out market access so it is for us that I write this.
I read this today and with a slight tweaking of the steps, I now have ROCK SOLID full market access on the first try.
I'll flat out say that all of the work can be chalked up to other people's time and effort, it's only the steps that worked for me I'm outlining here.
Beforehand:
Make sure you have a bootable CWM card (linky)
Make sure you have updates 4.6.18 and 4.6.16a.
Get the B&N 1.3 update here since you're going to revert your NC back to stock
START:
1) Before updating to 1.3 firmware you are required to do a complete wipe (which requires an aborted power-up [simply hold power button down during the launch process] 8 times in a row - or MUCH easier: the following command using adbWirless ).
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
2) I waited for the whole B&N setup after the wipe and I went through the steps of registering the device to my B&N account, then I did a factory reset at the "Erase and Deregister the device". It relaunches B&N one more time. After restarting I simply shut down the device before registering it again.
3) I then plugged in my Nook via. USB cable to my PC. I copied the 1.3 update to the root folder of the NC via. the USB cable. You can obtain the 1.3 update here if you didn't earlier.
4) I unplugged the USB. After 2 min. the NC recognized the update, and it did it automatically. It went through a full boot and I then shut down the NC.
5) I put in my CMW SD card with 4.6.18 and 4.6.16a on it. I then plugged in my USB cable into my Nook again to force the launch of CMW
6) In the CMW backup menu, I launched from zip file the 4.6.18, then right afterwards, the 4.6.16a nooters.
7) I shut down the NC, removed the CMW card, and did a regular launch.
8) I chose ZEAM launcher as default
9) I went into ROM manager and fixed permissions.
10) I went into the Market, signed in, and accepted the info, and saw the full, beautiful market populate and I'm good to go.
Hopefully this is a fix that works for everybody.....
(and yes - I know there's a separate thread on how to re-root after 1.3, but it's more of a troubleshooting thread at this point and frankly there's SO much conflicting info. in there I thought it prudent to start a new thread)
jnmoriginpoint said:
My goal - a rooted 1.3 stock device that had full market access back the way 1.2 worked w/ market prior to the update.
I'll preface this by saying I've tried nearly everything from almost every post in XDA in the last month, but I still had no market access and had to side-load all my apks. I get the feeling that there are quite a few of us that tried manulNooter and various forms of tweaks but are still w/out market access so it is for us that I write this.
I read this today and with a slight tweaking of the steps, I now have ROCK SOLID full market access on the first try.
I'll flat out say that all of the work can be chalked up to other people's time and effort, it's only the steps that worked for me I'm outlining here.
Beforehand:
Make sure you have a bootable CWM card (linky)
Make sure you have updates 4.6.18 and 4.6.16a.
Get the B&N 1.3 update here since you're going to revert your NC back to stock
START:
1) Before updating to 1.3 firmware you are required to do a complete wipe (which requires an aborted power-up [simply hold power button down during the launch process] 8 times in a row - or MUCH easier: the following command using adbWirless ).
2) I waited for the whole B&N setup after the wipe and I went through the steps of registering the device to my B&N account, then I did a factory reset at the "Erase and Deregister the device". It relaunches B&N one more time. After restarting I simply shut down the device before registering it again.
3) I then plugged in my Nook via. USB cable to my PC. I copied the 1.3 update to the root folder of the NC via. the USB cable. You can obtain the 1.3 update here if you didn't earlier.
4) I unplugged the USB. After 2 min. the NC recognized the update, and it did it automatically. It went through a full boot and I then shut down the NC.
5) I put in my CMW SD card with 4.6.18 and 4.6.16a on it. I then plugged in my USB cable into my Nook again to force the launch of CMW
6) In the CMW backup menu, I launched from zip file the 4.6.18, then right afterwards, the 4.6.16a nooters.
7) I shut down the NC, removed the CMW card, and did a regular launch.
8) I chose ZEAM launcher as default
9) I went into ROM manager and fixed permissions.
10) I went into the Market, signed in, and accepted the info, and saw the full, beautiful market populate and I'm good to go.
Hopefully this is a fix that works for everybody.....
(and yes - I know there's a separate thread on how to re-root after 1.3, but it's more of a troubleshooting thread at this point and frankly there's SO much conflicting info. in there I thought it prudent to start a new thread)
Click to expand...
Click to collapse
There is no 4.6.18 update - did you mean 4.518?????
Haven't tried this as I am using CM7 nightly builds ... but
Files that you need are here:
http://forum.xda-developers.com/showpost.php?p=17235819&postcount=1
Best regards,
-boggsie
docfreed said:
There is no 4.6.18 update - did you mean 4.518?????
Click to expand...
Click to collapse
Thks - yes - 4.5.18 - and fwiw, while I was super-happy about the progress - I turned off the NC last night and on launch this morning I'm stuck in a boot loop at the NC logo. Looks like I'm moving to CM7 and use the LCD density method to get market access. SO disappointing.
jnmoriginpoint said:
Thks - yes - 4.5.18 - and fwiw, while I was super-happy about the progress - I turned off the NC last night and on launch this morning I'm stuck in a boot loop at the NC logo. Looks like I'm moving to CM7 and use the LCD density method to get market access. SO disappointing.
Click to expand...
Click to collapse
Thanks for giving this a shot and posting your experience. I am hoping that one of the smart developer types will work on a Manualnooter (let's say 4.7.0) that will take us from stock 1.3 to root with a fully functional Market. Please, I know you are out there.
By the way, if you load CM7 with a -200 nightly or later then you will not need the LCD density fix as it has already been incorporated. Happy hunting!
jnmoriginpoint said:
Thks - yes - 4.5.18 - and fwiw, while I was super-happy about the progress - I turned off the NC last night and on launch this morning I'm stuck in a boot loop at the NC logo. Looks like I'm moving to CM7 and use the LCD density method to get market access. SO disappointing.
Click to expand...
Click to collapse
Did you update flash? Thats what causes the loop, I had the same thing happen to me and had to start again from scratch. Make sure you don't update flash through the market or this will happen again.
bobzdar said:
Did you update flash? Thats what causes the loop, I had the same thing happen to me and had to start again from scratch. Make sure you don't update flash through the market or this will happen again.
Click to expand...
Click to collapse
THANK YOU SWEET JESUS
I decided to revert to stock and every time I turned my nook off, there was no return. Every time I reflashed, after I nootered I updated everything from the market. I spent 2 hours trying to find the reason as to why I kept getting bootloops.
This fixed it.
turdferguson92 said:
THANK YOU SWEET JESUS
I decided to revert to stock and every time I turned my nook off, there was no return. Every time I reflashed, after I nootered I updated everything from the market. I spent 2 hours trying to find the reason as to why I kept getting bootloops.
This fixed it.
Click to expand...
Click to collapse
There is a fix to allow updated flash, can't remember which thread but after going through it I have updated to flash v11 without issue. I also got the (latest) market working by going into titanium backup and doing a data wipe of the market app.
Well, I followed all the given instructions, even bobzdar's method after reflashing for the 5th time. I still cannot get full market access. Even amazon market cuts me off. I've come to the conclusion that my only solution will be to move on to cm7. Honestly though, I prefer the stock rom over cm7.
All I want is cut the rope, and boat browser. Is that too much to ask for? lol
turdferguson92 said:
Well, I followed all the given instructions, even bobzdar's method after reflashing for the 5th time. I still cannot get full market access. Even amazon market cuts me off. I've come to the conclusion that my only solution will be to move on to cm7. Honestly though, I prefer the stock rom over cm7.
All I want is cut the rope, and boat browser. Is that too much to ask for? lol
Click to expand...
Click to collapse
For whatever reason, the market took a while to load the first time, but now it works whenever I go into it. Try opening it up and doing a search for something and see what happens. I did a search for flash after running the flash fix to go right to the updated v11 and it took 30 seconds to a minute for the search to go through, but once it did the market has worked normally since. It was odd, but what kicked the whole thing off was doing the data wipe in titanium backup and all of a sudden it auto updated flash and a few other things (indicating market was working), which necessitated doing the flash fix through CWM etc. Now everything is working properly, hopefully it's just working slowly like it was for me and you just have to kind of kick start it by doing a search.
Thanks for the detailed steps, and to bobzdar for his tips. I too was having the "Nook Col" problem even after having done the flash trick, so I started all over and all is working...
EXCEPT, now I can't download my B&N books. I get this error: "Unable to Download: Internal error: Exception executing the command".
I did update superuser among other things, not sure if that made any difference. It won't let me install the Nook app thru the Market, either.
Any suggestions? I'd like to read my books and would prefer NOT to do this all over again LOL.
zogg44 said:
Thanks for the detailed steps, and to bobzdar for his tips. I too was having the "Nook Col" problem even after having done the flash trick, so I started all over and all is working...
EXCEPT, now I can't download my B&N books. I get this error: "Unable to Download: Internal error: Exception executing the command".
I did update superuser among other things, not sure if that made any difference. It won't let me install the Nook app thru the Market, either.
Any suggestions? I'd like to read my books and would prefer NOT to do this all over again LOL.
Click to expand...
Click to collapse
New book or one already in your library? I just downloaded a book from my library without issue but I don't know if I've tried to download a new book since getting the market working again.
bobzdar said:
For whatever reason, the market took a while to load the first time, but now it works whenever I go into it. Try opening it up and doing a search for something and see what happens. I did a search for flash after running the flash fix to go right to the updated v11 and it took 30 seconds to a minute for the search to go through, but once it did the market has worked normally since. It was odd, but what kicked the whole thing off was doing the data wipe in titanium backup and all of a sudden it auto updated flash and a few other things (indicating market was working), which necessitated doing the flash fix through CWM etc. Now everything is working properly, hopefully it's just working slowly like it was for me and you just have to kind of kick start it by doing a search.
Click to expand...
Click to collapse
Well, evry time I did those steps, the market homepage/top apps or whatever seemed to show up blank, saying "No items found" or something like that.
I just decided to go back to 1.2. I like the new market better anyway.
bobzdar said:
New book or one already in your library? I just downloaded a book from my library without issue but I don't know if I've tried to download a new book since getting the market working again.
Click to expand...
Click to collapse
Already in the library. I have about 12 and can't dl any of them. Haven't tried to buy a new book yet, but I doubt that will work either.
It's frustrating because I was w/o the Nook for several days, did all this stuff and it works well other than this and limited market apps which I can live with.
I may have to go thru the whole process again and make sure I dl everything before I apply the hacks.
Installed cmod7 stable (7.2) and the gapps file (found in another link - the one on nookdevs doesn't work). On first boot, it is stuck at a screen that just has a bar that says "Setup Wizard". The bar doesn't appear to be tapable. Search forum, no threads found on this.
Thanks in advance!
Dave
rebooted, still problems
dweaton said:
Installed cmod7 stable (7.2) and the gapps file (found in another link - the one on nookdevs doesn't work). On first boot, it is stuck at a screen that just has a bar that says "Setup Wizard". The bar doesn't appear to be tapable. Search forum, no threads found on this.
Thanks in advance!
Dave
Click to expand...
Click to collapse
I powered off and then on so it would reboot - it went through the setup screens. I get aborts of android.process.media so it won't let me go through the google play icon. When I try to click on Nookreader for android while on barnes and noble web site, it aborts again. I had the latest daily on here 2 days ago and was getting the same abort, but only twice when android first started. Tapping on google play then said "server error" and would NEVER work. Tried through the web - said I needed to use google play app - hence a big loop of nothing working. That's when I went to the "stable" version of 7.20 encore. It doesn't appear to want to do anything right.
Any advice on getting this all to work would be greatly appreciated. Using clockwork with the nook 1.4.3 firmware is getting old just to get back to a device that works, albeit not with full android.
dweaton said:
I powered off and then on so it would reboot - it went through the setup screens. I get aborts of android.process.media so it won't let me go through the google play icon. When I try to click on Nookreader for android while on barnes and noble web site, it aborts again. I had the latest daily on here 2 days ago and was getting the same abort, but only twice when android first started. Tapping on google play then said "server error" and would NEVER work. Tried through the web - said I needed to use google play app - hence a big loop of nothing working. That's when I went to the "stable" version of 7.20 encore. It doesn't appear to want to do anything right.
Any advice on getting this all to work would be greatly appreciated. Using clockwork with the nook 1.4.3 firmware is getting old just to get back to a device that works, albeit not with full android.
Click to expand...
Click to collapse
Perform it in two steps... first flash CM7 alone... reboot it... set up wifi... let it settle... THEN flash gapps and set up google stuff.
still stuck - different place
DizzyDen said:
Perform it in two steps... first flash CM7 alone... reboot it... set up wifi... let it settle... THEN flash gapps and set up google stuff.
Click to expand...
Click to collapse
Thanks so much for the help! I really want this to work!
I installed just CM7 and booted up - got one message about the media thing again but only one. I then went to set up wifi and now I'm stuck at that screen - then n button doesn't pop up anything to let me go back to something - like home.
I don't know if it makes any difference - I did the format data/system reset option then the cm7 flash, but it is still remembering my wireless settings somewhere as it automatically connects and it's a wpa2 network. Is there another step for erasing/formatting something that I missed?
Sorry to sound so stupid - but I'm completely a noob (LOVE the video on the registration page!).
Thanks so much again!
Dave:
nope - still not working
Well, installed cm7 and set up wifi, checked it was working by going to the web. Let it sit a few minutes, then reboot with the microSD and installed the gapps. Rebooted, went through google setup, then tried the google play via the icon on the home screen - same thing. It repeats the android.media.application abort message 2 times and then aborts the google play before I even get anywhere.
So......I'm wondering about my google apps zip file -> it said it was google apps for android 2.x.x, whereas I thought the cm7 I installed was android 3. Does this make a diffference?
Thanks again!
Dave :fingers-crossed:
Click here for the correct Gapps file:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
still failing
I downloaded the cmod 7.0 file and the gapps (thanks Hoser88!!), created the microSD, booted, did the format data/system reset and installed cmod 7.0. Rebooted, got the same 2 error messages about "android.media.application" aborting, then checked wireless and it was running.
Rebooted with the microSD and installed gapps, removed microSD and rebooted, got the same 2 error messages. Tapped on "Market", it showed a screen with something circling in the middle VERY briefly, then that closed out and the same 2 error messages came up again.
I'm starting to get worried, as I *think* I'm doing what I'm supposed to yet it doesn't work for me. Any and all suggestions are greatly appreciated!
Just to see what happens, I'm going to try the latest nightly cmod7 and see what that does.
Thanks!
Dave
same problems........
I made the microSD with the latest nightly of cmod 7 and the gapps pointed to above. I flashed cmod 7 first, booted, checked wireless, etc.. Still get the same 2 aborts about android.process.media on startup. I then booted again with the microSD and installed the gapps, removed microSD and rebooted. Got the same 2 aborts on startup. Tapped "Market", you see another screen the says "loading" very briefly, then that screen goes away and the android.process.media abort shows and I have to tap force close (this happens twice). I have no idea what this media process is, but is there a way to disable it? I get the feeling it is contributing to my problems.
I'm really lost here. I want this SO bad. I want to have full Android, and have both the Nook and Kindle reader apps so I can keep all my books on 1 device.
Thanks in advance!
dave
Tried more, still fails
I tried a recent suggestion on the cyanogen nook color forum: format data/factory reset and format /system, then install. I did this using the latest nightly and gapps - still got the same abort twice. Found another note in the cyanogen forum saying to go to the rom app and run set permissions and then reboot. I did that - STILL get the aborts. Can't get to google play (shows as "Market") get the quick "Loading" screen followed by immediate close of that and 2 more aborts for adroid.process.media.
I know it remembered my wireless, etc. again. Is there something else I need to format so it completely forgets everything so I'm starting from a clean slate? What can be causing the adroid.process.media abort and how do I get rid of it? Sometimes I think it thinks it is running on a phone, and obviously it's not - do I need to something additional for that as well?
I'm feeling quite confused right now. I've done everything from here and from what I read in the cyanogen nook color forum, but I still can't get this to work. What's the use of running cmod 7 if I can't access the google app store? Please help!
Thank you,
Dave
It works!!
Don't know WHAT I did - I just completely re-downloaded everything - the clockwork image (16gb), the cmod 7.0, and the gapps. Before installing, I went in with the existing install that wasn't working as it should and turned off several apps and cleared their cache when available. I then booted the new microSD - format data/system reset, format /system, installed cmod 7 zip and gapps zip. Removed microSD and rebooted. No more message about android.process.media aborting! It also asked me to set up my Google stuff again, so that was a step in the right direction. I then tried "Market", and IT WORKED!! It still aborts occasionally but I just go right back in and keep going. I did run into something I don't understand - the Nook for Android app page puts a message at the top saying it's not compatible with my device!! Huh? Do I need to may install cmod7.2 stable since this part is working now?
Thanks for the help!! If anyone could help me through the rest of this (get Nook for Android app, getting Kindle for Android app) then I should be good to go from there. I can always download other apps I might want, but I just want to get those 2 working first.
Thanks again!
Dave
It works and I have Kindle and Nook apps!
I updated to 7.20 stable (least wise I hope I did it right - I just flashed from zip but didn't format anything first). After that update I was able to get the B&N Nook reader and the Kindle reader apps! Everything seems to be working fine now - no aborts, nothing!
So.....a BIG THANK YOU to everyone who helped me out!
Thanks SO much!!
Dave :good:
mark as solved?
Some of the other forums I'm on have a set of thread tools - one of which lets you mark the thread as solved. Is there a tool like that on this forum (haven't found it yet if there is) ?
dweaton said:
Some of the other forums I'm on have a set of thread tools - one of which lets you mark the thread as solved. Is there a tool like that on this forum (haven't found it yet if there is) ?
Click to expand...
Click to collapse
Just edit your first post and rename it to [SOLVED] installed cmod7, stuck at "Setup Wizard"
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
i don't know what i did ,this tablet was working fine for 2 years with RR custom rom i used root junky tools to root and install RR custom rom,pico gaps, xposedframework ,and android custom boot animation from 5.0,1 , it was working one second and then all of a sudden the google app , gmail ,and youtube all say
" "app name" relies on google play services which is not supported by your device ,contact manufacturer "
how do i fix this and how did it happen? funny thing is that the play store still works and apps can update but i can't use any google apps
all i did was log into a secondary account and then try and install the google app which was already installed on the primary account , the google app stopped working then it worked and then it stopped again and now none of the google apps will work on either account,how do i fix this?
google play services version is 11.9.75(230-182402865)
i tried uninstalling the google app from the secondary account and then tried using gmail and youtube on the secondary account and it does not work, then tried on the primary account and it does not work , then i tried uninstalling the google app from the primary account
and rebooting , and it still does not work
how can i fix this without having to reflash everything?
how do i stop this from happening again?
and i have 2 other tablets i set ap the same way only on those i used flash fire because they were on 5.1.1 i think
do i now have to worry about it happening to those tablets too?
should i not ever update or install any google apps from the play store again?
update: ok this is really strange , i booted one of my other tablets i set up the same way only it was flashed with flash fire from 5.1.1 instead of 5.0.1 and TWRP
(i have 3 5th gen fire 7's running RR custom rom, root, with xposed , 2 were on 5.1.1 and flashed with flash fire and one was on 5.0.1 and flashed with TWRP , all with root junky tools)
i first went to gmail and then to youtube both worked fine , then i went to the play store and i updated an app , not an app that uses play services though,
then i noticed a notification pop up that said something about google play services not being supported on the device , so i went to launch gmail again and then it was doing the same thing as it was on the other tablet , then i launched youtube , and same thing
then like a minute later after closing the apps and trying them again , they worked fine
i really would like to to know what is going on here
next i will try the 3rd tablet, , that one was the last one i set up and has the least apps on it
just to be clear here the play store works just fine , i can update ,install and uninstall apps through it
and my account is visible in the playstore and my accounts show up in the tablet
just cant get any google apps like gmail ,youtube , google plus and the google app working
gdroid666 said:
i tried uninstalling the google app from the secondary account and then tried using gmail and youtube on the secondary account and it does not work, then tried on the primary account and it does not work , then i tried uninstalling the google app from the primary account
and rebooting , and it still does not work
how can i fix this without having to reflash everything?
how do i stop this from happening again?
and i have 2 other tablets i set ap the same way only on those i used flash fire because they were on 5.1.1 i think
do i now have to worry about it happening to those tablets too?
should i not ever update or install any google apps from the play store again?
update: ok this is really strange , i booted one of my other tablets i set up the same way only it was flashed with flash fire from 5.1.1 instead of 5.0.1 and TWRP
(i have 3 5th gen fire 7's running RR custom rom, root, with xposed , 2 were on 5.1.1 and flashed with flash fire and one was on 5.0.1 and flashed with TWRP , all with root junky tools)
i first went to gmail and then to youtube both worked fine , then i went to the play store and i updated an app , not an app that uses play services though,
then i noticed a notification pop up that said something about google play services not being supported on the device , so i went to launch gmail again and then it was doing the same thing as it was on the other tablet , then i launched youtube , and same thing
then like a minute later after closing the apps and trying them again , they worked fine
i really would like to to know what is going on here
next i will try the 3rd tablet, , that one was the last one i set up and has the least apps on it
just to be clear here the play store works just fine , i can update ,install and uninstall apps through it
and my account is visible in the playstore and my accounts show up in the tablet
just cant get any google apps like gmail ,youtube , google plus and the google app working
Click to expand...
Click to collapse
Google (any many 3rd party) apps rely on Google Play Services for core/shared functionality. Play Services/Framework is supposed to seemlessly auto-update in the background and usually does. Believe you saw that happen on your 2nd tablet. For whatever reason the framework appears borked on the 1st device.
As previously advised fixing Google Play Services issues is difficult/unreliable without a fresh install. Given you can boot twrp on the device having this issue I suggest the following:
- boot into TWRP and backup the current (nonworking) environment
- dirty flash RR, SuperSU and a suitable OpenGApps package
- verify everything is working correctly
- proceed to a 'clean' flash if the trouble persists
Dirty flashing will preserve existing apps/data/settings and is obviously less disruptive. Effectively the way a FireOS OTA update works. However, it doesn't always work and can create additional problems.
Davey126 said:
Google (any many 3rd party) apps rely on Google Play Services for core/shared functionality. Play Services/Framework is supposed to seemlessly auto-update in the background and usually does. Believe you saw that happen on your 2nd tablet. For whatever reason the framework appears borked on the 1st device.
As previously advised fixing Google Play Services issues is difficult/unreliable without a fresh install. Given you can boot twrp on the device having this issue I suggest the following:
- boot into TWRP and backup the current (nonworking) environment
- dirty flash RR, SuperSU and a suitable OpenGApps package
- verify everything is working correctly
- proceed to a 'clean' flash if the trouble persists
Dirty flashing will preserve existing apps/data/settings and is obviously less disruptive. Effectively the way a FireOS OTA update works. However, it doesn't always work and can create additional problems.
Click to expand...
Click to collapse
ok thanks so what kind of additional problems? nothing serious like bricking right?
i do not know the difference between clean and dirty flash so how would i go about that from TWRP
i don't even remember how to get TWRP , i assume i need to get the tablet into fastboot ,i also forgot how i do that
and i may have uninstalled the clockwork mod driver from my PC not sure if i need those or not
is there a guide you can link me to on how to get the tablet into tethered TWRP and which option i need to select from it , i think i have the files i used for the initial flash somewhere i should be able to find those, the RR rom, gapps ,
super SU
also where would the backup go exactly? to an SD card? would you happen to know how much space i would need , if it goes to internal then how do i get the backup to Sd?
also what about xposed framework would that remain intact after a "dirty flash"
should i also add the xposed framework to the zip at the time of dirty flash if not or would i have to do after?
i can not remember too much about how i set this thing up and this is probably the only time i have ever used TWRP , the other 2 tablets i used FF
also could i just a dirty flash from FF? , guess i should use TWRP since i can note make a backup with FF right?
EDIT: i really have no clue what i am doing here ,what are the chances that when google play services updates in the background next time it will just fix itself? should i wait a few weeks and see if it corrects itself 1st?
gdroid666 said:
EDIT: i really have no clue what i am doing here ,what are the chances that when google play services updates in the background next time it will just fix itself? should i wait a few weeks and see if it corrects itself 1st?
Click to expand...
Click to collapse
Try updating Google Play Services from here. It usually doesn't work but worth a shot given your level of familiarity with managing your custom build.
Davey126 said:
Try updating Google Play Services from here. It usually doesn't work but worth a shot given your level of familiarity with managing your custom build.
Click to expand...
Click to collapse
yeah i tried it a few times ,rebooted and tried again and it is snot working
it is weird because on gmail i can click outside the message box that says no google play services and then i see my gmail account and it says getting your messages , and syncing but it just hangs forever and with youtube i get notifications for new videos for channels i am subbed to, when i click on the notification and open youtube from there the video plays but there is no video just audio and the no google play services message is there and everything is greyed out but i can hear the sound from the video
gdroid666 said:
yeah i tried it a few times ,rebooted and tried again and it is snot working
it is weird because on gmail i can click outside the message box that says no google play services and then i see my gmail account and it says getting your messages , and syncing but it just hangs forever and with youtube i get notifications for new videos for channels i am subbed to, when i click on the notification and open youtube from there the video plays but there is no video just audio and the no google play services message is there and everything is greyed out but i can hear the sound from the video
Click to expand...
Click to collapse
Yep - not unexpected from a borked Play Services is install. You're probably gonna have to bit the bullet and perform a fresh install. At that time it may be wise to consider a shift to a different ROM. Nothing wrong with RR but it isn't being updated which could eventually lead to further issues.
Davey126 said:
Yep - not unexpected from a borked Play Services is install. You're probably gonna have to bit the bullet and perform a fresh install. At that time it may be wise to consider a shift to a different ROM. Nothing wrong with RR but it isn't being updated which could eventually lead to further issues.
Click to expand...
Click to collapse
well the rom is working on the other 2 tablets it acted up for a minute then worked again on one of them
i am wondering if that issue could be because i had the internal memory maxed out?
it was almost 100% full then i started moving some apps to the sd card , maybe it tried to update and ran out of memory or something and got only partially updated?
gdroid666 said:
well the rom is working on the other 2 tablets it acted up for a minute then worked again on one of them
i am wondering if that issue could be because i had the internal memory maxed out?
it was almost 100% full then i started moving some apps to the sd card , maybe it tried to update and ran out of memory or something and got only partially updated?
Click to expand...
Click to collapse
Possibly. Trying to perform forensics w/o supporting data is a bit of a fools errand. What happened to your device is neither common nor rare. I would focus on remediation which likely means an uncomfortable rebuild (due to unfamiliarity with procedures). You are fortunate to have TWRP access which removes most of the risk. Unless it self-resolves (unlikely) you're going to have to get your hands dirty one way or the other.
Davey126 said:
Possibly. Trying to perform forensics w/o supporting data is a bit of a fools errand. What happened to your device is neither common nor rare. I would focus on remediation which likely means an uncomfortable rebuild (due to unfamiliarity with procedures). You are fortunate to have TWRP access which removes most of the risk. Unless it self-resolves (unlikely) you're going to have to get your hands dirty one way or the other.
Click to expand...
Click to collapse
so what would the risk be if i were to try and side load the .APK's for the play services to try and fix it that way?
which .apk's would i need and in what order would i need to install them , is it worth a shot to try and manually install them from .apk and see hat happens?
if not and i need to do twrp route then would i install the xposed framework zip at the same time
can i flash the rom , gapps, super su , xposed, and custom boot animation zips or would i need to reboot 1st , which order would be best to line them up in TWRP to flash
also what do i do for dirty flash, ? just not wipe anything like dalvik cache? what do i wipe and not wipe?
ok i have booted into TWRP and i made a backup of everything including cache
now how would i go about dirty flashing
i just want to know what to do about xposed , will it remain in tact if i dirty flash the rom , gapps and super SU ?
or do i need to add the xposed zip when i do the dirty flash? would i need to also side load the xposed installer .apk after too again?
in what order do i need to add the zips to the install list? and what do i need to wipe and not wipe and what order?
gdroid666 said:
ok i have booted into TWRP and i made a backup of everything including cache
now how would i go about dirty flashing
i just want to know what to do about xposed , will it remain in tact if i dirty flash the rom , gapps and super SU ?
or do i need to add the xposed zip when i do the dirty flash? would i need to also side load the xposed installer .apk after too again?
in what order do i need to add the zips to the install list? and what do i need to wipe and not wipe and what order?
Click to expand...
Click to collapse
As a precaution you should copy (not move) the TWRP folder to off-line storage. If the folder is located in the external SD card that's reasonably safe. Take a deep breath and proceed as follows:
- verify you have all of the required zips located somewhere on the device or external SD card
- boot into TWRP
- wipe the system partition ONLY
- install the following zips in the order listed (individually or as a group; doesn't matter):
--> RR ROM
--> GApps package (suggest arm/5.1/nano; nothing larger than mini)
--> SuperSU 2.76 or 2.82 SR5 (avoid versions between 2.76 and 2.82)
--> Xposed Framework v89
Once all the of installations are complete accept the offer to wipe cache/dalvik and then reboot system.
Davey126 said:
As a precaution you should copy (not move) the TWRP folder to off-line storage. If the folder is located in the external SD card that's reasonably safe. Take a deep breath and proceed as follows:
- verify you have all of the required zips located somewhere on the device or external SD card
- boot into TWRP
- wipe the system partition ONLY
- install the following zips in the order listed (individually or as a group; doesn't matter):
--> RR ROM
--> GApps package (suggest arm/5.1/nano; nothing larger than mini)
--> SuperSU 2.76 or 2.82 SR5 (avoid versions between 2.76 and 2.82)
--> Xposed Framework v89
Once all the of installations are complete accept the offer to wipe cache/dalvik and then reboot system.
Click to expand...
Click to collapse
ok i am back again , i still have not done the dirty flash yet because i have been busy
i will probably try it soon with the original files i used to flash the rom and xposed with
but first i would like to get your input on this theory i have
ok i am thinking that because i have 3 5th gen fire 7 tablets all rooted and running custom roms ,and only one is having a problem , and that the one with the problem is the one with TWRP /unlocked bootloader
that this may be the cause of the problem
https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/
i have the same pico gapps flashed on all 3 devices but only one device has the unlocked bootloader
and that is the broken device , and the message that i get says " [app name] relies on google play services which is not supported by your device.please contact the device manufacturer"
i went into the play store under settings it did indeed say that the device is uncertified
i then installed an app to get my GFS device ID ,and converted the hexadecimal number into a decimal number and successfully submitted it to the whitelist site google/android/uncertified
it still did not fix the problem , then i cleared data and cache of the play store in settings/apps/play store
and tried again and nothing still , then i checked in play store settings and saw it no longer says incertified but it the field is gone completely now it does not say uncertified but it does not say certified either
then i went back to settings /apps/ google play store and removed updates and reverted back to factory play store and checked settings again there is still no field where the uncertified used to be and it is still not working
and now i don't know how to get the play store to update to latest version aside from sideloading it
i am not sure what to do next but what do you think about my tablet being broken because google now blocking gapps on uncertified devices as being the cause for this issue ,seems really strange to me that only the one tablet with the unlocked bootloader is being affected
but why did the whitelist also not work then ,i am really confused now and i am not seeing any other posts here about similar issues
gdroid666 said:
ok i am back again , i still have not done the dirty flash yet because i have been busy
i will probably try it soon with the original files i used to flash the rom and xposed with
but first i would like to get your input on this theory i have
ok i am thinking that because i have 3 5th gen fire 7 tablets all rooted and running custom roms ,and only one is having a problem , and that the one with the problem is the one with TWRP /unlocked bootloader
that this may be the cause of the problem
https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/
i have the same pico gapps flashed on all 3 devices but only one device has the unlocked bootloader
and that is the broken device , and the message that i get says " [app name] relies on google play services which is not supported by your device.please contact the device manufacturer"
i went into the play store under settings it did indeed say that the device is uncertified
i then installed an app to get my GFS device ID ,and converted the hexadecimal number into a decimal number and successfully submitted it to the whitelist site google/android/uncertified
it still did not fix the problem , then i cleared data and cache of the play store in settings/apps/play store
and tried again and nothing still , then i checked in play store settings and saw it no longer says incertified but it the field is gone completely now it does not say uncertified but it does not say certified either
then i went back to settings /apps/ google play store and removed updates and reverted back to factory play store and checked settings again there is still no field where the uncertified used to be and it is still not working
and now i don't know how to get the play store to update to latest version aside from sideloading it
i am not sure what to do next but what do you think about my tablet being broken because google now blocking gapps on uncertified devices as being the cause for this issue ,seems really strange to me that only the one tablet with the unlocked bootloader is being affected
but why did the whitelist also not work then ,i am really confused now and i am not seeing any other posts here about similar issues
Click to expand...
Click to collapse
Your non-functioning tablet does NOT have an "unlocked bootloader". It has a coding oversight that allows a custom recovery (TWRP) to be booted from fastboot. In all other respects it is identical to the other two from a capability/signature perspective.
The policy change/enforcement you reference is not the cause as Google only starting blocking access a couple weeks ago. Nor will it likely impact this device based on my interpretation of the criteria Google applies.
What to do next? Reload as previously outlined. I also recommend (rather strongly) that you consider migrating to a supported ROM. At present that's either Fire Nexus or Lineage.
ok i finally got around to doing this
after the flash everything looked good, but i am still getting no play services , can't open youtube or gmail still
i get play services not supported by this device
gdroid666 said:
ok i finally got around to doing this
after the flash everything looked good, but i am still getting no play services , can't open youtube or gmail still
i get play services not supported by this device
Click to expand...
Click to collapse
Sorry to hear that. Best move on to second recommendation from previous post.
Davey126 said:
Sorry to hear that. Best move on to second recommendation from previous post.
Click to expand...
Click to collapse
from what i have been reading trying to find a fix that probably will not work either
looks like a lot of people having this issue even with real android devices with factory roms including samsung phones on N and lenovo tablets
this OS is really turning into a complete dumpster fire, Google should have provided a fix but i feel that they are deliberately causing these issues to kill devices to drive sales or for some other nefarious purpose
either that or they are just totally incompetent
i have not seen a single person who posted that they have this issue get a resolution to it
how is this acceptable how have they not been sued for this yet?
i understand that this is a hacked Amazon device but this issue seems to persist across legit devices with factory roms as well and there is no official solution what are people to do if they bought an expensive Samsung device and have this unsolvable issue?
just toss it in the bin and buy a new one i guess
i can;t beleive there is no solution that is as simple as installing some .apk's
gdroid666 said:
from what i have been reading trying to find a fix that probably will not work either
looks like a slot of people having this issue even with real android devices with factory rom including samsung phone on N and lenovo tabets
this OS is really turning into a complete dumpster fire, Google should have provided a fix but i feel that they are deliberately causing these issues to kill devices to drive sales or for some other nefarious purpose
either that or they are just totally incompetent
i have not seen a single person who posted that they have this issue get a resolution to it
how is this acceptable how have they not been sues for this yet?
i understand that this is a hacked Amazon device but this issue seems to persist across legit devices with factory roms as well and there is no official solution what are people to do if they bought an expensive Samsung device and have this unsolvable issue?
just toss it in the bin and buy a new one i guess
Click to expand...
Click to collapse
Sorry, don't subscribe to that line of thought. Google Play Services issues are largely self inflicted and almost always resolvable. Move to a supported ROM and the problem will likely go away. If you dumpster it in favor of something different stay away from current gen Amazon gizmos. With exception to the HD 10 none are rootable. Good luck.
Davey126 said:
Sorry, don't subscribe to that line of thought. Google Play Services issues are largely self inflicted and almost always resolvable. Move to a supported ROM and the problem will likely go away. If you dumpster it in favor of something different stay away from current gen Amazon gizmos. With exception to the HD 10 none are rootable. Good luck.
Click to expand...
Click to collapse
Yes i will try a new rom i guess which one is the most like the one i have now ?
and do you happen to know if any of them will support casting from the quick settings shade?
I actually did just buy the fire HD 10 on prime day for that very reason
but besides root what exactly can be done with it?
I mean no there are no custom roms or TWRP yet right
is anyone working on TWRP or a custom rom?
I kinda think i might want to leave it on fire OS to try out the always listening Alexa and Alexa show capabilities
Is it like the fire 7 where i can already remove lock screen ads install play store and change the launcher to nova without root even?
What does root allow on the HD 10 that is useful right now?
Would it possible to install xposed and youtube adaway on it with fire OS?
I have not opened it yet so do all current FW's support root still?
does the FW that added the Alexa show capabilities to fire OS still support root?
gdroid666 said:
Yes i will try a new rom i guess which one is the most like the one i have now ?
and do you happen to know if any of them will support casting from the quick settings shade?
I actually did just buy the fire HD 10 on prime day for that very reason
but besides root what exactly can be done with it?
I mean no there are no custom roms or TWRP yet right
is anyone working on TWRP or a custom rom?
I kinda think i might want to leave it on fire OS to try out the always listening Alexa and Alexa show capabilities
Is it like the fire 7 where i can already remove lock screen ads install play store and change the launcher to nova without root even?
What does root allow on the HD 10 that is useful right now?
Would it possible to install xposed and youtube adaway on it with fire OS?
I have not opened it yet so do all current FW's support root still?
does the FW that added the Alexa show capabilities to fire OS still support root?
Click to expand...
Click to collapse
- I would go with Fire Nexus + Xposed and a few select modules for maximum flexibility if seeking to mimic the RR UX
- head here for the latest developments on HD 10 platform
- nothing wrong with curated FireOS + xposed once rooted. I ran with that config for quite some time with no regrets
No rom dev.
Can't get magisk in.
Dk magisk anyways
Xposed is doa? Or past it's prime.
Ok, how to gain root? Flash kernel which won't flash? Ow.
ǀcey said:
No rom dev.
Click to expand...
Click to collapse
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
ǀcey said:
Can't get magisk in.
Click to expand...
Click to collapse
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
ǀcey said:
Dk magisk anyways
Click to expand...
Click to collapse
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
ǀcey said:
Xposed is doa? Or past it's prime.
Click to expand...
Click to collapse
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
ǀcey said:
Ok, how to gain root? Flash kernel which won't flash? Ow.
Click to expand...
Click to collapse
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.
Thank you, for all of your information!
It helped me by heaps!
The biggest problem I was having, was thinking the phone was in fastboot when it wasn't.
When I figured that out, the phone was quickly up n running on Phh-Treble with GApps Gsi.
Magisk Manager vs apk uses were confusing. It's Modules I can more easily blindly understand due to knowing XPosed.
Magisk went in smoothly & successfully via the change extension fastboot method which you explained.
But it appears the same as before inside the OS It's there but not really in type of thing.
Everything but the f2fs file and Magisk did complain.
I have no idea what kernel actually made it in now.
Safetynet! Hahaha! Is a new thing for me.
My phone is PlayStore bonafide uncertified also now.
PlayStore, I tried some other gapps nothing really changes, it just reupdates back to where it was, if it does, anyways(I think).
I tried registering device too. Failed that!
Being Uncertified = no netflix, no bank apps(deal breakers to me). GPhotos 1/2-ish working. Gvoice, Gmail working great! Razer Themes.apk + Pandora disappeared. I miss Razer Themes Lockscreens alot! Razer gives only a play link.
I installed older Netflix & Bank app. Both working.
Play ignores netflix but updated Bank. The same Bank app did stop working on a deemed outdated device in the past. It's not Chase but close.
I did try hiding things from the launcher via an other installed launcher.
An old Selinux(sp?) showed set to permissive. I changed to enforced, rebooted and it appeared to stick.
I installed Greenify(old) and stopped everything then did my monthly banking business, paid, xferred, etc. All transactions were confirmed. Boot still unlocked.
Soon afterwards, I installed Aptoide which informed me of root.
The Gsi's package Installer, won't install anything from within Es(I'm a diehard Es file manager user). The built-in file manager must be used to call the installer. The built-in file manager also crashes when searching.
A buggy installer I can deal with. Banking without it's app, I can not.
A halfbaked PlayStore is doable but not ideal.
The gsi itself on a RP2 is beautiful. The darks darker. The flashlight toggle works now! The fingerprint sensor never worked, still doesn't. 120fps, few games bake that capablity in. I haven't tested yet. No sound in Wyze app.
I recommend having your fav most used .apks dled before leaping onto it.
First boot was loud! Be prepared!
Then nothing.
2 days later, I noticed all alarms & notifications were set to silent sound.wav.
Idk, where to go from here. Stick to where it is now & wait for fixes. Go back. Or to go patch crazy if I can manage to get Magisk in.
I'm happy enough where it is now and it feels pretty secure. Will relocking the bootloader wipe it? The adult in me thinks.
But! I love tweaking...zzz
Relocking undoes it
LSS4181 said:
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.
Click to expand...
Click to collapse
I have one of the faulty charging ports so cannot do anything with USB. I do have my bootloader unlocked so is there any way to get the gsi's, twrp and root onto the phone via SD card? Any help is appreciated.