Develop Bugs

What to do with my new useless phone

Hi All,
I just bought a phone for my dad in China, since thats where I live and they are cheap here. I ended up choosing a HTC Desire VC (t328d) which are little known outside China and India.
The point is that I can't do anything with it now. I'm taking it back for him in 2 months and using it in the meantime but it does not have any google stuff on it which makes it a bit like a shoe without a sole. I'm not new to this and have messed around with phones before. I have rooted it and unlocked the bootloader. I've tried putting Google Apps on it loads of different ways and nothing works. I've tried putting it on by flashing it with CWM; installing the apk files individually; and copying the files over to system/apps folder (and changing permissions). I've tried several different downloads and they all fail with a parsing error. Anyway the point is it has failed and I've almost given up. There are no custom roms for it outside China so I could put a Chinese one on and try it all again, but Chinese people don't use google much so google stuff is not included in the roms.
Please can anyone offer advice on what to do with an android phone without google on it? are there any apps that offer similar stuff? where can i get apps from without google play store etc? Sorry for all the questions, I'm just annoyed that the new phone is suddenly pretty useless!
Thanks

Throw it(just kidding).
Exchange....:thumbup:

sanjaykumar.sanjay69 said:
Throw it(just kidding).
Exchange....:thumbup:
Click to expand...
Click to collapse
Not easy since its been rooted.

Gapps
rbnfrance said:
Not easy since its been rooted.
Click to expand...
Click to collapse
find gapps on rom manger,flash them,
if does not work, then pm me, i will tell you another store names.

Pritesh.mohan said:
find gapps on rom manger,flash them,
if does not work, then pm me, i will tell you another store names.
Click to expand...
Click to collapse
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
http://pan.baidu.com/share/link?shareid=135061&uk=1493554205
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?

sixpenny said:
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?
Click to expand...
Click to collapse
Yes, its so annoying. This phone is just sitting at the bottom of my drawer now. I have not tried using rom manager, but I'll give it another go when I can bare it.

sixpenny said:
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
http://pan.baidu.com/share/link?shareid=135061&uk=1493554205
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?
Click to expand...
Click to collapse
I also have the TCL P600. I rooted it already and now have it including full gapps. I wait for a multilanguage version now but anyhow it's quite nice now. You can root it like every other MTK6589 phone. Reset button is simply made by holding down power button for more than 5 seconds.
I like the phone since it is rooted and has GAPPS. After rooting just use JB GAPP zip and flash it in CWM. Works great from then on.
Here is the JB gapps zip for flashing with CWM: https://www.dropbox.com/s/zlf4rlbd2rav1nm/gapps-jb-20130301-signed.zip

weimerd said:
I also have the TCL P600. I rooted it already and now have it including full gapps. I wait for a multilanguage version now but anyhow it's quite nice now. You can root it like every other MTK6589 phone. Reset button is simply made by holding down power button for more than 5 seconds.
I like the phone since it is rooted and has GAPPS. After rooting just use JB GAPP zip and flash it in CWM. Works great from then on.
Here is the JB gapps zip for flashing with CWM: https://www.dropbox.com/s/zlf4rlbd2rav1nm/gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
that mtk6589 was the signalword for me now.
i have already rooted the device and now i am downloading the gapps file of yours. THX for the upload weimerd.
to install with cwm (which is a new word to me) and also i have never rooted a device really (except with odin)
how to install this gapps on the tcl600 ? dual sim will work after as well right?

put the downloaded zip on SD-card.
Power-off the phone.
Power on again while holding power and volume"+" button.
You will boot up into the cwm if you got root on the phone on right way.
- optional: I suggest to make a factory reset now from the menu before installing gapps. But it's not necessary.
Choose "Install zip from sdcard" (choose with power-button, up and down with volume buttons in menu) and install the gapps zip you downloaded.
Reboot the phone and see the gapps
DualSim works perfectly. This is not connected to gapps etc. So it's just that you added all google applications to the phone so you can use your google account, use wheather and news etc.
To really root the phone see here:
TCL P600 root package: http://www.4shared.com/zip/3HRtqraE/TCL_P600_Root.html
HowTo Root TCL P600:
- Extract the file
- Start the flash tool in extracted folder
- Make sure under options it is choosen “with battery”
- In FlashTool load scatter file contained in folder
- Click checkboxes of BOOTIMG and RECOVERY
- Doubleclick on BOOTIMG and refer to TCL-P600_130417__boot_patched_130508-162244.img
- Doubleclick on RECOVERY and refer to TCL-P600_130417__recovery_130508-162244.img
- Switch off mobile and unplug it from usb
- Click “download” in flash tool
- Plug in usb in phone
- If you get a green circle from flash tool saying OK you’re ready with root shell
- Unplug phone and reboot into CWM
- Start Droidtools and plugin usb to phone again
- Install superuser of your choice into phone.
- Ready – you have full root to phone.
If you experience any problems please check if you used the right drivers. Please check drivers attached in folders. Only use them.
I'm not responsible for your phone. If you brick it you have a bricked phone Nevertheless: This worked fine for me and a lot of others.

weimerd said:
by weimerd
Click to expand...
Click to collapse
Hi Weimerd,
i have followed your steps, but some things seem not to be so clear to me. I really want this to work and i see i am close to the final solution, THANKS to your help here.
here is what i have done so far.
1. the device was rooted, i had SU installed (with the usual mt6589_rooter) and booted in CWM, the installation of the zip file from sd started, but was aborted. tried it a couple of times, but result was the same
2. so i decided the facotry reset
to follow your rooting instruction in order to make the rest of the steps happening.
1. downloaded and extraced your file.
2. my phone is connected, i start the flash tool and to as per your instructions
{
"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"
}
(see picture 1.jpg)
3. when i say download i get the message that there might be some issues with the booting (see picture 2)
4. so i am thinking maybe all is ok, but the drivers are the problem, i checked the device manager and tried to update the driver (which windows seven said all drivers are up to date) see picture 3 and 4
-
tried the same thing again, switched off my phone before i press download, unplugged it, and then pressed download and re-attached the phone in the switched off mode, drivers are trying to install, this time it is unseccessful, but also here i cant install any driver.
any idea what i am possibly doing wrong here ??

sixpenny said:
Hi Weimerd,
i have followed your steps, but some things seem not to be so clear to me. I really want this to work and i see i am close to the final solution, THANKS to your help here.
here is what i have done so far.
1. the device was rooted, i had SU installed (with the usual mt6589_rooter) and booted in CWM, the installation of the zip file from sd started, but was aborted. tried it a couple of times, but result was the same
2. so i decided the facotry reset
to follow your rooting instruction in order to make the rest of the steps happening.
1. downloaded and extraced your file.
2. my phone is connected, i start the flash tool and to as per your instructions View attachment 1985002(see picture 1.jpg)
3. when i say download i get the message that there might be some issues with the booting View attachment 1985005(see picture 2)
4. so i am thinking maybe all is ok, but the drivers are the problem, i checked the device manager and tried to update the driver (which windows seven said all drivers are up to date) see picture 3 and 4 View attachment 1985006View attachment 1985007
-
tried the same thing again, switched off my phone before i press download, unplugged it, and then pressed download and re-attached the phone in the switched off mode, drivers are trying to install, this time it is unseccessful, but also here i cant install any driver.
any idea what i am possibly doing wrong here ??
Click to expand...
Click to collapse
First of all make sure you switched on USB debugging (in phone settings). Then uninstall any existing driver which may be there. Install only the ones in package.
With the mentioned drivers all should work.
Then make sure you follow the points make sure your phone is not connected to usb and is switched off. Then press "download"-Button and plugin the phone.
At that point normally the phone is beeing recognized by windows the first time asking for a driver. Look into device manager if it is so. Uninstall any existing other driver there for your phone and clean install only the driver in the package.
I see in device manager screenshot one unknown device. Please also check this.
I only have Windows8 here. Don't know if it's same with Win7 but should be. What error is showing when trying to install the driver?
By the way: No problem with the booting issue message of flashtool, you can ignore this.
here is gapps for JB uploaded by me to make sure nothing goes wrong: http://www.4shared.com/zip/apWjF47r/gapps_JellyBean.html

weimerd said:
First of all make sure you switched on USB debugging (in phone settings). Then uninstall any existing driver which may be there. Install only the ones in package.
With the mentioned drivers all should work.
Then make sure you follow the points make sure your phone is not connected to usb and is switched off. Then press "download"-Button and plugin the phone.
At that point normally the phone is beeing recognized by windows the first time asking for a driver. Look into device manager if it is so. Uninstall any existing other driver there for your phone and clean install only the driver in the package.
I see in device manager screenshot one unknown device. Please also check this.
I only have Windows8 here. Don't know if it's same with Win7 but should be. What error is showing when trying to install the driver?
By the way: No problem with the booting issue message of flashtool, you can ignore this.
here is gapps for JB uploaded by me to make sure nothing goes wrong: http://www.4shared.com/zip/apWjF47r/gapps_JellyBean.html
Click to expand...
Click to collapse
hi,
first of all: THANK YOU for your great help and support, i really appreciate your time you have been trying to help me. and actually helped me.
finally managed all drivers and everything as you have described. installed superuser as well and rebooted the device.
i see all google apps. google search is stopping, but i dont care about that.
but what troubles me is a bigger isse : I CANT TYPE...
unfortunately android keyboard has stopped...
now that is an interessting one. any experience with this?
i saw on droid tools i can remove china ? maybe ?

sixpenny said:
hi,
first of all: THANK YOU for your great help and support, i really appreciate your time you have been trying to help me. and actually helped me.
finally managed all drivers and everything as you have described. installed superuser as well and rebooted the device.
i see all google apps. google search is stopping, but i dont care about that.
but what troubles me is a bigger isse : I CANT TYPE...
unfortunately android keyboard has stopped...
now that is an interessting one. any experience with this?
i saw on droid tools i can remove china ? maybe ?
Click to expand...
Click to collapse
Never had that issue. Maybe it is because I upgraded the firmware already with tcl updater before. I suggest to do so, you can re-root it and put gapps on it now
I suggest installing another keyboard. Download one with computer, put apk on sd-card and install it through file manager. Should work

Yeah Weimerd.
done that now, thanks again. but google play is stopping after signing in.
maybe i will do the tcl update after a factory reset and give it once more a try.
if i do facotry reset all will go back as it used to be?

factory reset will most probably not delete root. So just do factory reset and delete dalvik cache (under advanced). Then install gapps zip again. Then reboot. Should work then

I checked this once more.
1. First of all I updated the phone with TCL updater to the latest firmware.
2. I rooted it as I described before.
3. I deleted lots of China Apps and also under system/media bootup sounds and some - for me - other stuff not needed in order to get more space on system partition.
4. I installed GAPPS through CWM. I did it with this one: http://goo.im/gapps/gapps-jb-20121011-signed.zip
After rebooting I also got the crash of google search. I ignored it and added my google account. After opening playstore then I got update for google search. After updating there is no crashing anymore.
All other gapps are working quite well. I tested GPS for the TCL P600 and was really suprised it works quite fast and accurate.
The only thing: There is no A-GPS setting. Let's say: There is no GPS setting at all. You can only switch GPS on and off. Settings are not included. Maybe this will be unlocked with a modded rom.
I'm now testing all functions in detail but up to now it works really great.
Hope you got it also up to this point. After all steps this phone is really perfect.

yes, but i am still struggeling to remove the root, i cleared the dalvik chache, reinstalled everything.
i cant access my google account nor the playstore.
the tcl updater isnt available. or can you show me the icon ?
i think best would be to remove the root and factory reset then and then go ahead and do it all once more.

rbnfrance said:
Hi All,
I just bought a phone for my dad in China, since thats where I live and they are cheap here. I ended up choosing a HTC Desire VC (t328d) which are little known outside China and India.
The point is that I can't do anything with it now. I'm taking it back for him in 2 months and using it in the meantime but it does not have any google stuff on it which makes it a bit like a shoe without a sole. I'm not new to this and have messed around with phones before. I have rooted it and unlocked the bootloader. I've tried putting Google Apps on it loads of different ways and nothing works. I've tried putting it on by flashing it with CWM; installing the apk files individually; and copying the files over to system/apps folder (and changing permissions). I've tried several different downloads and they all fail with a parsing error. Anyway the point is it has failed and I've almost given up. There are no custom roms for it outside China so I could put a Chinese one on and try it all again, but Chinese people don't use google much so google stuff is not included in the roms.
Please can anyone offer advice on what to do with an android phone without google on it? are there any apps that offer similar stuff? where can i get apps from without google play store etc? Sorry for all the questions, I'm just annoyed that the new phone is suddenly pretty useless!
Thanks
Click to expand...
Click to collapse
just try to make your own rom with those existing china roms and roms with google apps.. it is simple, follow this thread. http://forum.xda-developers.com/showthread.php?t=2113479

You may download the TCL updater from here: http://www.tclmobile.com.cn/productsview.php?catid=36&id=462
This is a windows tool for updating your tcl P600. It makes no difference if you decide for P600 or P606, the same firmware will be loaded. The tool will to all flashing, so it's very simple. Just download, install and run the tool, follow the steps and you get a flahed phone. Don't forget to save your data as all will be lost after flashing.
Also root will be gone after flashing with that tool.
---------- Post added at 07:05 AM ---------- Previous post was at 07:04 AM ----------
Aingaran said:
just try to make your own rom with those existing china roms and roms with google apps.. it is simple, follow this thread. http://forum.xda-developers.com/showthread.php?t=2113479
Click to expand...
Click to collapse
It's not as simple as you say. The main problem is that there is no stock rom available as basis. But nevertheless I'll take a shorter look to that

weimerd said:
You may download the TCL updater from here: http://www.tclmobile.com.cn/productsview.php?catid=36&id=462
Click to expand...
Click to collapse
Hi weimerd and all others who are reading this.
1. I have downloaded and installed the tcl updater, it updated the software, the root was gone.
2. then i updated all software with the tcl updater on the phone. software available was still 4.1.2
3. rooted the phone
4. installed the gapps
(there i noticed that its installing 4.2.2 apps)
keyboard is crashing, google play store crashing. same problem as before as i can see it
i will reset it once more and then hope for a final try when i am in the mood again. i sort loosing it over this tclp600, but its such a nice phone.
i like everything about it so far.
just this inability to use it with google standard apps

few questions before I root the KFHD8932GB

Hello, I've just bought my gf the 8.9 32gb version and she's not keen on the overlay UI and the lack of stuff on amazons market so she's asked me to root it.
1) If I root it, can I get it back to default state without showing that its previously been rooted? (any insuring later)
2) If you install the Play store, what device does the store think you have in order to install apps/games etc?
3) its just updated itself, am I right in thinking it cannot be rooted from this latest software? is downgrading easy?
4) Will we lose the things that are already on it? (Full wipe)
Thanks

Andyokane said:
Hello, I've just bought my gf the 8.9 32gb version and she's not keen on the overlay UI and the lack of stuff on amazons market so she's asked me to root it.
1) If I root it, can I get it back to default state without showing that its previously been rooted? (any insuring later)
2) If you install the Play store, what device does the store think you have in order to install apps/games etc?
3) its just updated itself, am I right in thinking it cannot be rooted from this latest software? is downgrading easy?
4) Will we lose the things that are already on it? (Full wipe)
Thanks
Click to expand...
Click to collapse
There's been no change to update methods, the bin4ry method, option 2 has always worked. If you look @ lizzard30's SteriROM 1.2 thread, you'll end up by-passing the whole rooting process, end up rooted, w/android market & more installed. Just make sure you adb drivers are properly installed: Windows 8 will definitely block installation of unsigned drivers, and Windows 7 a bit too--google search disabling driver signature enforcement for the OS your installing computer uses if it's Windows.
As part of the install process, you'll deregister from amazon. All your programs you've installed will be wiped, so if it ain't part of the of the install package you'd have to reinstall. You can select to wipe your SDCARD, but that isn't necessary. Music and documents should still be there.
If you're going Gi Joe this and root, install busybox, then android market, that's kool. You'll need bin4rys root method to root, get busybox installer from 1mobile market website, enable installation of unknown programs. You want the installer for after rooting--install it, open it, install busybox. Then you'll need kindle fire first aid. Don't use KFFA to root or install busybox. Install busybox, it's required to use KFFA. Use KFFA to install market first, then market apps if you'd like.
Good luck! Oh, if you don't deregister and use SteriROM and go medieval instead, visit application manager and wipe data for kindle reader, amazon vod, and silk. Maybe a few other amazon apps ... otherwise not all your stuff will show up.

I've completed every step and everything went perfect but now i've finished and rebooted im not stuck on the first KindleFire orange logo and it goes no further

Andyokane said:
I've completed every step and everything went perfect but now i've finished and rebooted im not stuck on the first KindleFire orange logo and it goes no further
Click to expand...
Click to collapse
SteriROM? Bin4ry? If you need help, pm me, I can send you my email to google chat or something to figure it out. Lemme know

4iiiidnerd said:
SteriROM?
Click to expand...
Click to collapse
??>>

ive tried the whole process now about 5 times, and it boot loops when I try install Twrp recovery/img any ideas??

Andyokane said:
ive tried the whole process now about 5 times, and it boot loops when I try install Twrp recovery/img any ideas??
Click to expand...
Click to collapse
so, you never get past "Fix the red screen"? and are unable to install TWRP. were there any errors when you installed the ADB drivers? error message do not mean everything is working good
It'd be nice if someone else had input on the TWRP install ... which I haven't done yet.
you might want to post on the steriROM thread (check for sim circumstances)
---
I looked at Hashcode's thread about twrp installation:
http://forum.xda-developers.com/showthread.php?t=2128175
notice step 4.5--your Kindle fire would have 8.3.1 on it, you will likely need to download the file and install in fastboot like Hashcode suggests

4iiiidnerd said:
so, you never get past "Fix the red screen"? and are unable to install TWRP. were there any errors when you installed the ADB drivers? error message do not mean everything is working good
It'd be nice if someone else had input on the TWRP install ... which I haven't done yet.
you might want to post on the steriROM thread (check for sim circumstances)
---
I looked at Hashcode's thread about twrp installation:
http://forum.xda-developers.com/showthread.php?t=2128175
notice step 4.5--your Kindle fire would have 8.3.1 on it, you will likely need to download the file and install in fastboot like Hashcode suggests
Click to expand...
Click to collapse
Didnt seem to get any errors. Going to try the StariRom method today and see how that does thanks.

State Of Xposed on Shield

So this thread will be about the general state of Xposed on our shield TV's. If you have any questions or need help related to Xposed on the Shield TV, feel free to ask.
First Things First, Xposed does work on the 2.1 firmware. (If someone on the Vulcan preview could chime in about 3.0 that would be great.)
Steps to install Xposed on 2.1 (Assuming you already have a working recovery)
1) Download xposed-vXX-sdk22-arm64.zip and XposedInstaller_3.0_alpha4.apk from this thread.
either adb push it to /sdcard/ or use a thumb drive etc etc.
2) ADB reboot recovery
3) Preform a full backup IMPORTANT (I did 2 backups, one to internal storage, and another to external usb, better safe than sorry!)
4) Flash xposed-vXX-sdk22-arm64.zip (Wiping cache after is optional)
4) Reboot to system, Booting will take longer than usual, it took about 5 minutes on my 16gb, but could take longer.
5) Install XposedInstaller_3.0_alpha4.apk (ES file explorer works great for this, you can download it from playstore)
6) Open up Xposed installer once installed, select framework, and it should show Xposed framework version 80 is active. If not, repeat steps 1-4, If you're still having problems, ask here. From the installer you can install modules, just make sure to activate them and reboot!​
Steps to install Xposed on 3.0 MM (with a working recovery)
1) Download xposed-vXX-sdk23-arm64.zip and XposedInstaller_3.0_alpha4.apk from this thread.
either adb push it to /sdcard/ or use a thumb drive etc etc.
2) ADB reboot recovery
3) Preform a full backup IMPORTANT (I did 2 backups, one to internal storage, and another to external usb, better safe than sorry!)
4) Flash xposed-vXX-sdk23-arm64.zip (Wiping cache after is optional)
4) Reboot to system, Booting will take longer than usual, it took about 5 minutes on my 16gb, but could take longer.
5) Install XposedInstaller_3.0_alpha4.apk (ES file explorer works great for this, you can download it from playstore)
6) Open up Xposed installer once installed, select framework, and it should show Xposed framework version 80 is active. If not, repeat steps 1-4, If you're still having problems, ask here. From the installer you can install modules, just make sure to activate them and reboot!​
I've only tried 2 modules so far, one works, one doesn't. If You have tried a module and it does or doesn't work, please comment with the version and I'll add it to this list.
WORKING
NoSafeVolumeWarning V1.7 Stable (http://forum.xda-developers.com/xposed/modules/module-nosafevolumewarning-t2718933/)
App Settings (http://repo.xposed.info/module/de.robv.android.xposed.mods.appsettings) (Thanks Andy4Shurr)
Xprivacy http://forum.xda-developers.com/xposed/modules/xprivacy-ultimate-android-privacy-app-t2320783 (thanks Bradwatson and banderos101)
NOT WORKING
Youtube Adaway V3.1.1 (http://forum.xda-developers.com/xposed/modules/app-t2547316)

Reservado

happydish said:
Reservado
Click to expand...
Click to collapse
Also Reserved, just in case.

Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback

olivier.bossaer said:
Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback
Click to expand...
Click to collapse
Haven't tried it yet, been super busy with school, currently running 3.0 stock (not even rooted). If you try it, let me know if it works! I don't see why it shouldn't

olivier.bossaer said:
Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback
Click to expand...
Click to collapse
Nope, did not work for me
after flashing the zip it keeps booting forever

Arf!
I haven't time to test now.
But seems unfortunate...
Hope there will be a workaround!
Envoyé de mon Nexus 6 en utilisant Tapatalk

I installed Xposed on the 3.0 update. Had no issues. Also installed Xprivacy. Hoping to bypass mlb blackouts with mlb.TV.
I went through the standard process for installing it. Basically the exact steps of the OP but the newest version of the framework.
Sent from my XT1575 using Tapatalk

App Settings module works perfectly.

Xposed and root are working fine for me on 3.0 update, I'll write another guide maybe later today, but the steps are the same, just with the updated zip (SDK 23 for MM).
Brad, is Xprivacy working for you? Any problems?

happydish said:
Xposed and root are working fine for me on 3.0 update, I'll write another guide maybe later today, but the steps are the same, just with the updated zip (SDK 23 for MM).
Brad, is Xprivacy working for you? Any problems?
Click to expand...
Click to collapse
I can also confirm sucess with the sdk23 MM latest version and shield marshmellow
Xprivacy seems to be working well, except ondemand doesnt seem to pop up for any, or at least some, of the storage restrictions..........im not sure if xprivacy has been updated for marshmellow, so im not sure if storage restriction is working, i will pay attention next time i install an app from scratch........

Andy4Shurr said:
App Settings module works perfectly.
Click to expand...
Click to collapse
Andy can u help me.I have installed xposed and it says it is active.Than i instaled App Settings and when i try to change Dpi or other app setting nothing happens.(i have stock 6.0 ...3.0 rooted)

Installed root and xposed on 3.0 no problems, just needed to use pen stick because adaptive storage. Cannot seem to access the bootloader via hardware method (wait 3 secs then hold power button). I Tried many variations of it to no avail... Also I have to reflash the boot loader every time to access it. If I choose kernel recovery from bootloader it just shows the android with a warning / error.
Using Xposed mod Unbeloved Hosts and Lucky Patcher. Between the two I can filter 99% of all ads.

keep getting a error when tryin to flash with twrp on my nvidia shield tv whats is the corret zip for my device? Thanks all.

K I got Xposed installed MM 3.0 But when I use KODI if I have a stream playing it stops a few mins in, If I stop all of the modules in xposed and restart KODI Starts to work again, no probleems streaming. So it has to be Xposed or one of the modules I was using. Luck Patcher, App settings, Xprivecy, yourtube, MinGaurd (Not sure full name der) , YouTube AdAway.

Just installed the latest version of Xposed following the steps on the guide. I'm on 3.3 update, rooted. No problems so far. Will test some modules and report back.

joelcool69 said:
Just installed the latest version of Xposed following the steps on the guide. I'm on 3.3 update, rooted. No problems so far. Will test some modules and report back.
Click to expand...
Click to collapse
I finally unlocked my bootloader and rooted my Shield after using it for about a year. I use Xposed regularly on my Nexus 6P but wanted to know if anyone has information about Youtube Adaway Module working (or alternative). So far seems like it doesn't work everywhere.
Are there any other modules worth getting on Xposed for Android TV? Perhaps something for Xbox 360 Controllers?
Also would be very interested in Youtube HDR if anyone has a workaround seeing that it's supported officially by Youtube but their Youtube for Android TV app literally hasn't been updated since April so I take it we'll have to wait a few months. Not fun considering my 4K HDR tv has been waiting a year for this.
Thanks in Advance.

copticwalad said:
I finally unlocked my bootloader and rooted my Shield after using it for about a year. I use Xposed regularly on my Nexus 6P but wanted to know if anyone has information about Youtube Adaway Module working (or alternative). So far seems like it doesn't work everywhere.
Are there any other modules worth getting on Xposed for Android TV? Perhaps something for Xbox 360 Controllers?
Also would be very interested in Youtube HDR if anyone has a workaround seeing that it's supported officially by Youtube but their Youtube for Android TV app literally hasn't been updated since April so I take it we'll have to wait a few months. Not fun considering my 4K HDR tv has been waiting a year for this.
Thanks in Advance.
Click to expand...
Click to collapse
Well, Youtube Adaway Module it's working for me. About 1 hr of continuous playback and no one single ad. Xprivacy and Marshmallow SD Fix working too.

Now that Nougat has been out for months and Xposed not working on it, has anyone figured out a way to block Youtube ads? I know arter97 has patched youtube apks but nothing yet for the Shield.

Does Adguard work on Android TV?

Should I update FTV OS on my rooted ftv

I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia

ant17 said:
I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia
Click to expand...
Click to collapse
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
The update to FireOS 5 is mostly recommended for App comparability. More & more apps in the PlayStore & Amazon have lollipop as the starting point.
I did learn to live with the no Home button detection for AppStarter. I still use AppStarter 90% of the time. I just keep AppStarter as the only app in recent. So it has just added a couple of presses to what I was use to with FireStarter. But if the HOME button detection is a huge deal for you. You should stay there.
As for the updates. I have not seen any performance hits. The only major problem might be bugs. But the tier rollout of the update usually takes care of that. I tried the new UI on a couple of FTVS2's & they weren't laggy at all. I usually find the latest FW to be as fast or faster of prior onces. But that might be because I prefer to do clean installs when upgrading FW. Specially on an update as big as the one that just started to rollout. The new update includes more stuff but luckily it comes with options to turn some of that stuff off.
We can also always downgrade PreRooted Rom's. So it's fine to take things for a spin. As long as you have a good install of TRWP. There shouldn't be a problem. Other the user error or power outage.

I wouldn't care about the KODI update, but a message from tv addons says streams are more often using the https: for shows and 16.1 doesn't support that.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.

ant17 said:
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.
Click to expand...
Click to collapse
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Y314K said:
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.
Click to expand...
Click to collapse
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.

ant17 said:
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.
Click to expand...
Click to collapse
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using Apps that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been activated/granted to ES File Explorer.

Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.

ant17 said:
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.
Click to expand...
Click to collapse
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.

Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.

Deleted

ant17 said:
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.
Click to expand...
Click to collapse
The only method is to connect a keyboard to your FTV1 & choose to boot into recovery at startup. You should see the exact version on the lower left hand side.
If your going to be using a USB drive to flash things. You will need a USB hub to have both the USB Keyboard & USB drive hooked up to the device at the same time.
Those guides are the most complete ones. But they are some what old & also each FTV has it's own history of what has been done to it. So make sure you modify accordingly. I thought about making a post with my notes regarding this updating guide but I thought everybody's starting point is probably to different & I don't want to be responsible for bricking any FTV1's.

Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.

evaporic said:
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request
Click to expand...
Click to collapse
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
ant17 said:
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.
Click to expand...
Click to collapse
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton
Click to expand...
Click to collapse
thanks dl'd it.

Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
----------------------------------------------------------------------------------------------------------------------------------------
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse

evaporic said:
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse
Great, glad there is now tested method for this. :highfive:
Can you please be a bit more detail in your steps... Please fill in the blanks below. That way other folks don't have to guess.
My FTV1 started from PreRooted FW v________ & TWRP v___.
Use a Fat32 formatted USB Stick.
Download & add the following files to the USB Stick (Check hash's):
CWM Recovery 6.0.5.1.4a - (md5sum: 67b1a13b7bec645cb9291e80478d4635)
FireTV Boot Menu 1.0 - (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
FireTV 1 (bueller) Prerooted Stock Images [51.1.6.3_516012020] - (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
Connected a USB Keyboard & boot to TWRP recovery.
First wipe __________. (None if you didn't wipe anything first)
Using TWRP flash ____________________.
_________________________________________.
Please provide as much detail as possible. Thanks

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom menu issues

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18

For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.

New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.

Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.

Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.

drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.

Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.

drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.

Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!

drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...

Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!

I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.

drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.

Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.

Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.