Develop Bugs

[Q] Sandvold freezing at boot

I am using Sandvold's ROM but, starting from some days ago, I encountered a big problem: during startup, my Desire freezes and cannot terminate the boot sequence. Even a nandroid restore is not able to fix it: I have to factory reset the device and, after that, restore works. I haven't changed anything, I don't know what could cause this problem, which is very annoying.
I use the latest version, 0.18.2.1.
What could I do?

I'm using the same version of the ROM and for a while now it has been randomly freezing up and I have to physically remove the battery to be able to restart it, after which it resets the date back to January 1980.
Today it froze up and it is also stuck in a boot loop. Tried wiping the dalvik cache and that didn't work so I'll do the factory reset like you suggest. I don't really want to have to switch back to a GB ROM though as I really like ICS.

Same problem here, the problem started when I rebooted today. Running sandvold 0.18.1.
After some digging I could identify a rough source of the problem, but I'm not Android guru, so it will take somebody more experienced than me to figure this out. Essentially, what happens, is that the system_server goes into a loop and keeps on crashing and getting restarted. I've attached the logcat for the gurus.
I'll try reinstalling and possibly wiping to see if that helps.

Just a quick followup, I had to do a full wipe to get back to working order. Attached is a comparison logcat. I don't really understand how Android boots, so I would kindly ask the more knowledgeable devs to have a quick look. Thanks!

After setting the phone up and rebooting, the problem is back again. Seems like there is a time/date-related bomb in sandvold 0.18.

The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Actually I didn't try to install anything from .apk so it can be related to the installation process itself.
Also the same problem has 0.17.1.1 (I don't сheck all versions, just the last ones of majors).
---------- Post added at 09:47 AM ---------- Previous post was at 09:20 AM ----------
0.16.1 - the same problem.
Steps to reproduce:
1. Wipe and install ICS
2. Add google account (at that point the phone still survives a reboot nicely)
3. Install any soft from Play
4. Reboot and enjoy the bootloop
Add: update of an existing soft from Play still causes a bootloop.

dietwice said:
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Click to expand...
Click to collapse
Someone with posting privileges should report this problem in the developer's forum...

roberto.zanasi said:
Someone with posting privileges should report this problem in the developer's forum...
Click to expand...
Click to collapse
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.

dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Click to expand...
Click to collapse
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.

roberto.zanasi said:
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
Click to expand...
Click to collapse
I also tried to do this via Terminal, and my "su" is ok.
But it doesn't work.
It looks like commands are being executed successfully, but it in fact they aren't.

Same problem for me...I'll try to fix it following your help!!! I let you know!!
It work, but I'm not able to "install" the edit Play Store downloaded!!! Reboot work, but no Play Store present among my applications!!!
I find com.process.vending in my application list, but it's a grey icon whit the small sd symbol!
I'll try again to uninstall it!

I have the same problem but, when I tried to use the dietwice's method, I found only the Vending.apk on /system/app folder. So I removed it, replaced with the Vending.apk file downloaded and I continued to follow the method and then I rebooted the phone.
The boot loop is present also after this, so I'd like to know if the fact that I didn't found com.android.vending and com.android.vending.updater is a signal that something was wrong even before applying the dietwice's method.
Someone can answer to my question, please?

I have the same problem as freakymonkey. Any Ideas?

gartenriese said:
I have the same problem as freakymonkey. Any Ideas?
Click to expand...
Click to collapse
I have flashed the ROM again from ClockworkMod recovery and, first to make the reboot, I used the dietwice's method and everything went OK! :good:
On the first boot something went wrong with synchronization with my gmail account, but after a reboot (without boot loop) everything worked fine.

I restored everything but sd-ext and it (re)booted fine, so it has something to do with that. Maybe some Google Play Store data is still on there? How can I get rid of these?
EDIT: Ok, I found some files, will try to delete them tomorrow.

Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
Click to expand...
Click to collapse

matteo.rek said:
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
Click to expand...
Click to collapse
I have been unable to get the Play Store back on my HTC Desire. I have followed the above steps exactly but no shortcut appears on the applications screen.
I have tried wiping the dalvik cache, even did a fresh install of ICS Sandvold Rom but no luck.
Could it be because of the default a2sd?
Any assistance much appreciated guys

[Q] Kindle Fire 8.4.9 Root?

Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?

I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?

You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!

Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848

jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!

Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "

KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.

you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?

KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.

akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm

I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.

Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.

akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow

stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.

akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.

Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .

The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...

Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!

[Q] Downgrade Issue.

Hello All,
Purchased an Amazon Fire TV from Amazon, it shipped in one day and I have been toying with it for the last few hours. Rooting was easy, as was installing SU, Busybox, Stickmount etc.. However, I am not to the point to where I want to install a custom recovery so I can update to the latest firmware without loosing root. The instructions say I need to downgrade to an earlier firmware in order to do this. My problem is that every time I reboot into recovery it says "Update was not successful" and It boots back to the same version that I started with.
The version I have now is 5.1.1.1.0 fully rooted w/ Busybox. I don't know exactly what I am doing wrong. I have both pushed the update.zip to the AFTV, and I have also put it on a thumb drive. I have tried earlier versions then the one recommended in the guide that I was following. All of this to no avail.
Please help.
Thank you.

Anybody? I was up till little after 3 AM trying to figure this out. Factory reset, re-rooted, nothing seems to work. Has anyone else had this issue?

I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.

roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Just tried the mirror. That ended in the same result. I am going to try re-installing Busybox again to see if that has any change.

roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?

brotherandyslb said:
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
Click to expand...
Click to collapse
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.

nyder said:
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
Click to expand...
Click to collapse
Ok,
Lets start from the top:
Factory Reset
Watch Video
Sign into Amazon Prime
So no to parental controls
Go to developer options and turn it to on so I can use ADB
Connect with ADB
adb install towelroot
go into towelroot and root
adb install supersu
go into supersu and let it update
adb install busybox
go into busybox and install it and let it symlink
adb the command to turn off updates
Then I follow the guide over at aftvnews.com to downgrade
Download the firmware version you wish to install from the software page
Rename the downloaded file to update.zip
Connect to your Fire TV using ADB
(If you don’t know how, follow up to Step 4 Part 2 in our Windows or Mac guide)
Run the command: adb shell
Run the command: su
(If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
Run the command: chmod 777 /cache
Run the command: chmod 777 /cache/recovery
Note: If
you see a message saying “No such file or directory”, then run the following two commands:
mkdir /cache/recovery
chmod 777 /cache/recovery
Run the command: cd /cache/recovery
Run the command: echo --update_package=/cache/update.zip > command
Run the command: exit
Run the command (yes, again): exit
Run the command: adb push update.zip /cache
(This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
At this point your fire TV should restart and begin installing whichever firmware version you selected.
Click to expand...
Click to collapse
At this point the AFTV restarts and proceeds to install the new firmware about 1/4 way thru it gives the error message and then restarts.

How to install Gapps on Fire TV Stick 2 (tank) with Lineage OS already Installed

First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...unt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.

So I haven't ever really looked into putting custom roms on my fire stick before so I had to look up what PlayFire was. I haven't had time to mod mine yet but I'm a little confused as to why PlayFire (not upgraded since 2017) would be needed if the LeanBack launcher is already on the rom, Is it just reinstalling it with all the xposed and HDXposed stuff it comes with?

Could you please post or message me your twrp backup I have tried everything and can not get it working tried many times. When I run the script nothing happens still can't use Google play or login to it. Followed the steps to the tee.

Worked without any issues! thanks!

Thank you very much @theflashfromthecw it work great, but do you have a patch for working mic search ?
---------- Post added at 05:04 PM ---------- Previous post was at 04:43 PM ----------
The device is freezig after 3 minutes with the newest gapps and the linkes Google ACC manager. Any solutions ?

Try to install xposed-v87-sdk22-arm.zip with Xinstall and Downgrade option enabled before or adb install -d com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk to downgrade if PlayStore update it afterward.

Is this still working? I have tried to get this working on FTV Tank running Lineage, but no luck with sign in..
Thanks!
update: I was able to get it working, I needed to enable developer options, and then root access because the script was not completing (needed for making changes to /system).
Thanks again for putting this together!

theflashfromthecw said:
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...nt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
Click to expand...
Click to collapse
Hi.... Will this method work on pre-rooted stock image ROM?

Unable to sign-in
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.

Hi guys, nice work! Will it work on a 1st generation FireTV (box, not stick)?

NihaalMoosa said:
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Click to expand...
Click to collapse
You must run
sh /sdcard/PlayFire/LazyNoTouch.sh

no luck
Hi
I am not able to run the script, as I have created a folder called "sdcard" on the root of the internal storage and placed the PlayFire folder there. Furthermore, I used the "sh /sdcard/PlayFire/LazyNoTouch.sh" in ADB Shell, but no luck. Do we need to root Lineage OS before we use the script? If it is, can someone kindly show me a guide, how to root, as I have never done it before.

Flash supersu
https://redirect.viglink.com/?key=e...2-1-t4016981/amp/&ref=https://www.google.com/
In twrp
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"

0815hoffi said:
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
Click to expand...
Click to collapse
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).

any advice on how to properly activate recommendations on leanback
everything else works

lars1384 said:
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
Click to expand...
Click to collapse
would this work with the latest lineage os..?

For me it has not works with the latest.
With
lineage-12.1-20200221-UNOFFICIAL-tank.zip
It has worked.
I Think MicroG support in latest is the Problem maybe.

Cant seem to download tvstock version for the gapps you mentioned. As soon as I select platform and android version.. the tvstock button gets disabled
seems like tvstock is available from android 6.0 onwards for arm platform.
Please help or point me to a compatible gapps zip

Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated

Mhtkmr25 said:
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Click to expand...
Click to collapse
Me too. Seems like opengapps doesn't have a mirror for that one anymore. I tried everything I could think of to search for it too, I even tried to build it from source and failed. But I kept reading every post I could and the best I could come up was finding this link:
https://www.androidfilehost.com/?fid=8889791610682906163
from this post from @diegocr, who is the OP of this build of LOS 12.1 for tank:
https://forum.xda-developers.com/t/rom-unlocked-tank-lineageos-12-1.3961110/post-83220635
It works! Didn't have to mess with any scripts because I couldn't actually find the gapps .zip I needed for those anyway. It's already modified. I just had to reboot into TWRP and flash it.
I'm not sure what the actual tvstock would have had that this doesn't. It does seem stripped down, but that was what I was hoping for when I opened up the thing to short out CLK.

Question Remove baked-in YouTube app

I recently upgraded to the latest Android 12 for my OnePlus 9 Pro. It's working fairly well. I (hopefully) fixed all the tedious issues with root access and SafetyNet. Now there's only one problem the new ROM is causing me: the baked in version of YouTube is newer than the version of YouTube that YouTube Vanced would otherwise install.
I can't just use "uninstall updates" because the version baked in to the ROM is STILL newer than the Vanced version.- I also can't easily just kill it from /system/product/app/YouTube because System has that weird write protection thing on it. It also won't let me just disable it and then install Vanced
Is there any way I could get the Vanced app going? Is there a way to remove the baked-in YouTube app and just install Vanced?

Use adb to uninstall Google's YouTube and install the YouTube vanced app.

If you really want to modify system partition, you can remount it in read/write mode:
Something like this: mount -o rw,remount /system
You can also try disabling the package from command line:
pm disable <package name>

I used debloat app from fdroid it's based off the module

I use the debloat module by itself, just install and run "debloat" from a root terminal, then choose the apps you want to remove.
vponomarev said:
If you really want to modify system partition, you can remount it in read/write mode:
Something like this: mount -o rw,remount /system
Click to expand...
Click to collapse
It's been impossible to remount /system read-write since at least OOS11 due to the dynamic partitions. If you're aware of a way to do this on OOS12, I'd be interested to hear specifics, but a simple mount command won't work on a stock device anymore.

Instal Titanium Backup and freeze the app. Had the same issue as you, now no issue after freezing it.

raghu102 said:
Instal Titanium Backup and freeze the app. Had the same issue as you, now no issue after freezing it.
Click to expand...
Click to collapse
I did this as well with TB!

Hi guys,
The easiest way for me was to downgrade to the latest official Youtube .apk version supported by Vanced (in my case 16.29.39; latest version is shown next to the install button in the Vanced manager). Once you know the correct .apk version, just google it with apkmirror for example. Save it on your desktop; connect your phone; open power shell and downgrade via adb:
adb install -r -d XXXXXXX.apk
Than you can use Vanced Manager to install YouTube Vanced.
After that, I used TeMeFi kickass tool to detach YouTube from the Play Store.
Did the same procedure for YT Music. Rock'n Roll!

@OP
Post above looks the best way to me. Detaching YT from play store would allow you to uninstall it and install Vanced version.