Related
I am old school rooter custom ROM user on many devices. ( Nook Color / Transformer / LG-G2x ) So I understand the process of rooting and bootloader's and adb ect..... BUT ..... I am brand new to Kindle Fire. Just bought one today. I have looked over these forums for hours. I have learned a bit ... but still not 100% sure of the best route to take. I found a great option with BuritoRoot3, but seems im screwed because I have 3.6.x stock. I want FULL root. I don't care about Kindle desktop or stock crap. I have a ROM I want to run (HellFire) but I dont fully understand now without BuritoRoot3 how to go about
1) Rooting
2) Making a backup / recovery
3) FIREFIREFIRE
4) TWRP or CWM ?
or some easier why to go about this. Like a drop back to 6.2 stock some how ?? is that possible ....
Any guidance would be greatly appreciated.
Thanks again
Thibor69 said:
I am old school rooter custom ROM user on many devices. ( Nook Color / Transformer / LG-G2x ) So I understand the process of rooting and bootloader's and adb ect..... BUT ..... I am brand new to Kindle Fire. Just bought one today. I have looked over these forums for hours. I have learned a bit ... but still not 100% sure of the best route to take. I found a great option with BuritoRoot3, but seems im screwed because I have 3.6.x stock. I want FULL root. I don't care about Kindle desktop or stock crap. I have a ROM I want to run (HellFire) but I dont fully understand now without BuritoRoot3 how to go about
1) Rooting
2) Making a backup / recovery
3) FIREFIREFIRE
4) TWRP or CWM ?
or some easier why to go about this. Like a drop back to 6.2 stock some how ?? is that possible ....
Any guidance would be greatly appreciated.
Thanks again
Click to expand...
Click to collapse
Skim this...
http://forum.xda-developers.com/showthread.php?t=1552547
It will get you caught up on basic terminology, installing drivers, relevant fastboot/adb commands. Focus on post #3... near the end, it has a step-by-step on how you should go about flashing a custom ROM on a stock device. You do not need to root the stock software if you are going straight to a custom ROM. The document is slightly dated as it refers to an older version of FFF, but it will get you started nonetheless. You can update to the newest version of FFF when you are all done without much trouble.
Right now, the preferred recovery is TWRP because CWMR has problems flashing ICS based ROMs, so you should probably go with that one. Backups/restores should be pretty self-explanatory once you get TWRP installed.
The most recent Fire I bought, I didn't waste any time going through the rooting crap. I just put it into fastboot, installed FFF and TWRP, and used adb to push ICS to sdcard for flashing in recovery.
I never even let the stock OS boot
Use TWRP for now, CWM has issues with the latest kernel.
And definitely read the guide kinfauns gave you a link to. As long as you have a couple of brain cells to play with, it'll give you a good foundation to work from.
soupmagnet said:
The most recent Fire I bought, I didn't waste any time going through the rooting crap. I just put it into fastboot, installed FFF and TWRP, and used adb to push ICS to sdcard for flashing in recovery.
I never even let the stock OS boot
Use TWRP for now, CWM has issues with the latest kernel.
And definitely read the guide kinfauns gave you a link to. As long as you have a couple of brain cells to play with, it'll give you a good foundation to work from.
Click to expand...
Click to collapse
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers
Thibor69 said:
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers
Click to expand...
Click to collapse
On a stock device, you have 2 choices...
1) Use a factory cable to get directly into fastboot mode
2) Use pokey9000's fbmode exploit to set the bootmode to fastboot (4002) and reboot
In the URL I gave you, there are links and directions on how to use fbmode near the end of post #3.
Fastboot....
Thibor69 said:
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers
Click to expand...
Click to collapse
I had the same question when I first started with the KF. Basically you need to change the "Bootmode" of the KF to boot into Fastboot mode. This is most easily done using the Kindle Fire Utility then restart your KF.
It is really not necessary to do this to root/install a custom ROM and it has lead a lot of inexperienced users to get "stuck at the yellow triangle," but if you want to play around with it, it is easy to do.
Hope this helps. Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
pokey's fbmode is the way to go for 6.3
Sent from my Amazon Kindle Fire using Tapatalk 2
Entropy512 said:
pokey's fbmode is the way to go for 6.3
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Were is pokey's fbmode link ? I can't find it.
Thibor69 said:
Were is pokey's fbmode link ? I can't find it.
Click to expand...
Click to collapse
It's this one: http://forum.xda-developers.com/showthread.php?t=1414832
They didn't fix it in 6.3
Alternatively, it's "easier" to hop into fastboot mode with FFF, so that shouldn't worry you much once it's installed.
Dasanko said:
It's this one: http://forum.xda-developers.com/showthread.php?t=1414832
They didn't fix it in 6.3
Click to expand...
Click to collapse
I think It'd be pretty tough to "fix" fbmode without locking the bootloader. It's only a matter of time though.
Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.
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
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.
This is a seventh generation Fired HD 10. I've had it for a few years, and when I first got it, I came on here and followed some instructions for how to root, install SuperSU, etc. I don't remember the exact instructions, and at this point I would like to unroot it. I don't have ADB or anything installed (I've changed computers since then), and at this point I barely remember anything I did when I rooted it in the first place. Doing a factory reset was NOT the solution, though. Did that twice, and even wiped partition, and SuperSU is still installed and Fire Toolbox doesn't work on it at all. Any direction to a proper thread or instructions would be much appreciated.
I edited the title and opening post for more clarity. I really am lost here, so any help would be greatly appreciated. If there's any pertinent information I left out that might help answer my question, please let me know, if I can figure it out I'll be glad to edit my post again. Probably worth adding that the fire OS version is 5.6.0.1