My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.
I having this problem too, cant set custom launcher.. anyone help us??
The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!
I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.
Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.
With 5.2.7.4 , you need root for this commands!!!
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot
Ahh where were you a couple days ago!
noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk
Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!
The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.
Related
Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.
I just purchased a unit that has TV AddOns Custom Wizzard Edition that was advertised to be rooted with the latest custom rooted firmware installed. The unit shows up as having the latest 4.0 Amazon firmware on it and yet the seller says that it's a custom image and that the unit is indeed rooted. I honestly can't tell, but Super SU won't work on the unit and I'd like to downgrade the firmware to a rootable custom version and remove what he has on it to install my more familiar standard XBMC setup to it and then lock updates.
Can someone point me to a guide for downgrading the firmware or better yet removing the entire setup so that I can configure the unit in the manner to which I am accustomed to? I'd certainly appreciate any help....I honestly do not believe this unit is rooted, but he's swearing that it is and that the latest firmware that I'm seeing on it is a custom rooted firmware. I really need help here in finding out if it really is rooted and would greatly appreciate anyone's advice on downgrading the firmware or removing the setup entirely without losing root if it is in fact rooted. I'm in the dark as to cwm since I've never worked with it....
Thanks in advance for any help anyone can offer!
Use the Fresh Start program in TV Addons to remove all of the Custom Wizard stuff in XBMC.
Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.
nhumber said:
Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.
Click to expand...
Click to collapse
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!
fxbill said:
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!
Click to expand...
Click to collapse
glad you got it all straightened out. you can still adb push your backup files on a clean xbmc install.. so you just sideload xbmc then adb push your backup to the correct location, i forget that exact location at the moment tho.. theres alot of good instructions on the xbmc wiki. http://kodi.wiki/view/Amazon_Fire_TV#Copying_files . the xbmc backup addon also works from what i was reading, i havent personally tried it myself.
Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..
slackbladder said:
Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..
Click to expand...
Click to collapse
Are you installing sloane-5.0.5-rooted_r4.zip from recovery?
It looks like it installed OK but even so if you already have recovery installed you still have a way back in.....so no worry.
That's what I was gonna say, seems ok to me?
If it won't boot Into recovery or won't boot follow this guide here -
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
But if you can access recovery with a keyboard press or via adb just follow the guide on aftvnews but since you have already tried to root don't use the installer just flash the prerooted rom (if needed redownload the zip check the md5 checksums & flash In recovery)
Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just one other thing chaps.... to be able to load rbox's twrp,.... is that only possible via an sd card plugged in and using ramdisk-recovery.cpio.lzma and then switching on firetv?
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?
slackbladder said:
Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?
Click to expand...
Click to collapse
You lost me here but glad you managed to finish the installation.
BTW if your FireTv1 is on OS5 you can rooted with kingroot. You need to provide more info to be able to help you furthermore.
Now youve rooted dont forget to block updates via adb! You need a keyboard to access twrp like I said before, no sd card In the aftv2 doesn't matter, you can still access twrp. Yes you can root the aftv gen 1 using Kingroot (please do not use super sume afterwards people have bricked after using super sume!) Block updates & wait for the recovery & prerooted rom by rbox to be released. Yes of course you need to sideload Kodi if you want to, Kodi is not suppled with any root/recovery or rom. Sideload via your phone/adb/adbfire/ftp or es file explorer.
Sent from my SM-G900F using Tapatalk
Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
---------------------------------
Thanks for the info deanr1977,...
I did try to use a keyboard but the firetv2 just kept on booting all the way to the home screen no matter what i did.
This was before I had actually installed the rom though, so this may well explain why I could get to the twrp recovery menu.
Is there a time limit as to how quickly you have to press a particular set of keys on a keyboard to get the recovery menu to show up?
slackbladder said:
Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
Click to expand...
Click to collapse
Sure it will be back up soon, I'm in the UK & can access it fine so just sure it will only be a matter of time & it will be back up & running at your end?
Sent from my SM-G900F using Tapatalk
deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.
slackbladder said:
deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.
Click to expand...
Click to collapse
you mean Virgin Media? yes
You have around 10 or 6 seconds to select boot normal to the left or boot to twrp to the right.
I use a Logitech K400 plus keyboard, works perfectly & also has a touch keypad which comes in very handy to those apps which need a mouse to access.
This one here -
http://www.amazon.co.uk/Logitech-Wireless-Keyboard-QWERTY-Layout/dp/B00XJ3LVPI
No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.
slackbladder said:
No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.
Click to expand...
Click to collapse
I'm not happy with there set top box's or interface, but the Internet been fine for me, very fast almost all the time
I gave up in the and had to call them....
basically done all i could at my end... flushdns,... checked hosts, checked opendns, turned off everything except router and new VM| router (modem only mode) and tried an ipad... nope still no good. all this after a full shut down of everything and two reboots.
tried my phone,.... yep you got it right, full access to aftvnews.
whats even more stupid is that I'm using part of my wifi to access the net due to the poor 3g signal and i can access aftvnews.
Well VM staff said there's nothing wrong with network, nothing wrong at my end, and if i want access to keep using tor browser.
that's not really what i wanted to hear.
but he did mention that my IP address may have been blocked at the other end. although I'm not to sure why.
I also read some info from Elias, owner of aftvnews here... http://www.esaba.com/blog/limitations-of-siteground-vps-cloud-hosting/
seems he's not very happy either.
I've asked a bt customer to check for me,.. all okay. a sky customer... all okay,... and also yourself....
This only ever happened to me once before and that was on a forum many years ago. The owner had to unblock me so I could access the website again.
within two weeks I had been blocked again.
I've done many dumb things to this phone but I've finally found something I have not been able to recover from. Let's start with the list of things you guys will have me try that I've already done.
- FlashAll to the latest as well as the "Return to Stock" thread here on XDA
- Lenovo's Recovery Tool (I thought someone on XDA might be wrong about something and went with the Mfg's software, sorry I doubted you guys.)
I'm using linux so I convert your Flash bat to an sh but I've never had issues doing so before. I've rooted this and three other phones and I'd like to think I know what I'm doing I've spent about two weeks on here and other Android forums but this time I need to actually ask for your help.
Now on to my issue.
I installed Lineage OS using their lovely guide and everything was great until I found out my WiFi isn't working. Well can't have that, return to stock! Oh my WiFi is still dead. Wait now I can't even enable dev options because I cannot get past the initial setup without WiFI. OK full reset wipe and restore. Nope nothing doing.
It shows MAC unavailable in the initial setup. adb shell over via recovery shows no wlan0 then I tried TWRP and also OrangeFox because I saw a similar fix with it. I try ip link show but ip isn't there tried to su but it's not going. I think I have eveything mounted right but I'm more Arch than Android :\
And in 5 seconds someone is going to link a thread on here I couldn't find in the search with a easy 3 step procedure. But just in case that doesn't happen feel free to ask for any logs.
I'm a dumb. Be sure you do the Pre-install instructions as these are what fixed my issues.
Hi, is your phone ATT version? Thanks.
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
primusmagestri said:
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
Click to expand...
Click to collapse
you should not remove twrp. Your Firestick is soft bricked
primusmagestri said:
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
Click to expand...
Click to collapse
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Sus_i said:
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Click to expand...
Click to collapse
he removed twrp and he have 6.2.8.9. He cant install jailbreak now
anphabvn said:
he removed twrp and he have 6.2.8.9. He cant install jailbreak now
Click to expand...
Click to collapse
That is not true.
He installed 6.2.8.9 via TWRP and a boot.img, so the efuse for shorting may be gone (if he flashed a TZ image update at some point too, which we don't know).
Anyways. TWRP will block flashing preloader/LK and TZ images from the stock rom, so the old vulnerable preloader is still on his stick installed, therefore he CAN install the jailbreak again, that's for sure
In order to block the expoit, he need to do at least one update with the stock recovery (which will flash the new preloader). Only that will block the latest kamakiri 2.0.1.
anphabvn said:
you should not remove twrp. Your Firestick is soft bricked
Click to expand...
Click to collapse
Sus_i said:
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Click to expand...
Click to collapse
I've had some few crazy months and went away so I haven't checked the replies. I appreciate your responses and I'll try to see if I can resurrect the damned thing, just as a hobby since it didn't cost that much.
mmmk, fireiso burnt to usb, boot it up, been futzing with a ALU foil trying to find the sweet spot but no device seen by the script I'd guess that's what happens when it's FUBAR
primusmagestri said:
mmmk, fireiso burnt to usb, boot it up, been futzing with a ALU foil trying to find the sweet spot but no device seen by the script I'd guess that's what happens when it's FUBAR
Click to expand...
Click to collapse
If you see no device in lsusb while shorted, try the 'new' method (run bootrom-step with sudo and connect the stick without a short).
You can also use this OPs guide together with the latest mantis kamakiri:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)
Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...
forum.xda-developers.com