Could someone point out the steps for me to get my newly bought Firephone working without the fear of bricking it or loosing root?
I want to achieve:
- root
- block updates
- install latest possible Amazon Firmware
- ability to install CM11 later
If possible please point me to the relevant threads here in the right order.
http://forum.xda-developers.com/fire-phone/help/installing-root-safestrap-cm11-t3157339
Most of the info is here, you may have to check elsewhere for blocking updates though.
Latest firmware can always be installed via OTA or by downloading the update file from here http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550 and placing it in the root of your storage, then going into device settings and selecting check for updates, in which case it'll detect the file.
i recommend holding off on doing an Over The Air update as 4.6.6 seems to be giving users some issue, I've seen reports of not being able to root so it might be best to download 4.6.3 until things are clarified.
The walkthrough in my signature should cover all of that. Romario is right about 4.6.6 for now.
Related
Hello!
I have just recieved my Fire TV (not plugged in yet).
My goal is XBMC.
I want to know what is the correct order to achieve root, xbmc with maximum stability...
I have collected a mass of guides with everything I need, but I do not know in what order I should do them...
Should I block updates first (or at all)?
Should I first update it to the latest FW?
When should I root? when should I sideload APKs and stuff...
Thanks in advance! :laugh:
Doesn't really make a difference. But follow this if you want:
1. Update first to the latest firmware (before you get too used to the old UI)
2. Update remote if it's available.
3. Then block updates.
4. Then root
5. Sideload all your apps.
1206
roligov said:
Doesn't really make a difference. But follow this if you want:
1. Update first to the latest firmware (before you get too used to the old UI)
2. Update remote if it's available.
3. Then block updates.
4. Then root
5. Sideload all your apps.
Click to expand...
Click to collapse
Thanks alot
In the future (after I block updates) - is there a reason to not update again? Do I lose root each update?
Thanks
Gaiosan said:
Thanks alot
In the future (after I block updates) - is there a reason to not update again? Do I lose root each update?
Thanks
Click to expand...
Click to collapse
Yes, you lose root with each update. The reason to not update is to keep root since we don't know if the next update will block the current rooting exploit and prevent rooting.
Hi all, apologies if this has been answered but I've search for the last couple of days without finding the answer.
I have 2 AFTV's one on the latest update and one on 51.1.4.0_user_514005520.
I want to manually update from 51.1.4.0_user_514005520 to 51.1.4.0_user_514006420. I have the bin file but unsure if this is possible without being rooted and have su installed. Currently the latest Kodi and SPMC don't seem to work at all on this software version.
I would expect to be able to place the bin file somewhere on the machine a then do a "adb reboot recovery" but I've not had any luck in working out how this is done. It's signed after all so I see no issue in allowing the update.
The reason I'd like to not update any further than 51.1.4.0_user_514006420 is due to the fact the efuse is blown on the next increment of the updates. With all the great work been done on here to obtain root on higher firmwares has made me want to keep the efuse intact and on the lowest working updating.
Many thanks to anyone who can help.
o71g said:
Hi all, apologies if this has been answered but I've search for the last couple of days without finding the answer.
I have 2 AFTV's one on the latest update and one on 51.1.4.0_user_514005520.
I want to manually update from 51.1.4.0_user_514005520 to 51.1.4.0_user_514006420. I have the bin file but unsure if this is possible without being rooted and have su installed. Currently the latest Kodi and SPMC don't seem to work at all on this software version.
I would expect to be able to place the bin file somewhere on the machine a then do a "adb reboot recovery" but I've not had any luck in working out how this is done. It's signed after all so I see no issue in allowing the update.
The reason I'd like to not update any further than 51.1.4.0_user_514006420 is due to the fact the efuse is blown on the next increment of the updates. With all the great work been done on here to obtain root on higher firmwares has made me want to keep the efuse intact and on the lowest working updating.
Many thanks to anyone who can help.
Click to expand...
Click to collapse
If you are not rooted it is no way of doing this. Your box can only be updated OTA and that will take it to the newest update available in the stream.
I used the KINGOROOT technique to root my SM-T800. I had to downgrade to firmware T800XXU1ANF8_T800XAR1ANF6_XAR (ANF8) to allow KINGOROOT to work.
The SM-T800 is now offering an OTA update. The only detail provided is "Size 39.96 MB" No clue what version it is.
Is there any way to determine what version of update would be loaded?
Would root be maintained?
I have purchased SuperSU Pro, and enabled "Survival Mode", which says it "attempts" to keep superuser access across OTA updates.
Can anyone confirm whether SuperSU Pro's "attempts" are actually successful on the SM-T800?
Once rooted you should disregard small updates.
You never know what this update will do. It could do anything from something simple to locking your bootloader. It won't be the first time people have ended up locked out of their device after an update.
If you really want to flash it, let it download then flash it with FLASHFIRE.
ashyx said:
Once rooted you should disregard small updates.
You never know what this update will do. It could do anything from something simple to locking your bootloader. It won't be the first time people have ended up locked out of their device after an update.
If you really want to flash it, let it download then flash it with FLASHFIRE.
Click to expand...
Click to collapse
I wasn't thinking of the small updates - I was going jump ahead and flash the latest stock Lollipop (T800XXU1BOE2_T800XAR1BOC5_XAR) Android 5.0.2?
At this point I've got the tablet usable with KitKat - thanks for all your help!
I won't have time to mess with it for a few weeks probably, so I'll defer the Lollipop update till then.
I guess I have already let it download something, although it doesn't say what. However, it is nagging me to install the OTA update all the time. So how can I
1) Capture the downloaded update file?
2) Find out what version it is so I can decide if I want it?
3) Stop the nagging to install the update?
If you're going the whole hog then just flash Lollipop with Flashfire and you'll keep root.
So I rooted my 1st Gen FireTV as soon as I got it, and I think I'm on the very first Firmware. I had blocked OTA updates and as far as I know have never updated. that being said, I don't think I've ever done much that actually used the Root functionality. The only thing I really do is use Kodi 15.1 annnnndddd thats it.
I do own an Amazon Echo, and saw that Alexa is now part of the new FTV update. Not sure if I can link them together and just boss my FTV around via the Echo or not, but I like the idea of more / updated functionality from my FireTV
Soooo thoughts? Am I missing anything great by updating and giving up Root? I have seen that I could update with pre-rooted firmware but then I would have to install CRM / Recovery, then do incrimental upgrades after installing a Bootmenu, etc. That seems like a lot of stuff I need in place and a lot of points of failure or bricking for something I'm not sure I even need =/
If so, what would you suggest is the easiest way to re-enable OTA updates? I was going to ADB and use pm enable com.amazon.dcp Thanks for any advice, by the way, I'm pretty new at this.
Well OK then =/
Well, like many things, the answer is up to you.
If you have no need for root then you have no need to for root.
I like, many others, prefer the option of having root, recovery and unlocked bootloaders.
If you don't use anything Amazon and only use it for Kodi then root will give you the ability to freeze the FireTV Launcher have Kodi set as Home.
Installing recovery and a updated pre-rooted ROM isn't too difficult and you've done the 'hard' part by having root already.
Update wise, unless you want to be running the latest versions then yes you'll have to on top of it otherwise you can just update to the current version and be done with it.
You can check back every now and then to see what the additional updates from Amazon fix or what features it adds and decide then if you want to update.
If anyone has any information on this latest update Components let me know please because, I have yet to figure out how to disable OTA updates, but a user on here might’ve given me a way. I will test on ADB soon.
I am already on latest OS 5.2.7.7 because of STUPID OTA. But now I have another update from yesterday called Components.
Will this Components update ruin anything that the OP from the root thread has created?
I want to try rooting on 5.2.7.7 soon but I’m just hoping this other update didn’t ruin my chances.
At this point, does it even matter anymore? I’m already updated to every single latest update available on my Sloan box 2nd gen. I can’t do much root wise because I’m afraid to open my device and I’m stuck with a bull**** rom and Home Screen. Can’t even add a custom launcher as Amazon also broke this with their firmware updates...
G S W said:
If anyone has any information on this latest update Components let me know please because, I have yet to figure out how to disable OTA updates, but a user on here might’ve given me a way. I will test on ADB soon.
I am already on latest OS 5.2.7.7 because of STUPID OTA. But now I have another update from yesterday called Components.
Will this Components update ruin anything that the OP from the root thread has created?
I want to try rooting on 5.2.7.7 soon but I’m just hoping this other update didn’t ruin my chances.
At this point, does it even matter anymore? I’m already updated to every single latest update available on my Sloan box 2nd gen. I can’t do much root wise because I’m afraid to open my device and I’m stuck with a bull**** rom and Home Screen. Can’t even add a custom launcher as Amazon also broke this with their firmware updates...
Click to expand...
Click to collapse
Doesnt do nothing apart from modifications to cloudfront server urls and some of the /system files which prevent adb/accessibility of custom launcher replacements and ftvlaunchx bypass apks etc etc .
Basically the 2nd part of the 5.2.7.7 fcks the custom launcher compatibility .
To get round it , root the device install custom launcher ...
pm disable com.amazon.tv.launcher
wait 5 seconds
pm disable com.amazon.firehomestarter