Related
I never really use Live Wallpapers on my Evo, but I noticed today that the option is completely gone now. HW 003 with latest stock OTA rooted with unrevoked.
Menu -> Wallpaper from the stock home screen and Launcher Pro Plus are both missing the Live Wallpapers option, and if I try to open a Live Wallpaper from the Market (which installs fine), it tells me my phone does not support Live Wallpapers.
The two things I can think of that I've done lately are installing Launcher Pro Plus and running Fix Permissions from ROM Manager (seeking better battery life). Currently my LiveWallpapers.apk and LiveWallpapersPicker.apk have permissions of 644, but changing them to 777 seems to have no effect (even after a reboot).
I tried several things last night:
uninstalled Launcher Pro
reinstalled busybox
ran fix permissions from Clockwork Recovery
attempted to reinstall LiveWallpapers.apk
I say attempted because the install failed on both LiveWallpapers.apk and LiveWallpapersPicker.apk. I grabbed these from the latest Sprint OTA update.
Now, according to Astro, both apk's are in /system/apps, but there is no uninstall option, just install.
Can anyone lend me a hand? I have a nandroid backup from a few weeks ago, but I don't really want to flash it unless it's absolutely necessary. Thanks in advance.
VaughnOnix said:
I never really use Live Wallpapers on my Evo, but I noticed today that the option is completely gone now. HW 003 with latest stock OTA rooted with unrevoked.
Menu -> Wallpaper from the stock home screen and Launcher Pro Plus are both missing the Live Wallpapers option, and if I try to open a Live Wallpaper from the Market (which installs fine), it tells me my phone does not support Live Wallpapers.
The two things I can think of that I've done lately are installing Launcher Pro Plus and running Fix Permissions from ROM Manager (seeking better battery life). Currently my LiveWallpapers.apk and LiveWallpapersPicker.apk have permissions of 644, but changing them to 777 seems to have no effect (even after a reboot).
I tried several things last night:
uninstalled Launcher Pro
reinstalled busybox
ran fix permissions from Clockwork Recovery
attempted to reinstall LiveWallpapers.apk
I say attempted because the install failed on both LiveWallpapers.apk and LiveWallpapersPicker.apk. I grabbed these from the latest Sprint OTA update.
Now, according to Astro, both apk's are in /system/apps, but there is no uninstall option, just install.
Can anyone lend me a hand? I have a nandroid backup from a few weeks ago, but I don't really want to flash it unless it's absolutely necessary. Thanks in advance.
Click to expand...
Click to collapse
I don't use ROM Manager for anything. It is far too easy and more productive to do things manually. Using Root Explorer or another file manager that lets you alter system files, you can easily maneuver to the /system/app folder, select the live wallpaper .apk, select Mount R/W and set the permissions to however you see fit. Hopefully, you've made a nandroid backup of your device PRIOR to making the changes that have caused you these problems. If not, get in the habit of doing so because if things go wrong or you find that you want to return things back to the way they were prior to the change(s), all you have to do is nandroid restore. Everything would be as it was.
dougjamal said:
I don't use ROM Manager for anything. It is far too easy and more productive to do things manually. Using Root Explorer or another file manager that lets you alter system files, you can easily maneuver to the /system/app folder, select the live wallpaper .apk, select Mount R/W and set the permissions to however you see fit. Hopefully, you've made a nandroid backup of your device PRIOR to making the changes that have caused you these problems. If not, get in the habit of doing so because if things go wrong or you find that you want to return things back to the way they were prior to the change(s), all you have to do is nandroid restore. Everything would be as it was.
Click to expand...
Click to collapse
Thanks for the response. Root Explorer is indeed how I set the apk's permissions to 777 just to test. I'm not in the habit of making nandroid backups unless I'm flashing something.
I'm not trying to blame ROM Manager and/or Launcher Pro, just wracking my brain trying to figure out how I got here. I could have very easily lost Live Wallpapers long before either of those.
Edit Update:
I broke down and flashed to my nandroid backup from sometime before running fix permissions and installing Launcher Pro... still no Live Wallpapers option. Now I'm out of ideas.
VaughnOnix said:
Thanks for the response. Root Explorer is indeed how I set the apk's permissions to 777 just to test. I'm not in the habit of making nandroid backups unless I'm flashing something.
I'm not trying to blame ROM Manager and/or Launcher Pro, just wracking my brain trying to figure out how I got here. I could have very easily lost Live Wallpapers long before either of those.
Edit Update:
I broke down and flashed to my nandroid backup from sometime before running fix permissions and installing Launcher Pro... still no Live Wallpapers option. Now I'm out of ideas.
Click to expand...
Click to collapse
It's been a while since I've used LauncherPro extensively, but and I could be mistaken, but there's a chance that the HTC live wallpaper may be off limits while using LP like many of the HTC widgets are. The reason I say this is because your nandroid restore from long before your fix did not produce any live wallpapers. Do this, if you have the time: go into the applications menu, clear defaults after scrolling down and selecting LauncherPro. Press the home button and then select Sense as your launcher. Now select a live wallpaper and see if it displays. If it does then you know they are off limits to LP.
Just Me, D
via the XDA Premium app
dougjamal said:
It's been a while since I've used LauncherPro extensively, but and I could be mistaken, but there's a chance that the HTC live wallpaper may be off limits while using LP like many of the HTC widgets are. The reason I say this is because your nandroid restore from long before your fix did not produce any live wallpapers. Do this, if you have the time: go into the applications menu, clear defaults after scrolling down and selecting LauncherPro. Press the home button and then select Sense as your launcher. Now select a live wallpaper and see if it displays. If it does then you know they are off limits to LP.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
Well, my nandroid was from before I ever installed Launcher Pro, and I'm testing with more than just the HTC live wallpapers, but clearing defaults and data for Launcher Pro changed nothing.
Hello all. I have been searching the forums and could not find anything to help with my specific problem. I got my KF this past Thursday and rooted it with Breakdroid. The Fire was on 6.2.
Well, today when I tried to change my wallpaper again by doing the whole changing permissions thing with Root explorer, i got a message that my "phone" didn't appear to be rooted so I couldn't access the file. So after searching the internet I learned that an auto update likely unrooted the device. Checked my settings and sure enough, it updated to 6.3.
I still have the Android Market, Root Explorer, Es File explorer and all other apps I downloaded which are working and I would like to keep. But my issue is I can't change the wallpaper to anything, not even to the stock Kindle Fire wallpaper, which I thought would change since it unrooted it. I'm scared to reset it or turn it off for fear it may brick. Is there a way I can re-root it, or is it fine like it is? I'm scared really to do anything with it. Thanks. I am using a MAc, btw and all the re rooting tools seem to only be for Windows.
pretty sure youll be fine to use breakdroid and kindlewater again Im not on mac but It seems to be whats available http://forum.xda-developers.com/showthread.php?t=1511757
Thepooch said:
pretty sure youll be fine to use breakdroid and kindlewater again Im not on mac but It seems to be whats available http://forum.xda-developers.com/showthread.php?t=1511757
Click to expand...
Click to collapse
So I just re-root again as if I've never done it before? Even though I still have Superuser on the device. Or can I just factory reset it?
You need to re-root the device, factory will just erase all your apps and it still won't be rooted.
You are going to have to reroot the kindle if you want to do anything that requires root access. Super user does nothing without root. However if you factory reset you will lose everything and your ability to download Android apps via Google play I recommend rooting and flashing the modaco rom if you want a better stock experience that does not automatically update. Hope it goes well
Sent from my Galaxy Nexus using xda premium
feistygoat10 said:
You need to re-root the device, factory will just erase all your apps and it still won't be rooted.
Click to expand...
Click to collapse
Okay. I know I need to re-root but do I just re-root over what I currently have? I already have the superuser app, ES file explorer and Root explorer. If I just go ahead now and re-root it as it is, do I have to install these apps again or will I just be able to resume my device as it was before the update broke the root? I just don't want to mess it up.
Really if I can just get it back to where the wallpapers change (default Amazon), I'll be content with the way it is. What happened was I changed the wallpaper and set permissions for it not to change as it normally would. Of course, the update came afterwards, and now I can't change the wallpaper at all. I was a little worried something may be wrong with it since I expected the wallpaper to be reset back to the stock Amazon ones that change all the time.
I am not running stock right now though if I remember correctly the kindle fire stock interface does not have a "background" it is just the carousal and the favorites thing. So are you running a launcher that you changed the background of or did you change the screen saver? If it is really bad you should just backup your data if you are worried and reroot it is almost impossible to fully brick I think I have done it like 17 times messing with it though works fine. If you need a windows computer you could probably go to a public library or university library and use their computers.
Sent from my Galaxy Nexus using xda premium
Kheladu said:
I am not running stock right now though if I remember correctly the kindle fire stock interface does not have a "background" it is just the carousal and the favorites thing. So are you running a launcher that you changed the background of or did you change the screen saver? If it is really bad you should just backup your data if you are worried and reroot it is almost impossible to fully brick I think I have done it like 17 times messing with it though works fine. If you need a windows computer you could probably go to a public library or university library and use their computers.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes. I am running a launcher (Go Launcher) and changed the wallpaper using that before the OTA update. You know using the launcher to change the wallpaper gives you the options to leave your wallpaper in place by changing permissions in root explorer because when you wake your Fire the wallpaper becomes one of Amazons. The launcher, Market, and all my apps still work from when I rooted it. I just thought that once the root was broken by the update, that my wallpaper would disappear and the stock Amazon wallpapers would return, but they didn't. I'm still on the same wallpaper and cannot change it at all. That's what was worrying me.
If you don't want to root over what you have then try uninstalling the launcher and reinstalling it or an other launcher. See if it works.
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.
Hi,
i have a fire stick (unrooted) and currently use firestarter.
Is there a way to stop the default KFTV launcher loading at startup without root? I still would like to load it up now and again, but only when needed using firestarter.
I hear the default launcher uses up a lot of ram
Any help appreciated
DEREKTROTTER said:
Hi,
i have a fire stick (unrooted) and currently use firestarter.
Is there a way to stop the default KFTV launcher loading at startup without root? I still would like to load it up now and again, but only when needed using firestarter.
I hear the default launcher uses up a lot of ram
Any help appreciated
Click to expand...
Click to collapse
Settings/ Manage APPS/ FireStarter
Clear data
Clear cache
bula1ca said:
Settings/ Manage APPS/ FireStarter
Clear data
Clear cache
Click to expand...
Click to collapse
ill try it thanks
do you mean KFTVlauncher (clear data / cache) ?
guessing it would need to be done on every startup
Nope, there currently isnt a way without root.
The FTVLauncher is the base for a lot of the other Amazon stuff on the stick which wouldn't work without it.
This is why its very aggressive in how it works.
If I remember clearing data from it will remove a lot of stuff/settings/data from the stick (might be thinking of the Kindle launcher though?)
Freezing the FTVLauncher is the probably the main reason for gaining root, it takes up a far amount of RAM when running!
Your better off rooting, installing Titanium Backup, freezing it, setting FireStarter as 'Home' and unfreezing it when you need it.
Dude360 said:
Nope, there currently isnt a way without root.
The FTVLauncher is the base for a lot of the other Amazon stuff on the stick which wouldn't work without it.
This is why its very aggressive in how it works.
If I remember clearing data from it will remove a lot of stuff/settings/data from the stick (might be thinking of the Kindle launcher though?)
Freezing the FTVLauncher is the probably the main reason for gaining root, it takes up a far amount of RAM when running!
Your better off rooting, installing Titanium Backup, freezing it, setting FireStarter as 'Home' and unfreezing it when you need it.
Click to expand...
Click to collapse
It will not remove any settings.
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.