Related
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
I did a hardware root on my Fire TV a couple of weeks ago and decided to try to unlock it tonight. I was on the latest firmware and recovery so I had to flash the 51.1.0 recovery. I pushed the 51.1.1.0 OTA update, rebooted into recovery, and it ran through the downgrade fine with no errors. It then rebooted and never came back up. The power light never comes on and I don't think the USB port is even powered. So obviously it's bricked, but is there a way to fix it?
pathartl said:
I did a hardware root on my Fire TV a couple of weeks ago and decided to try to unlock it tonight. I was on the latest firmware and recovery so I had to flash the 51.1.0 recovery. I pushed the 51.1.1.0 OTA update, rebooted into recovery, and it ran through the downgrade fine with no errors. It then rebooted and never came back up. The power light never comes on and I don't think the USB port is even powered. So obviously it's bricked, but is there a way to fix it?
Click to expand...
Click to collapse
A few people here have described aftv just not powering on. There is apparently a problem with some aftvs and amazon is aware. I know you did a hardware root (something I know nothing about) but thought you should know its possible you have a defective unit.
My advice would be to tell amazon. They'll probably send a new one. If its not rootable you could try exchanging it at bestbuy or staples and hope you find one with rootable firmware. Though if you did a hardware root I'm thinking you're not in the US.
If you were on 51.1.4.1 or newer you bricked it. But since you have hardware access, just relfash the images from the latest update. You cannot use an old bootloader once you've booted 51.1.4.1.
rbox said:
If you were on 51.1.4.1 or newer you bricked it. But since you have hardware access, just relfash the images from the latest update. You cannot use an old bootloader once you've booted 51.1.4.1.
Click to expand...
Click to collapse
Unless it's your pre-rooted 51.1.4.1, correct?
Axecaster said:
Unless it's your pre-rooted 51.1.4.1, correct?
Click to expand...
Click to collapse
Yes. Official 51.1.4.1 can't use the old bootloader.
KLit75 said:
A few people here have described aftv just not powering on. There is apparently a problem with some aftvs and amazon is aware. I know you did a hardware root (something I know nothing about) but thought you should know its possible you have a defective unit.
My advice would be to tell amazon. They'll probably send a new one. If its not rootable you could try exchanging it at bestbuy or staples and hope you find one with rootable firmware. Though if you did a hardware root I'm thinking you're not in the US.
Click to expand...
Click to collapse
Good to know. I'll give it a shot today. I did HW root originally because I had two other aftv's that had unrootable firmware, and the HW root will work on every version.
rbox said:
Yes. Official 51.1.4.1 can't use the old bootloader.
Click to expand...
Click to collapse
Even though I had root past 51.1.4.1? I have access to the entire EMMC, there's no way of running the old bootloader?
pathartl said:
Even though I had root past 51.1.4.1? I have access to the entire EMMC, there's no way of running the old bootloader?
Click to expand...
Click to collapse
If you booted 51.1.4.1 you blew an efuse that prevents the old bootloader from working.
Just trying to get my head round this, I'm in the UK so my AFTV was not software rootable so have rooted using the soldering method. Can I install the earlier boot loader if I use the pre rooted image? And if so does that then in turn mean I can unlock the boot loader and more importantly install recovery and then use the more elegant method of USB storage than the stick & folder mount I'm using at the moment? Thanks in advance
DarthEwok said:
Just trying to get my head round this, I'm in the UK so my AFTV was not software rootable so have rooted using the soldering method. Can I install the earlier boot loader if I use the pre rooted image? And if so does that then in turn mean I can unlock the boot loader and more importantly install recovery and then use the more elegant method of USB storage than the stick & folder mount I'm using at the moment? Thanks in advance
Click to expand...
Click to collapse
If you hardware root and it never had 51.1.4.1, then you can follow the regular instructions once you have root working, starting with installing the old recovery, and then downgrading.
A coworker gave me a rooted (towelroot) fire TV sw version 51.1.0.1_user_510055620. After I hooked it up to my WiFi and registered it with my account there's no apps on it and it won't allow me to download Netflix. What is my next step? How do I get this thing up and running?
PrO... said:
A coworker gave me a rooted (towelroot) fire TV sw version 51.1.0.1_user_510055620. After I hooked it up to my WiFi and registered it with my account there's no apps on it and it won't allow me to download Netflix. What is my next step? How do I get this thing up and running?
Click to expand...
Click to collapse
Do you know if CWM is installed? Im thinking the netflix available on Amazon is incompatible with your old firmware.
Basically, i youre going to want to update to one of rbox's prerooted firmware versions. Its not hard but you do need to follow the guides carefully. Best bet is to go to aftvnews. He breaks it down really well.
I'm not sure. How do I check? I also need to update the xbmc to kodi (I've started to search!)
So far I've only been able to unlock the bootloader but I can't push the recovery.img for some reason. I hope there's an easier way by now. Lol
PrO... said:
So far I've only been able to unlock the bootloader but I can't push the recovery.img for some reason. I hope there's an easier way by now. Lol
Click to expand...
Click to collapse
just follow this guide up to the point of your existing software and then update to the latest custom rom by rbox.
http://www.aftvnews.com/start/
Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you
Does anyone know?
If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button
If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?
That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.
Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
rbox said:
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
Click to expand...
Click to collapse
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
zroice said:
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
Click to expand...
Click to collapse
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
rbox said:
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
but amazon is not giving those out isnt it? =)
zroice said:
but amazon is not giving those out isnt it? =)
Click to expand...
Click to collapse
The tablet that uses that for their unlock has a program to generate the unlock codes. It's similar to my unlock, but it runs on your computer to generate the code versus my unlock that runs on the device.
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
Yes, mine requires root.
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
BreakingDroid said:
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
Click to expand...
Click to collapse
I'm trying to get recovery for FireTV1 working, before I work on the stick. The problem is if I brick the stick, it's game over. I'm trying to find all the ways that I can brick it while working on the FireTV1, so I don't do it with the stick.
mjbxx said:
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
Click to expand...
Click to collapse
hmmm but didnt I read that once you update the bootloader unlock is no longer possible?
I got the FireTV with old software still which accoding to atfnews is not rootable but bootloader unlockable.
I read that once you update that the eFuse thing will become active and prevent unlock attempts.
All in all I just need to know if I should update the 1st Gen from the current " 51.1.4.0" build to the latest one to get root, disable OTA etc and still be able to unlock bootloader and boot directly to a recovery or if it would needed to be hardware rooted in order to do that. (to prevent the bootloader update.. which activates the efuse)
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
rbox said:
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
rbox is right. You can unlock the bootloader of a 1st-gen Fire TV using only an A-to-A usb cable. Although I'm not sure if it works on 51.1.4.0. I think it requires 51.1.0.2 or older.
I was going to write a guide, but the python script to generate the unlock code/file has been taken down, and it was really only useful for those who bricked with a locked bootloader, so I didn't try to find the script. Pretty sure the script was called cublock.py from here.
Assuming you can get ahold of the script, and it works on your software version, you would connect an A-to-A usb cable and reboot into fastboot by connecting via ADB and running
Code:
adb reboot fastboot
then run
Code:
fastboot devices
to ensure you're in fastboot and connected, then run
Code:
fastboot oem emmc-info
to get a code that you need for the python script. The code is in the form
Code:
(bootloader) 0x12345678
and you use the python script to generate the unlock code like this
Code:
./cublock.py 56 12345678
That will generate an unlock file which you then use as follows:
Code:
fastboot flash unlock /path/to/file.unlock
After that, you can use fastboot to flash custom recovery if you'd like. Instructions are at the bottom of this guide under the "Repair Recovery with Fastboot Mode" section. I've attached a screenshot of the process from my notes for the unwritten guide, back when I tried it.
ill try that - thanks very much
what driver to use for fastboot mode?
zroice said:
what driver to use for fastboot mode?
Click to expand...
Click to collapse
I'm not sure which Windows drivers to use. My Mac didn't need any.
This should help concerning Windows ADB/Fastboot drivers:
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Tools.zip package from this post includes the cublock.py file
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
zroice said:
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
Click to expand...
Click to collapse
P.S: I could try to boot linux from USB if that helps - but that probably also needs some sort of drivers doesnt it?