Related
Hi .. would really like some help as I got a replacement G2 and I need to return my broken phone back tmrw and would like to root it.
I actually rooted my first g2 using temp root/visionary about a year ago...
but now I can't seem to understand the wiki's or any guides on how to root my phone again. . help!
Tried the AMT way, says device is not connected
Currently trying to use this guide : http://forum.xda-developers.com/showthread.php?t=1107911
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
any help would be appreciated.. sorry I am a complete noob at this
ahan421 said:
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Do you have Android debugging enabled on your phone? I don't know if it matters but I think your sdcard shouldn't be mounted when you connect it to your PC.
With the above things done, you should be able to type
adb devices
And it should list your device and its serial number.
You probably need to install drivers. I'm assuming you're using windows?
You can get the driver package here
You'll need to downgrade first with this guide
Then I recommend the wiki method to root
-Nipqer
I just downloaded the HTC drivers
i'm following the downgrade guide now
i downloaded the 2 files and put them in the platform-tools folder
already having trouble with the first step
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
> adb shell cat /dev/msm_rotator"
where do i type this command?
"> adb shell cat /dev/msm_rotator"
sorry if i sound like an complete idiot.. i have no clue what to do.
alright, i read through some of the adb for dummies
when i type in adb devices i do not see a serial number.. but i've installed the htc drivers already
is there something else i need to install? thanks
edit:* Yay i just got the drivers working, serial number is now showing!
edit 2: i had no idea what i was doing... somehow got through the instructions, downloaded some pda drivers, followed the guides and now my phone is rooted!
i felt like Neo typing in the codes... Thank you guys. Thank you XDA!!
Glad to hear you got it sorted out. Sounds like a good learning experience
I have a Kindle fire running 6.3.2 I attempted to root with KFU and it got stuck halfway through the process and was able to get it back to normal using soupkit. Was going to try again but am having problems getting KFU to install SU and root,.
QUESTION... (and I have googled this to death and read posts and posts and posts but everything points to using KFU) - Is there a way to root and get SU without using KFU? Soupkit seems to work fine but from what I understand it can't install SU and root. Any help is appreciated
Depending on what your version of android is it won't install SU. Go online and download the apk for SuperSU or SU and install it using ES File Explorer.
androidnooob98 said:
Depending on what your version of android is it won't install SU. Go online and download the apk for SuperSU or SU and install it using ES File Explorer.
Click to expand...
Click to collapse
Thanks for the reply, I finally got it to working in windows. KFU would give status of online but boot status unknown.. when it finally gave status of 4000 and online KFU worked.
Hey first post here and followed the http://forum.xda-developers.com/showthread.php?t=2069117 guide on how to root my kindle and i have a few questions.
So i've done everything the guide has said and now my kfhd is showing the fastboot mode and i'm lost on what to do next. i have tried a few of the options in the KF first aide ( option 21 ) and nothing has happened. If anyone could give me some insight to some small issue i have overlooked i would appreciate it
Edit: I just did option 21 and got as far as the prompt asking me to launch superuser which i could not find on my device any thoughts?
Ping not recognized
Ok so i'm pretty sure i'm half way rooted i have busy box installer and the root checker in my app list.
The only thing i don't have is the superuser and I think this has to do with the line in the prompt which says 'ping' us bit recognized as an internal or external command, operable program or batch file. even though the root program continues to root and eventually says sucsess waiting on superuser nothing happens because i don't have super user to continue with.
heres a link to 2 pictures imgur.com/a/SIKf4
EDIT: I just tried to install the google play store with the kindle fire first aid and the prompt kept saying /system/bin/sh: su: not found
hopefully this information helps. I also updated my imgur album with the failed Google store install prompt picture
Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.
akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.
akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.
akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.
Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!
Q&A for FireTV Full Bootloader Unlock
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.
Before posting, please use the forum search and read through the discussion thread for FireTV Full Bootloader Unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Worked perfectly for me. Just wanted to say thanks!
Stuck at CHMOD step...
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?
RuffRhyno said:
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?
Click to expand...
Click to collapse
I don't know your level of experience so I'm going back to basics.
You mentioned that you tried in Windows and OSX.
Where exactly are you issuing the command?
Are you in the adb shell?
Did you type 'adb shell' after pushing the file to the FTV?
After full unlocking of boot loader and using an ssh server on the firetv, when I connect I am stuck with a root prompt. is there a way to step down the shell to manage package installations. for some reason "pm" command is not functioning correctly with root. I wish to use this for remote administration, I suppose, using the commands "start adbd" and "stop adbd" from within an ssh term session and then connecting to adb port might suffice but I would prefer to keep adb service stopped since it is not password protected. campuses are always full of prowlers and pranksters at all times. thanks
Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!
mozzer27 said:
Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!
Click to expand...
Click to collapse
That is normal and yes your root is fully unlocked if you get [email protected] when adb shell command is being sent.
Could this be used on the fire TV stick? version 54.1.0.2_user_102018720?
I still have a sealed german fire tv, which came with 51.1.3.0_user_513010720, for which no software root is known.
After having studied the unlock-code at the original Fire HDX thread and the modified tool for the Fire TV I wonder if the following might be possible.
From the hdx thread the first steps:
Code:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
create a file unlock.img with following content:
0xmmssssssss
where mm=manfid and ss=serial
encrypt it with my vortox fork of signing tool at
https://github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
This seems identical, what the routine at https:// github.com/androidrbox/aftv-full-unlock/blob/master/jni/aftv-full-unlock.c does.
rbox said:
For now, this requires root. Apparently, the IDs that are required for this can be gotten through fastboot, so if someone can figure that out, then brand new Fire TVs with 51.1.0.2 or older can be unlocked and have recovery installed before booting the first time.
Click to expand...
Click to collapse
For what exactly is root necessary? You can get the manfid and serial without root.
The fire-tv-tool then base64 encodes the signed result from cuber.
Code:
snprintf(idme_cmd, sizeof(idme_cmd), "idme unlock_code %s\n", bptr->data);
system(idme_cmd);
That should be also possible without uid 0.
Before I brick my fire tv. I wondered if someone could shed some light, if I might succeed trying
a) using cuber manually to sign the unlock data, base64-encode it and unlock my bootloader with idme unlock
b) using cuber manually to sign the unlock data and use ./fastboot flash unlock unlock.signed like it is possible with the Fire HDX-devices.
After that I could fastboot boot twrp and finally get root and downgrade. Possible or did I miss something?
The bootloader on your fire tv is not vulnerable to this exploit so it is not going to work. That is the reason "Fire TVs with 51.1.0.2 or older" is stated.
adb after full-unlock-bootloader
Can someone please help me? AFTER installing unlocked bootloader, when connected to fire tv via adb, I no longer get a pop up window for Superuser request: Adb on the fire tv. I need to know if that is normal and if ADB automatically gets SuperSu rights?
PS: Adb still works fine just no popup asking me for Superuser request or a pop up saying saying Adb has been granted permission. Thanks
Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu
goodbye hppalm said:
Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu
Click to expand...
Click to collapse
You most probably have a partial not a full unlock bootloader, that is why. CWM only needed a partial bootloader and so is boot menu however go ahead a fully unlock it, will help you later if for some reason box gets bricked.
Ty bula for comments, I think I screwed my firetv, by the thread it said if u have recovery working everything should be fine, I tried the boot menu, now stuck on white logo and no response, is it hard bricked now
Downgrading AFTV using a Mac
PLEASE HELP!
Has there been any update to AFTVnews posting titled "How to manually upgrade or downgrade the amazon fire tv". The instructions are old (June 2014)and don't seem to work. I've searched the internet and can't seem to find any way to downgrade AFTV before unlocking the bootloader.
Also, I can't find anything detailing how to use adbfire in order to downgrade AFTV.
In addition, I found information on how to downgrade AFTV firmware, but nothing for Mac users.
Your help would be greatly appreciated!!
i used the guides on aftvnews.com to unlock the bootloader on my original firetv. they worked great and I was using a mac
I'm running Pre-rooted 51.1.4.0_user514006420 and I'm fairly certain I need to update my Clockwork which is why i'm trying to follow the unlock guide online to fully unlock from following instructions.
However I hit a dead wall when just getting the process going. I've been stuck here long ago and I'm not revisiting this same issue once again.
When running the command.
Code:
[email protected]:/ adb push aftv-full-unlock /data/local/tmp/
My return is
Code:
adb push aftv-full-unlock /data/local/tmp/
cannot stat 'aftv-full-unlock' : No such file or directory
1|[email protected]:/ $
I have the file in the adb directory as instructed.
I really hope someone has some insight. I can't go beyond this version unless figured out to maintain root and when getting to this current firmware I'm on my FireTV doesn't ever sleep anymore.
Thanks!
May I suggest using this utility to automate the procedure?
http://forum.xda-developers.com/showthread.php?t=2736774
is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx
htchd2fix said:
is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx
Click to expand...
Click to collapse
No