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.
i bought my firetv off ebay and it came rooted with twrp running fireos 5.2.1.1 (551203220)
im wanting to install the new prerooted 5.2.4.1 images but im getting confused on what i need to do. seems like every post i read sends me back in circles to same websites and the info is confusing.
russ722 said:
i bought my firetv off ebay and it came rooted with twrp running fireos 5.2.1.1 (551203220)
im wanting to install the new prerooted 5.2.4.1 images but im getting confused on what i need to do. seems like every post i read sends me back in circles to same websites and the info is confusing.
Click to expand...
Click to collapse
It's easy. Would recommend you use a USB Stick & verify the files are not corrupt.
http://www.aftvnews.com/how-to-installupdate-a-package-using-twrp-on-the-amazon-fire-tv/
And in case your device was rooted with KingRoot or the likes...
http://www.aftvnews.com/how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery/
Note: NEVER WIPE "SYSTEM". And if you mistakenly do. Make sure you reflash a PreRooted ROM before any rebooting or powering down.
Y314K said:
It's easy. Would recommend you use a USB Stick & verify the files are not corrupt.
http://www.aftvnews.com/how-to-installupdate-a-package-using-twrp-on-the-amazon-fire-tv/
And in case your device was rooted with KingRoot or the likes...
http://www.aftvnews.com/how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery/
Note: NEVER WIPE "SYSTEM". And if you mistakenly do. Make sure you reflash a PreRooted ROM before any rebooting or powering down.
Click to expand...
Click to collapse
Thanks for the links. Is it possible to do this without a USB keyboard?
russ722 said:
Thanks for the links. Is it possible to do this without a USB keyboard?
Click to expand...
Click to collapse
Yes, you should be able to use the ADB Mouse emulator. I have never tried it but it should be the same steps/principal as it's done on the USB-less FireTV Stick. Just start reading from Step 12 of the following guide. (DO NOT DOWNLOAD FIRETV STICK FILES, Just follow how to enable the ADB Mouse Emu)
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Since you will combining two guides. Make sure your fully awake & know what you are doing. Don't flash the wrong devices file. The prior Guide is correct. From this guide you are only reviewing how to use ADB's Mouse Emu.
It might be easier to just get a USB Hub & connect both a USB Stick & KeyBoard. Btw, wireless USB keyboards work fine.
Y314K said:
Yes, you should be able to use the ADB Mouse emulator. I have never tried it but it should be the same steps/principal as it's done on the USB-less FireTV Stick. Just start reading from Step 12 of the following guide. (DO NOT DOWNLOAD FIRETV STICK FILES, Just follow how to enable the ADB Mouse Emu)
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Since you will combining two guides. Make sure your fully awake & know what you are doing. Don't flash the wrong devices file. The prior Guide is correct. From this guide you are only reviewing how to use ADB's Mouse Emu.
It might be easier to just get a USB Hub & connect both a USB Stick & KeyBoard. Btw, wireless USB keyboards work fine.
Click to expand...
Click to collapse
Thanks for the help I appreciate it..I'm gonna have to hold off on this for now since I don't have the correct USB cord .
Y314K said:
It's easy. Would recommend you use a USB Stick & verify the files are not corrupt.
http://www.aftvnews.com/how-to-installupdate-a-package-using-twrp-on-the-amazon-fire-tv/
And in case your device was rooted with KingRoot or the likes...
http://www.aftvnews.com/how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery/
Note: NEVER WIPE "SYSTEM". And if you mistakenly do. Make sure you reflash a PreRooted ROM before any rebooting or powering down.
Click to expand...
Click to collapse
ok got ahold of a usb keyboard.... question on flashing
when i flash do i wipe anything first? delvic,data ,cache?
idk how it was rooted any advice?
russ722 said:
ok got ahold of a usb keyboard.... question on flashing
when i flash do i wipe anything first? delvic,data ,cache?
idk how it was rooted any advice?
Click to expand...
Click to collapse
k, so let's go thru the options. After some info.
Is it a FTV1 (Only has a USB port) or FTV2 (Has a USB Port & a microSD Port).
Then go to Settings/Applications/Manage Installed Applications & look for either TowelRoot or KingRoot or anything with King in the name.
Also check if you see SuperSU v2.46, BusyBox, XPosed in Apps. They will be in alphabetical order.
Do you have a particular setup that would be to complicated to start from scratch?
Report back on the ?'S above & I can give you a more detailed answer for your device.
Got it!!! Running latest software. Thanks for all your help.all I did was wipe data,cache,delvick and flashed rom
russ722 said:
Got it!!! Running latest software. Thanks for all your help.all I did was wipe data,cache,delvick and flashed rom
Click to expand...
Click to collapse
Great to hear.
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.
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
dovedescent7 said:
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
Click to expand...
Click to collapse
I had a box the other week that was on 5.2.7.3 so the issue isn't if it only updates to your current version.
There may be a corrupted ota update apk in your build, have you made sure that ota updates are enabled in >settings>my firetv and tried the adb commands to make sure they are actually enabled?
Sent from my SM-G935F using Tapatalk
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
dovedescent7 said:
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
Click to expand...
Click to collapse
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
dovedescent7 said:
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
Click to expand...
Click to collapse
No, it works up to 5.2.6.9
Sus_i said:
No, it works up to 5.2.6.9
Click to expand...
Click to collapse
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
dovedescent7 said:
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
Click to expand...
Click to collapse
Yes I had to edit the post there as i got confused myself, I had wrote 5.2.7.0 lol.
So just to clarify 5.2.6.9 and under you can use mediatek software root.
5.2.7.0 and over requires the hardware short method.
Sent from my SM-G935F using Tapatalk
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
Click to expand...
Click to collapse
Lets say, it 'should' work :good:
I don't know if someone tested it on your OS version, because it's much older than the exploit itself.
The most current OS version back then was 5.2.6.8, the mtk root method came up and everybody was happy, finally a new root method for the second gen box
Big A patched it with 5.2.7.0.
Needless to say that most people tested it on 5.2.6.8 and .9.
It may be that the exploit isn't adapted to your OS version, but who knows.
Let us know what happens.
Good luck
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
dovedescent7 said:
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
Click to expand...
Click to collapse
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Sus_i said:
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Click to expand...
Click to collapse
THANKS!
NOW I NEED URGENT HELP
Rooted ftv 2 with short method now stuck at twrp.
Can i simply now install prerooted rom from within TWRP via rom on SD card?
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
dovedescent7 said:
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
Click to expand...
Click to collapse
Have you flashed this way, first the 5.2.6.7_v2 and then a later 5.2.7.x one? It's mentioned in the prerooted thread.
Wipe cache and dalvik before you reboot.
If it won't boot, you probably need to wipe data and internalsd too. Best is to use the 'format' data tab in TWRPs wipe section.
After that, the box should boot, but you need to log on at the setup, pair the remote and so on...
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
I just did this on a used device I purchased that came with 5.2.6.7 and it worked perfectly. Follow the instructions and you'll have no issues and none of that jumper stuff.