Develop Bugs

[Q] Kindle Fire wifi won't turn on at all

hey everyone,
I normally don't post on here because I find the info without needing to, but I can't find this even with google fu, any help appreciated
Problem: Wifi won't turn on
ROMs tried: Orignal Kindle ROM, CM 9 (hashcode make), CM 9 (Energy mod ICS)
Other notes: My methods worked on my other KFs, but not this one.... however its an older version. I was sure to make everything factory default, wipes the two caches, and out of frustration from TeamWin deleted everything on the flash and system (except TeamWin Obviously). I have the Android SDK setup to interface with the device, so if you need me to hit it from there let me know. Everything else works, but a wifi only tablet without wifi is useless in my book.
Thanks once again for any help I will go back to google fu'n and head to wall bashing

Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.

hmm
Thepooch said:
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.

update
initialhit said:
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
Click to expand...
Click to collapse
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.

final update
initialhit said:
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
Click to expand...
Click to collapse
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!

initialhit said:
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
Click to expand...
Click to collapse
Did the factory ROM flash correct the issue or still a no-go for WiFi?

Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.

kibusaki said:
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
Click to expand...
Click to collapse
Wrong device. Wrong forum.

help needed please !!

Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?

Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it

Broncos15 said:
Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it
Click to expand...
Click to collapse
No if that was the case then why will the file bo .bin.html ?

Mr.Dumb said:
No if that was the case then why will the file bo .bin.html ?
Click to expand...
Click to collapse
It shouldn't have .html on the end. Check the md5 sum for the file and make sure that it is the same as it should be, you should ALWAYS do this when messing with the bootloader

Maybe you flashed wrong images.
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...

maxaurelius said:
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...
Click to expand...
Click to collapse
I actually plan on doing this for a similar reason. My sons kindle battery life is appalling as it drains faster than before and charges slower, plus kindle updates are lacking badly and some things don't work anymore.
I hope you can fix it somehow.
Happy new year.

Mr.Dumb said:
Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?
Click to expand...
Click to collapse
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike

11fan said:
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike
Click to expand...
Click to collapse
Thanks a lot friends, i surely have a jem and i tried to read ad do things intended to do for jem only (seems strange to me that link i posted is for otter though i cross checked many times not to flash other device images but may be messed up in enthusiasm)
Never mind i eventually had to end up selling this on craiglist as a friend mentioned and got a working one from ebay ( to my shock it's reported as lost and stolen) looks i have great bad luck...
Now the kindle is just nothing unless i have cm in it but i will need all you guys help so that i dont end up like before
So please help me out with links so that i do all things correctly ...please i don't have any money now to loose or fix this ...
Thanks in advance
Edit : i tried to root kindle but was not able to, its on the highest or most up to date version of fire os as per amazon
I tried to root with restore by binary, cant see superuser in app drawer, able to see it in system/apps via root explorer
Tried to install firefire.apk it shows no root & root explorer doesn't rename system apps to .bak.... So i believe i cant root..
Please @11fan help me out now i need only cm on kindle thats fine for me.......
I'd be gratful to you for the help

Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk

11fan said:
Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy

Mr.Dumb said:
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy
Click to expand...
Click to collapse
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike

11fan said:
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike
Click to expand...
Click to collapse
Yes please help me with TWRP / CWM. Please & I want to install CM on it now

Did you get it rooted?
Mike

11fan said:
Did you get it rooted?
Mike
Click to expand...
Click to collapse
Yes
Hello @11fan
Edit : got it rooted, TWRP installed, made a nandroid backuo & tried to flash CM (chkd MD5 as well) but CM boot screen stayed for so so long...so I rebooted the device to TWRP and did a full wipe as well as format data...now have no os installed, cant mount as usb storage to copy nandroid...kooks like i've messed again....
Praying to God that I have some way again to restore...
Edit 2 : sorted via adb sideload

Glad you got it....i was going to tell you that the LONG cm screen on first boot is normal! I just loaded cm12 on mine last night and first boot took about 8 minutes, maybe longer as I forgot to time it!
Mike

[Q] Help!! Firmware gone and PC doesnt recognize my M9!!

I installed recovery to root my HTC One M9 yesterday. It seemed like I made some mistakes and now my firmware is totally gone and my computer doesn't recognize my phone anymore. However I still have access to recovery and I want to know if installing a Rom via SD-card is possible or not. If not, what should I do? Any help will be very appreciated. Thanks!!!

What recovery do you have access to? If it's twrp then yes you can load from sd card.. Have you tried an RUU for your phone? That should work as well.

enchanter100 said:
What recovery do you have access to? If it's twrp then yes you can load from sd card.. Have you tried an RUU for your phone? That should work as well.
Click to expand...
Click to collapse
Hello! Recovery I installed was PhilZ Touch CWM. I'm trying right now! Thanks.

Hi .. I think I made things confused a bit. What I meant by SD-card was external micro SD-card. Thanks!

Not sure what you mean by firmware. This is what you need to do:
Install the latest version of adb. Go to recovery, turn on sideload mode.
in cmd prompt-> adb sideload *location/name of rom.zip* e.g. c:\users\xxx\rom.zip
Restart and bam you are done

MadScientist2015 said:
I installed recovery to root my HTC One M9 yesterday. It seemed like I made some mistakes and now my firmware is totally gone and my computer doesn't recognize my phone anymore. However I still have access to recovery and I want to know if installing a Rom via SD-card is possible or not. If not, what should I do? Any help will be very appreciated. Thanks!!!
Click to expand...
Click to collapse
Does the computer recognize the phone in bootloader/fastboot/download mode? If you can enter recovery and download mode, then your phone is probably working fine (except for not having a working ROM) and your computer should see your phone on some level.
Are you using WIndows? I think you might need to get your device drivers on your computer working. Check Device Manager if you're in windows. With your phone connected, you should have 2 devices. One should be under a section called Android USB Devices (might be called My HTC) and the other is going to be under Portable Devices section (might be called HC One M9). If you don't have both, then you need to work on your driver issue on your computer.
Edit: Sorry if this is blunt, but since you seem to not really know some very basic terminology, i recommend that you do a LOT of reading on this forum so you can have a better understanding of what's going on with your device and how to solve your problem. I know you might feel like youre in panic-mode because your device won't boot, but you're going to get into more trouble if you just start trying a bunch of "solutions" without having any understanding of what you're doing. I know, because I've been there before.
Edit2: Also, it would help to steer you in the correct direction if you listed your location and carrier info

MadScientist2015 said:
Hello! Recovery I installed was PhilZ Touch CWM. I'm trying right now! Thanks.
Click to expand...
Click to collapse
FIRST THING, install TWRP 2.8.6.4, you can find it on captian_throwbacks thread here,

Aldo101t said:
FIRST THING, install TWRP 2.8.6.4, you can find it on captian_throwbacks thread here,
Click to expand...
Click to collapse
Actually, the beta version 2.8.6.4 is not recommendet anymore. Captian_Throwback now recommends using the official version 2.8.6.1. (Sidenote: The version number of the official one is lower because the numbering of the beta version is unofficial.)

Help please! Fire phone without an OS and stuck on amazon logo

Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance

Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.

Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.

lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.

When I get home I'll try using that file that you have posted.
I'll update the results.

lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?

Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.

lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.

Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.

This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v

@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"

AFTV 2 Sloane won't update past 5.2.6.0 How to force update adb/usb?

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.