Already had an idea to possible getting some of the FireStarter options back thru XPosed Modules mentioned in a thread. But once @SimLynks - [TOTAL MOD] Playing With Fire excellent tutorial was release. I was able to guess that XPosed Edge Pro would be the best option to try. Thanks @SimLynks for the great MOD.
This is a walk-thru on how to get the old FireStarter Boot & Home button options working again using the fullest XPosed Module I've seen. This is only fully compatible with ROOTED FireTV (Sticks). This should work for just about any app including FireStarter, AppStarter, Kodi, SPMC, MrMC, etc. This will let you upgrade past FireOS 5.0.5 to the latest FireOS 5 Pre-Rooted roms & enjoy the new UI & bug fixes. A mouse is not require for installing or changing XPosed Edge settings. Since long pressing brings out sub-menus.
Requirements:
1. Rooted FireTV device.
2. XPosed Edge Pro. (More Triggers for boot startup is only available in the Pro version)
Should work on either FireOS 5 or even FireOS 3.
3. Must have installed XPosed Module & Manager App.
4. You have a functioning FireStarter or AppStarter or Kodi or SPMC, MrMC, etc.
5. Read the whole post before getting started.
You do not need the Pro version but @ $1.99 it is a great way to support the developer of this module. And the Pro version will let you do more with this module.
Download & install XPosed Edge Pro v3.9. This can be done thru sideloading. Since the Pro version is needed. Once you have it installed & checked. You will need to reboot your device for it to become active. Change the following settings after you reboot your device. The last setting will not work unless you have the XPosed Edge module activated. And for that you must do a reboot on your device.
1. Start XPosed Edge. Go down to "More triggers". (Only available in the Pro version)
2. Choose "Boot completed".
3. Choose "App".
4. Choose "FireStarter/AppStarter" or "Kodi" or "SPMC" or "MrMC". Depending on your taste.
5. Now your "Boot completed " should show the icon of the App you choose.
6. Now hit back once. And go up to "Keys".
7. Now choose "Home".
8. You should have the option to change "Click", "Double click" & "Long press".
9. Go to & choose "Click".
10. Go to "App".
11. Choose "FireStarter/AppStarter" or "Kodi" or "SPMC" or "MrMC". Depending on your taste.
12. Now your "Click " should show the icon of the App you choose.
13. Now go down to "Double click".
14. In my case I choose to go "Home" when ever I "Double click". You can choose something else.
( I was not able to choose/find "Settings" like we could before. Might be a FW bug. Wonder if that got fix on the latest update.)
15. You should see the icon of what ever you choose for your "Double click". I decided to leave the long press as default.
16. Now go up to "Home".
17. Now long press "OK/Enter" on "Home" until you get to the check box menu.
18. In the check box menu choose "Enable".
19. You will now see the a check in the checkbox for "Home".
20. Hit back one time to go back to the main menu.
21. On the main menu. Go to "Keys" & long press until the checkbox menu shows up.
22. Then choose "Enable".
23. You should now see a check in the "Keys" checkbox & you should see a small popup letting you know that "Key control on" is activated.
Congrats. You now have a FireStarter/AppStarter auto-starting at bootup. And you have full control over your Home button.
I only tried this with AppStarter so there might be some minor tweaks that need to be done with FireStarter or Kodi or SPMC or MrMC but they should be minor. Let us know how it goes for you'll.
Thanks to @SimLynks post here for clarifying that the Pro version is needed to follow this walk-thru. He did mention an option to use his [TOTAL MOD] Playing With Fire directions on how to disable the default FireTV launcher. I myself prefer to just pay the $1.99 for the Pro version. But you do have a choice.
- Will add "running apps list" pics & option in the next few days.
- Updated the walk-thru to reflect that the XPosed Edge Pro version is required to follow it.
Nice how-to. THX a lot.
I will test it in a few days, when I had some time for it.
Good to see that the long waitiung time for a soltuion like rbox-mods did it, has an end!!!
Greetings by Idijt
Thanks for the great guide! Do you have a first gen stick? I was wondering about the performance on it with this set up. I'm currently still on 5.05 with my first gen stick. I had tried never ROM previously but it had noticable lags. Went back to 5.05.
Metconnect2000 said:
Thanks for the great guide! Do you have a first gen stick? I was wondering about the performance on it with this set up. I'm currently still on 5.05 with my first gen stick. I had tried never ROM previously but it had noticable lags. Went back to 5.05.
Click to expand...
Click to collapse
All my devices are Rooted FireTV 1's.
@Y314K Great work on this guide how to configure some of the more detailed features of this awesome Xposed Mod.
However this guide specifically uses "More Triggers" which IS a Pro-Only feature. Users can accomplish a similar task by following parts of my info on this module over in the Playing with Fire MOD thread, but would need to disable the default FireTV launcher instead of using the Pro-Only Triggers feature.
I do agree that Jozein deserves some money for this awesome Module, but there are definitely a large majority of users who will refuse to pay for basically anything (at least until they try the free version and then realize they want "more" so pay for pro). You might want to consider doing a separate section on how to do this using the free only features, just a thought.
Also I'd recommend suggesting users add in the "running apps list" to Home Double Click or Home Long Press, so that they get access to the Task Switcher built into this Module. Definitely one of my favorite features from XEdge that was missing from FireOS.
Metconnect2000 said:
Thanks for the great guide! Do you have a first gen stick? I was wondering about the performance on it with this set up. I'm currently still on 5.05 with my first gen stick. I had tried newer ROM previously but it had noticeable lags. Went back to 5.05.
Click to expand...
Click to collapse
Curious if the non-voice remote is being used? Seems to cause slower/choppy navigation with registering input compared to a bluetooth game controller or k400r keyboard on a first gen stick. This was just general observation between 5.0.5 and 5.2.4.1, before the Xposed Edge/Pro module. The xposed module route offers a much cleaner, more responsive approach to the FireStarter home button and start-on-boot features.
Axecaster said:
Curious if the non-voice remote is being used? Seems to cause slower/choppy navigation with registering input compared to a bluetooth game controller or k400r keyboard on a first gen stick. This was just general observation between 5.0.5 and 5.2.4.1, before the Xposed Edge/Pro module. The xposed module route offers a much cleaner, more responsive approach to the FireStarter home button and start-on-boot features.
Click to expand...
Click to collapse
Cool. Thanks. Yes I have a non voice remote. It seems that there first gen stick is so sluggish at times. Haven't used it for a while. Was hoping to debloat and make it more snappier.
Metconnect2000 said:
Cool. Thanks. Yes I have a non voice remote. It seems that there first gen stick is so sluggish at times. Haven't used it for a while. Was hoping to debloat and make it more snappier.
Click to expand...
Click to collapse
If debloat is what your looking for, I suggest you checkout the firestick-loader project over at Github. https://github.com/esc0rtd3w/firestick-loader
Seems this does everything it can to remove non-essential packages from the FireStick, is also one of the source I used to know what was safe or not-safe to remove.
SimLynks said:
If debloat is what your looking for, I suggest you checkout the firestick-loader project. Seems this does everything it can to remove non-essential packages from the FireStick, is also one of the source I used to know what was safe or not-safe to remove.
Click to expand...
Click to collapse
Is there any way you can point me in the direction of the Fire TV version of the Amazon App Store? Can you upload the apk and post a link maybe?
I'm sorry for asking newbie question regards Must have installed XPosed Module & Manager App.
Where can I find xposed module and manager app?
One more, is anyway I could get rid of kingroot?
I have twrp installed, is any way I could just load any fresh prerooted ROM? My Amazon version is 5.2.1.0 and I wish I could have working firestarter. If I ask too much please disregard my post.5.2.1.0
Thank you
netgar said:
I'm sorry for asking newbie question regards Must have installed XPosed Module & Manager App.
Where can I find xposed module and manager app?
One more, is anyway I could get rid of kingroot?
I have twrp installed, is any way I could just load any fresh prerooted ROM? My Amazon version is 5.2.1.0 and I wish I could have working firestarter. If I ask too much please disregard my post.5.2.1.0
Thank you
Click to expand...
Click to collapse
The XPosed version depends which FTV device you have. Can you be more specific ? FT1, FTV2 or FTVS1 ?
Best XPosed tutorial is in Section 4:
http://marksmods.com/Hack-the-Fire-TV/How-to-Install-Android-TV-on-the-Fire-TV-page2.html#xposed
I usually install the zip XPosed Framework right after installing a PreRooted ROM.
To get rid of KinRoot just follow this guide & reflash your PreRooted ROM:
http://www.aftvnews.com/how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery/
Y314K said:
The XPosed version depends which FTV device you have. Can you be more specific ? FT1, FTV2 or FTVS1 ?
Best XPosed tutorial is in Section 4:
http://marksmods.com/Hack-the-Fire-TV/How-to-Install-Android-TV-on-the-Fire-TV-page2.html#xposed
I usually install the zip XPosed Framework right after installing a PreRooted ROM.
To get rid of KinRoot just follow this guide & reflash your PreRooted ROM:
http://www.aftvnews.com/how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery/
Click to expand...
Click to collapse
Thank you so much for your help. I use FTV2.
So, just do factory reset, I bet if I do it I will loose my kingroot and my ROM won't be rooted is it right?
Is is possible to wipe the system somehow in TWRP and just flash prerooted ROM?
Thank you again...
netgar said:
Thank you so much for your help. I use FTV2.
So, just do factory reset, I bet if I do it I will loose my kingroot and my ROM won't be rooted is it right?
Is is possible to wipe the system somehow in TWRP and just flash prerooted ROM?
Thank you again...
Click to expand...
Click to collapse
1. When rooted & with TWRP installed. Only do Factory Reset from TWRP.
2. You never need to include /System in any wipe. Even Factory Reset. Since flashing a PreRooted ROM will take care of /System.
3. If you ever do wipe /System make sure you flash a PreRooted ROM before any reboot or power down or you will brick.
4. For FTV1's & FTV2's I strongly recommend you use a Fat32 USB stick to flash anything on TWRP.
Y314K said:
1. When rooted & with TWRP installed. Only do Factory Reset from TWRP.
2. You never need to include /System in any wipe. Even Factory Reset. Since flashing a PreRooted ROM will take care of /System.
3. If you ever do wipe /System make sure you flash a PreRooted ROM before any reboot or power down or you will brick.
4. For FTV1's & FTV2's I strongly recommend you use a Fat32 USB stick to flash anything on TWRP.
Click to expand...
Click to collapse
Ohh... I installed prerooted ROM and I did factory reset from TWRP and I stocked on "formatting cashe using make_ext4fs..." for the last 20min or more
Thats mean I bricked it? ohhh
Right now I loop coming back to TWRP and reboots again What to do to fix it?
netgar said:
Ohh... I installed prerooted ROM and I did factory reset from TWRP and I stocked on "formatting cashe using make_ext4fs..." for the last 20min or more
Thats mean I bricked it? ohhh
Right now I loop coming back to TWRP and reboots again What to do to fix it?
Click to expand...
Click to collapse
Seems you where using the old FireOS 3 external storage script. Not sure there was an .zip uninstall for it. Did u always had a USB Drive/Stick connected to your device ? Are you still connecting to it ?
Actually that was never used on FTV2's.
Try to do a Factory Reset in TWRP but don't reboot (hit the HOME button on the middle-bottom). Then flash the PreRooted ROM. Then reboot. But take the USB stick out after it starts to reboot.
Y314K said:
Seems you where using the old FireOS 3 external storage script. Not sure there was an .zip uninstall for it. Did u always had a USB Drive/Stick connected to your device ? Are you still connecting to it ?
Actually that was never used on FTV2's.
Try to do a Factory Reset in TWRP but don't reboot (hit the HOME button on the middle-bottom). Then flash the PreRooted ROM. Then reboot. But take the USB stick out after it starts to reboot.
Click to expand...
Click to collapse
I dont use USB stick, just ds card.
This is what I get when Iam trying to flash prerooted ROM
netgar said:
I dont use USB stick, just ds card.
This is what I get when Iam trying to flash prerooted ROM
Click to expand...
Click to collapse
Never seen that error. You'll need a USB hub to try using a USB keyboard & USB stick. Also make sure you include a MD5 file so TWRP can verify the PreRooted ROM is not corrupted.
http://www.aftvnews.com/how-to-use-twrps-built-in-md5-file-integrity-checker-to-avoid-bricking/
You can try using the SDCard again. Just add a MD5 file for the TWRP verification.
Y314K said:
Never seen that error. You'll need a USB hub to try using a USB keyboard & USB stick. Also make sure you include a MD5 file so TWRP can verify the PreRooted ROM is not corrupted.
http://www.aftvnews.com/how-to-use-twrps-built-in-md5-file-integrity-checker-to-avoid-bricking/
You can try using the SDCard again. Just add a MD5 file for the TWRP verification.
Click to expand...
Click to collapse
This is something to do with "cache"
Please look at this: https://forum.xda-developers.com/fire-tv/help/fire-tv-2-boot-loop-twrp-t3648309
Looks like it is the same problem.
how to run this command in adb shell? I have no clue
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Click to expand...
Click to collapse
netgar said:
This is something to do with "cache"
Please look at this: https://forum.xda-developers.com/fire-tv/help/fire-tv-2-boot-loop-twrp-t3648309
Looks like it is the same problem.
how to run this command in adb shell? I have no clue
Click to expand...
Click to collapse
For TWRP terminal you just go to Advanced in the main TWRP menu. You can find it there. Then follow RBox link info for cache loop.
So make sure you have Cache UNMounted in the TWRP mount menu first. Before you run the command.
Related
Just purchased a used KFHD 8.9 and would like to root. I would like to use Prokennexusa "How To" for Newbs but have a few questions before proceeding. I'm a brand new XDAD member and literally spent hours researching this site and others.
I don't really care with version of the Kindle I'm running. If I could get this to run Jelly Bean and nuke the Kindle OS it wouldn't be the end of the world. But I'm not in a crazy rush either, and am willing to wait if I need to.
1. Can I root with version 8.3.1 running, or do I need to restore to factory settings while offline and block OTA updates before I can start Prokennexusa's Newb instructions?
2. Are the KFHD 7 and 8.9 interchangeable in terms of how the root process works?
Apologies if I'm threadjacking on my first day or asking questions that have been answered in technical language I didn't understand, and thanks in advance for any help.
XP
Rooting Kindle Fire HD 8.9" Version 8.3.1
I rooted my Amazon Kindle Fire HD version 8.3.0 and along comes a new update 8.3.1 and it overwrites my rooted device. I have talked with two guys at RootPro.com and neither of them had a solution for rooting the new version. If someone comes up with the solution, I would be interested.
currensb said:
I rooted my Amazon Kindle Fire HD version 8.3.0 and along comes a new update 8.3.1 and it overwrites my rooted device. I have talked with two guys at RootPro.com and neither of them had a solution for rooting the new version. If someone comes up with the solution, I would be interested.
Click to expand...
Click to collapse
Just curious, did you simultaneously disable all OTA updates when you rooted? I may have misunderstood posters on some other threads, but it seems Amazon has found away to get the root-killing OTA's on Kindles that have been set to disable them...
I also have kfhd 8.9 running on version 8.3.1. I am trying to install 2nd-bootloader for custom ROMs. When running adb command I get the error that no device found even though I can get into fastboot. I don't know what to do. I believe that I need to be root to use adb and for it to recognize my device? Maybe need to install root and also driver for usb? I'm so confused. However, this thread makes it appears that I can't root the device for my version of kfhd. Any advice is appreciated if I need to be root and if I also need to find drivers as well even though I have downloaded the latest android sdk.
AlexAquarium said:
I also have kfhd 8.9 running on version 8.3.1. I am trying to install 2nd-bootloader for custom ROMs. When running adb command I get the error that no device found even though I can get into fastboot. I don't know what to do. I believe that I need to be root to use adb and for it to recognize my device? Maybe need to install root and also driver for usb? I'm so confused. However, this thread makes it appears that I can't root the device for my version of kfhd. Any advice is appreciated if I need to be root and if I also need to find drivers as well even though I have downloaded the latest android sdk.
Click to expand...
Click to collapse
You can root your device on 8.3.1 I did it last night.
The following assumes windows 7.
First, you need to have adb enabled on the KFHD.
Once you've done that, connect the device and try adb devices. If you get an empty list you need to have the correct drivers installed. That took me a while. In the device manager on your pc uninstall the kfhd. Google kindle fire hd usb driver and you will go to an amazon page that gives you instructions as to how to install the correct adb driver for the kfhd (you have to run a program called Kindlefireusb.exe (or something like that). That will then install the correct driver. Now reconnect your device and type adb devices again once the devices have been recognised. The list of devices should no longer be empty but should show the serial number of your device.
Next you can go on to root the device - i used the Sony experia method, although I had to do it twice.
Once you're rooted, then you can install twrp using the instructions on the second bootloader thread.
I'm on my mobile at the moment, I will update this post a little later on from my pc with more detail.
Sent from my GT-N7100 using Tapatalk 2
apd said:
You can root your device on 8.3.1 I did it last night.
The following assumes windows 7.
First, you need to have adb enabled on the KFHD.
Once you've done that, connect the device and try adb devices. If you get an empty list you need to have the correct drivers installed. That took me a while. In the device manager on your pc uninstall the kfhd. Google kindle fire hd usb driver and you will go to an amazon page that gives you instructions as to how to install the correct adb driver for the kfhd (you have to run a program called Kindlefireusb.exe (or something like that). That will then install the correct driver. Now reconnect your device and type adb devices again once the devices have been recognised. The list of devices should no longer be empty but should show the serial number of your device.
Next you can go on to root the device - i used the Sony experia method, although I had to do it twice.
Once you're rooted, then you can install twrp using the instructions on the second bootloader thread.
I'm on my mobile at the moment, I will update this post a little later on from my pc with more detail.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I appreciate your reply. I've never rooted anything, so just wanted to request that nothing be taken for granted. From what I understand, people who know what they're doing have bricked kindle hd's.
I was able to google "enable adb kindle fire 8.9" and got instructions saying to go to settings, then security.
But a couple of quick questions:
I wasn't sure what this meant:
"connect the device and try adb devices. If you get an empty list you need to have the correct drivers installed. That took me a while. In the device manager on your pc uninstall the kfhd."
Is the Sony experia method different from Prokennexusa's "how to" for noobs?
Also, is twrp the auto update disabler?
I'll hold off on doing anything until everything's confirmed.
Thanks again,
XP
herp derp
XPwasn'treallythatbad said:
But a couple of quick questions:
I wasn't sure what this meant:
"connect the device and try adb devices. If you get an empty list you need to have the correct drivers installed. That took me a while. In the device manager on your pc uninstall the kfhd."
I'll hold off on doing anything until everything's confirmed.
Thanks again,
XP
Click to expand...
Click to collapse
Have you got the Android SDK installed? If so, press Windows key + R and type "cmd".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From there type "adb devices" (without quotes ofcourse). If you see something like this:
Then download this and install it:
Kindle Fire ADB Drivers
If you installed that before or just installed it now you should get a screen like this (but with a different serial number)(i blocked mine ;D):
If you did, you have successfully got ADB to connect to your kindle!
XPwasn'treallythatbad said:
Is the Sony experia method different from Prokennexusa's "how to" for noobs?
Click to expand...
Click to collapse
Yes, since that was for the 7' variant of KFHD
Try this one:
KFHD 8.9 Root method
XPwasn'treallythatbad said:
Also, is twrp the auto update disabler?
Click to expand...
Click to collapse
No, TWRP (Team Win Recovery Project) is a custom recovery for android for installing custom ROMs like CyanogenMod. To install that go here:
Install 2nd-Bootloader with TWRP
Credit to Hashcode.
Excellent summary and thanks for saving me the time in doing it!
Only one comment - the above will only work if the location of adb.exe is in your PATH for your computer (else you will have to run adb from wherever it is installed in your computer, which may be C:\Users\[USERNAME]\AppData\Local\Android\android-sdk\platform-tools which is a bit of a pain!).
Good luck!
apd said:
Excellent summary and thanks for saving me the time in doing it!
Only one comment - the above will only work if the location of adb.exe is in your PATH for your computer (else you will have to run adb from wherever it is installed in your computer, which may be C:\Users\[USERNAME]\AppData\Local\Android\android-sdk\platform-tools which is a bit of a pain!).
Good luck!
Click to expand...
Click to collapse
I totally forgot about that! Thanks man ;D
dugoy13 said:
Have you got the Android SDK installed? If so, press Windows key + R and type "cmd".
From there type "adb devices" (without quotes ofcourse). If you see something like this:
Then download this and install it:
Kindle Fire ADB Drivers
If you installed that before or just installed it now you should get a screen like this (but with a different serial number)(i blocked mine ;D):
If you did, you have successfully got ADB to connect to your kindle!
Yes, since that was for the 7' variant of KFHD
Try this one:
KFHD 8.9 Root method
No, TWRP (Team Win Recovery Project) is a custom recovery for android for installing custom ROMs like CyanogenMod. To install that go here:
Install 2nd-Bootloader with TWRP
Credit to Hashcode.
Click to expand...
Click to collapse
apd said:
Excellent summary and thanks for saving me the time in doing it!
Only one comment - the above will only work if the location of adb.exe is in your PATH for your computer (else you will have to run adb from wherever it is installed in your computer, which may be C:\Users\[USERNAME]\AppData\Local\Android\android-sdk\platform-tools which is a bit of a pain!).
Good luck!
Click to expand...
Click to collapse
dugoy13 said:
I totally forgot about that! Thanks man ;D
Click to expand...
Click to collapse
Much appreciated.
Have you successfully disabled OTA updates, or is that not necessary?
XPwasn'treallythatbad said:
Much appreciated.
Have you successfully disabled OTA updates, or is that not necessary?
Click to expand...
Click to collapse
If you go to CM10, then there is no chance of an OTA update. If you stay on stock, there is a risk of OTA update. Lizzord in his ROM (here) thinks he has blocked OTA. I thought I had blocked OTA with KindleFreePro but that didn't work. I personally don't see any need to stay with the Stock ROM, with its bloatware, now that the CM10 ROm is doing so well.
Apd, thank you for much appreciated advice. I was able to get the amazon drivers installed and adb to recognize the device. I tried dugoy13's link to install root using option 1 and then followed Hashcode's instruction to put cynogenmod on my kindle. I only see few apps installed just the really basic stuff. Where's play store? The google search bar I have don't have the mic icon on it either. How do I go about installing apps?
AlexAquarium said:
Ok I'm in cynogemod10.1 and I only see few apps installed just the really basic stuff. Where's play store? The google search bar I have don't have the mic icon on it either. How do I go about installing apps?
Click to expand...
Click to collapse
What a huge post - not entirely necessary! Anyway, if your app drawer doesn't include Google Play, try reinstalling the google apps (i.e. reinstall the gapps ...zip in TWRP) as they include Google Play. You will need to manually install some of the other google apps (such as maps) using google play.
There's no audio input on CM10.1 on the KFHD8.9 yet - only audio output. Hashcode is working on it.
apd said:
What a huge post - not entirely necessary! Anyway, if your app drawer doesn't include Google Play, try reinstalling the google apps (i.e. reinstall the gapps ...zip in TWRP) as they include Google Play. You will need to manually install some of the other google apps (such as maps) using google play.
There's no audio input on CM10.1 on the KFHD8.9 yet - only audio output. Hashcode is working on it.
Click to expand...
Click to collapse
Apd I cleaned up my messages, it was sort of a stream of questions that I resolved myself and felt people should know since I asked. But it is a mess As for reinstalling gapps, do I need to uninstall,wipe clean anything or just go to install and select gapps to install? Thanks.
AlexAquarium said:
Apd I cleaned up my messages, it was sort of a stream of questions that I resolved myself and felt people should know since I asked. But it is a mess As for reinstalling gapps, do I need to uninstall,wipe clean anything or just go to install and select gapps to install? Thanks.
Click to expand...
Click to collapse
No I would simply reinstall the gapps (from within TWRP). it might be an idea to wipe the cache and the dalvik afterwards but do not wipe anything else as you risk wiping the apps you have just installed!
PS Thanks for cleaning up the thread!
apd said:
No I would simply reinstall the gapps (from within TWRP). it might be an idea to wipe the cache and the dalvik afterwards but do not wipe anything else as you risk wiping the apps you have just installed!
PS Thanks for cleaning up the thread!
Click to expand...
Click to collapse
Not a problem, didn't realize I can edit past posts, I'll keep it cleaner in the future. Thanks again, reinstall gapps file worked!
Apd one more thing. I know that I need to wipe the "System and "Factory Reset" (no idea what it's doing behind the scene) when installing from amazon stock. But if Hashcode release a new build with me having his previous build, should I wipe anything before installing his new cm10.1 build? Do i just select the Install from TWRP for the new build? If there is no new gapps, I don't need to reinstall gapps correct?
There is also option of side load(dirty flash?) which also can be done in TWRP. So it's confusing which way to proceed. So essentially what are the steps for installing a new build? I think my install from stock did not install gapp correctly because I installed both at the same time instead of one at a time such as the cm10.1 build reboot and install gapps and reboot. Thanks for all your tips.
AlexAquarium said:
Apd one more thing. I know that I need to wipe the "System and "Factory Reset" (no idea what it's doing behind the scene) when installing from amazon stock. But if Hashcode release a new build with me having his previous build, should I wipe anything before installing his new cm10.1 build? Do i just select the Install from TWRP for the new build? If there is no new gapps, I don't need to reinstall gapps correct?
There is also option of side load(dirty flash?) which also can be done in TWRP. So it's confusing which way to proceed. So essentially what are the steps for installing a new build? I think my install from stock did not install gapp correctly because I installed both at the same time instead of one at a time such as the cm10.1 build reboot and install gapps and reboot. Thanks for all your tips.
Click to expand...
Click to collapse
Factory reset: erase all user data and apps but preserve the ROM itself.
Wipe system: wipes the ROM including apps and userdata but preserves the content of the internal SD card
Dirty flash: flash a new ROM over an existing one without performing a wipe beforehand. Still recommended to wipe cache and dalvik (don't ask what they are (Google!), just do it!)
Sideload: can mean many things but in this context usually means pushing a file via adb
When a new ROM is published, if it is an iterative change to the existing ROM (ie no major changes to the underlying ROM) then it is often safe to dirty flash but if you have problems then you should wipe and reflash the ROM. The creator of the ROM will usually say if it is safe to do a dirty flash. If you dirty flash you will not need to reinstall gappps or other apps. If you wipe you will.
Some tips. Before flashing a new ROM, take a backup in TWRP. This takes some time but it means that if something goes wrong with the the new ROM you have a backup of your entire previous setup.
Also, download (and buy) a copy of Titanium Backup and learn how to use it. This allows you to backup all your apps and their settings in one go so if you have to wipe, you can reinstall all your apps and their settings in one go. It very rarely causes problems. It is not recommended to reinstall system apps or settings using titanium unless the ROM is very similar to the previous ROM.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
apd said:
Factory reset: erase all user data and apps but preserve the ROM itself.
Wipe system: wipes the ROM including apps and userdata but preserves the content of the internal SD card
Dirty flash: flash a new ROM over an existing one without performing a wipe beforehand. Still recommended to wipe cache and dalvik (don't ask what they are (Google!), just do it!)
Sideload: can mean many things but in this context usually means pushing a file via adb
When a new ROM is published, if it is an iterative change to the existing ROM (ie no major changes to the underlying ROM) then it is often safe to dirty flash but if you have problems then you should wipe and reflash the ROM. The creator of the ROM will usually say if it is safe to do a dirty flash. If you dirty flash you will not need to reinstall gappps or other apps. If you wipe you will.
Some tips. Before flashing a new ROM, take a backup in TWRP. This takes some time but it means that if something goes wrong with the the new ROM you have a backup of your entire previous setup.
Also, download (and buy) a copy of Titanium Backup and learn how to use it. This allows you to backup all your apps and their settings in one go so if you have to wipe, you can reinstall all your apps and their settings in one go. It very rarely causes problems. It is not recommended to reinstall system apps or settings using titanium unless the ROM is very similar to the previous ROM.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
Click to expand...
Click to collapse
Awesome. You are a very informative. Thank you. From what you say, the TWRP's Install option seems very similar to TWRP's Sideload option then. I use adp to push the zip files to my kindle and then in TWRP perform the install operation. If I go into TWRP's Sideload option, I presume it will get the zip file from my pc and install it and thus saving me an extra step.
Much easier to install than sideload . Just copy the file from your pc to the tablet before you reboot into Twrp. Our better still, download the file directly from the Web on to your tablet and then reboot into twrp!
Sent from my GT-N7100 using Tapatalk 2
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Thanks. Looks to have worked flawlessly.
Works great! Thanks!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Works great. As a thank you I used my play credit from the NP Promo to upgrade to SuperSU Pro. hopefully you see that money!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Thank you. Simplest root evar I will also buy SU Pro
Worked perfectly, of course. Thanks as always.
Just saw this today but had already used the other root method here to get it. Either way, thanks for all the hard work you do on everything
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Is this assured to work with both LRX21M and LRX21V?
Worked perfectly, and now StickMount is working too. Just played a video off USB in XBMC.
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Pardon my ignorance, but what does this do exactly? ...aside from the obvious "gives you root"...I mean how, what does it do to the system?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Click to expand...
Click to collapse
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Zip attachment
volwrath said:
Thank you. Simplest root evar I will also buy SU Pro
Click to expand...
Click to collapse
Do you just download to phone or PC and put the extraction on the Nexus Player to gain root?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Cant find it in the settings anywhere.
Click to expand...
Click to collapse
Are you referring to the launcher settings or SuperSU settings there should be an option in SuperSU settings to set the SuperSU icon to invisible.
I just happened to check my system today and had the OTA update from LRX21M to LRX21V waiting. I tried installing it but Recovery stopped halfway through the install with an Error. I got back into Android with a power-cycle, so things are fine, but it's still on 21M.
I'm guessing this was due to having rooted the device. Is there a proper way to remove SuperSU to allow for a system update? I see there are 3 different options for cleaning up; does it particularly matter which one I choose? I could just pick one and try it but I'm kind of curious what the differences are between the options. Anybody know?
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
xBIGREDDx said:
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
Click to expand...
Click to collapse
probably a full unroot and flashing the stock boot.img would fully unroot, I wonder when LRX22C (5.0.1) will hit the nexus player
The root is fundamental in all devices for many things, and thanks to Chainfire and others independent developers we can consider Android a semi-open platform. (semi-open because not all is open source)
We don't want Android like the Apple walled garden, but we are not even against the sale of the software, we just want a common garden in which the user can choose and is not obliged.
For example with the root, it was easier to start this project:
Nexus Player with a Full Version of Android Lollipop https://plus.google.com/103019026671039069038/posts/V5XaLxK3vN8
This is just the base rom with all hardware components working, on this base that is very usable, i want add many other options. like external usb webcam and mic, improving the audio part that have fixed volume and many other things useful for the use in TV.
Nexus Player is not just Android TV, but is the first Nexus device with an intel cpu. Is a milestone in the evolution of Android.
This is just the start and I am very open to sharing and collaboration on this project.
Thanks Chainfire for the root and for your "How-To SU" guidelines.
Out of interest will rooting prevent OTA updates from installing in the future?
Chainfire said:
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Click to expand...
Click to collapse
I did this, despite the warning it gave me. Now although I still get permission dialogs etc, I can not run the main program to delete apps etc from SU access. Is there anyway to go back to the main screen? I went to the apps sections of the NP and unlike other apps it didnt have an open command.
To get it back do I need to uninstall and then re-CFroot?
Thanks. I should pay better attention to dialog boxes but its not a huge deal.
So, I'm new to rooting and this is my first Nexus device.
I'm loving it and all the options but now I'm getting a notification to update.
I see all the forums about hooking it up to a computer and using commands to do it all and then rerooting.
I was looking for an easier way.
I bought a Nexus 5 to play with because I liked this one so much and when OTAs came up, it would let me download them and reboot into CWM recovery and ask if I want to flash the ZIP.
This one just boots into TWRP (No CWM for 5x) and does nothing.
I found the update as a zip here:
<https://gist.github.com/jduck/744a6c8a9042e9c792b7>
My question is: can I just download it and use TWRP to flash it or is the sequence of commands on a computer the only way to do it?
Thank you in advance for your help and I apologize for my ignorance.
Gotta start somewhere though, right?
Hi !
I personnaly use NRT from Wugfresh for my Nexus 5x and my Nexus 7 2013, both rooted.
In "model type", select Nexus 5x and your build.
In "Restore/upgrade/downgrade", select "device is on/normal", then click "Flash stock+ unroot".
Select the build you want to install, it can dl and extract it for you, and select "No Wipe Mode" in order to keep your data and apps. (don't try to put your ota file here)
Go through the steps, and in the end, hit "Root" to root again.
I know there are others methods to apply just the OTA with command lines, but I never did it cause I never took the time to learn. I should do it, maybe it's faster with command lines.
Anyway this works, even if it takes a little time, and it is kind of automatic. But I strongly recommend you try both method to find what suits you most. Or wait for someone else to reply so you'll have more points of view !
Have fun with your N5x !
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
erichjelm said:
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
Click to expand...
Click to collapse
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Darke5tShad0w said:
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Click to expand...
Click to collapse
It's not working.
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
erichjelm said:
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
Click to expand...
Click to collapse
Are you using flashfire v0.28?
Xposed modifies the system so while you maybe able to get the ota it can prevent you from installing them even with flashfire.
Go to the flashfire thread and see if this is a problem with the app or because or xposed (most likely answer).
Otherwise find the ota threads and see if you can flash it through recovery (not the N version)
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
erichjelm said:
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
Click to expand...
Click to collapse
Thats at the end of my ability to help you with this particular problem, I have only owned a Nexus for 2 months and they are completely diff to Samsung plus I run pure nexus rom, you may just have to use a computer.
And I really appreciate it.
I'll just use a computer and do it.
Don't want to risk trying to flash the zip and bricking but I'm still curious.
Just not curious enough.
Haha.
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
erichjelm said:
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
Click to expand...
Click to collapse
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Greedybro said:
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Click to expand...
Click to collapse
This one didn't unroot. Just uninstalled Xposed. Kept all my data and stuff. Apps stayed signed in even. I was afraid because I heard "factory reset" in yours. Or something to that nature. The only thing I'm having problems with now is Tapatalk told me to check my adblock settings and won't load anything. I'll have to look up what's wrong with it. Other than that, it's doing all right.
You are right and wrong, it unroots but reroots in the process. Same I did when I used nrt. And as i didn't wipe data, apps stayed sign in as Well.
But i tried flashfire on my nexus 7 and I it is way more useful and faster than nrt. I am adopting it !
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.
rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good:
Anyone running Android Q beta 2 ? Can you make a comparison to Pie in terms of speed or apps that crash or hang? TIA
I have no apps crashing and no apps unable to start. Performance and battery are identical to Pie.
The Android Q is definitely a daily driver for me.
EDIT: The only single issue I have is that double-tap or lift to wake are not working.
Guys how to root? Android Q?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Will this work on beta 2 ??
spleenandcigars said:
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Click to expand...
Click to collapse
not work on Beta 2, bro
How best to backout of the AndroidQ beta2?
Installed but Android Auto is playing up so want to go back to v8
Can't mount system partition R/W on Marlin using TWRP 3.2.3-1 once updated to AQB2 (although I did a dirty update by removing the -w erase flag from the bat file before executing.) Guess I'll try nuking everything and rebuilding from scratch to see if the partitions will mount R/W to install Magisk...
Is anyone able to set his own mp3 ringtone on this?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
George_Bushels said:
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
Click to expand...
Click to collapse
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Homeboy76 said:
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Click to expand...
Click to collapse
Yes.
sonpro10x said:
not work on Beta 2, bro
Click to expand...
Click to collapse
As you can see in this screenshot, it's working just fine. You have to install the latest Magisk canary build. TWRP won't work to do some backups, but you can flash it fine.
Been running Q2 for a few days and is a great daily driver. As soon as Nova paid was installed I have no complaints
and battery life has been excellent. Coming from the Essential phone rooted this has been a pleasant surprise. For 180.00 new
unlocked on Sprint this is a good deal. I also prefer the 16x9 screen and camera.
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
tufyuma said:
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
Click to expand...
Click to collapse
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
bonfire62 said:
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
Click to expand...
Click to collapse
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
tufyuma said:
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
Click to expand...
Click to collapse
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
bonfire62 said:
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
Click to expand...
Click to collapse
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
tufyuma said:
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
Click to expand...
Click to collapse
After clean flash, still having the same issue with the downloads. Going to Solidexplorer shows that the sdcard partition never created a Download folder. Chrome also is completely not working now, so definitely rolling back until it's resolved.