Hey, so I got to twrp on the FTV2 Sloane via the shorting method with help from sus_i.
Done a full wipe,and then the box wouldn't show up on adb to enable me to push a rooted rom, not thinking about the microsd slot I done the unthinkable and tried to reboot to recovery causing the dreaded amazon logo brick.
My Problem is I've been trying the unbrick_firetv tool on windows and Ubuntu and it's just not happening for me?.... It's stuck on mediatek inject reading 0%, how long should the process take?
If that wasn't bad enough the short method is no longer working, it's just going straight to serial protocol mismatch error as soon as I connect power.
I know these Sloanes are brutal for bricking/rooting/flashing.
Does anyone got advice, should I leave it in a cupboard for a few weeks and hope (like what usually happens) it magically comes back to life? Or is there anything else I can do apart from lob it out window
###edit ### unbricked by using newer method (shorting dat0), I learned that the method I described above is now obsolete and anyone facing bricked device should USE THE NEW SHORT METHOD, UNBRICK ROOT TWRP SLOANE
Bertonumber1 said:
Hey, so I got to twrp on the FTV2 Sloane via the shorting method with help from sus_i.
Click to expand...
Click to collapse
What firmware update were you on before you shorted? I have a stock unrooted 2nd gen Sloane running 5.2.7.6 . Is the short method my only option?
Logos Ascetic said:
What firmware update were you on before you shorted? I have a stock unrooted 2nd gen Sloane running 5.2.7.6 . Is the short method my only option?
Click to expand...
Click to collapse
@Logos Ascetic Yes you have to use the short method on all the latest firmwares I think anything above 5.2.6.2 requires the dat0 short, for sure 5.2.7.6 requires the short.
Sloane is difficult to root this way and requires patience. But you'll get there if you keep at it.
Related
So I've rooted my Kindle Fire HD 8.9" and now I'd like to know what I need to do next in order to get an Android ROM (probably CM10) running on it. I have searched all around but I can not for the life of me figure out how to get it working. I know I need to get TWRP installed so I can flash the rom but I do not know how to get TWRP installed. Any help would be great at this point!
stergmtl said:
So I've rooted my Kindle Fire HD 8.9" and now I'd like to know what I need to do next in order to get an Android ROM (probably CM10) running on it. I have searched all around but I can not for the life of me figure out how to get it working. I know I need to get TWRP installed so I can flash the rom but I do not know how to get TWRP installed. Any help would be great at this point!
Click to expand...
Click to collapse
This: http://forum.xda-developers.com/showthread.php?t=2128175
Sent from my KFHD using xda premium
Firmware version/method
stergmtl said:
So I've rooted my Kindle Fire HD 8.9"
Click to expand...
Click to collapse
I tried months ago to root my 8.9... with no success (Bin4ry's V 17). What method did you use to root and do you remember what firmware you had before you did it? I think I might be stuck because I have version: 8.1.4. Has anyone had success rooting the 8.9 with 8.1.4?
:fingers-crossed:
root KFHD 8.9
Green Wenonah said:
I tried months ago to root my 8.9... with no success (Bin4ry's V 17). What method did you use to root and do you remember what firmware you had before you did it? I think I might be stuck because I have version: 8.1.4. Has anyone had success rooting the 8.9 with 8.1.4?
:fingers-crossed:
Click to expand...
Click to collapse
I have.. but I did experience a lot of frustration at first
May I ask how far you go in the process before it fails?
In my case the problem was getting my kindle to be recognized....turns out
I needed the right driver.
Sorry, replied to questions not directed at me.
Green Wenonah said:
What method did you use to root and do you remember what firmware you had before you did it? I think I might be stuck because I have version: 8.1.4. Has anyone had success rooting the 8.9 with 8.1.4?
Click to expand...
Click to collapse
I've done it with version 8.3.0 yesterday following this approach as suggested here.
Got some errors the first time. After factory reset second time was fine.
Had my problems with GMarket afterwards but following this (german!) approach it worked fine.
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
I do not want to give you a hard time but why you guys do not read before doing it. There are few post here mentioning that boxes get bricked if you use supersu-me. Can you connect to it through adb? The only way to get it back if somehow rbox will release an unbrick image as he did for firetv 2
sardiswolf said:
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
Click to expand...
Click to collapse
Same thing happened to me with fire stick but not stuck on amazon logo but fire TV stick logo.
Sent from my iPhone using Tapatalk
READ ME!
If you read the Kingroot thread on this forum, located here. You will find that the authors of Kingroot have taken exception to the author of SuperSu and anyone else who uses it in their programs to replace Kinguser, because of the claims of conflicting programs and/or malicious coding. Kingroot authors counter claim that programs like Super-Sume improperly remove Kingroot leaving orphaned files which may cause problems. But the author of Super-Sume says his program will not brick your device.
Most people have had no luck installing SuperSu on their devices after being rooted by Kingroot even though Kingroot authors claim they could co-exist on the same device, because Kingroot has added a restriction regarding SuperSu. So consequently those who have gotten SuperSu installed on their Kingroot rooted devices have ended up with problems.
Don't install random stuff via root without custom recovery! Its just as effective as a pull and pray people. You need some protection.
Just be patient!!
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
sardiswolf said:
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
Click to expand...
Click to collapse
There's really nothing you can do if you have a locked firetv1 box that is bricked.
rbox said:
There's really nothing you can do if you have a locked firetv1 box that is bricked.
Click to expand...
Click to collapse
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
sardiswolf said:
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
Click to expand...
Click to collapse
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
rbox said:
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
Click to expand...
Click to collapse
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
sardiswolf said:
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
Click to expand...
Click to collapse
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
rbox said:
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
Click to expand...
Click to collapse
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
sardiswolf said:
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
Click to expand...
Click to collapse
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
rbox said:
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
Click to expand...
Click to collapse
Thanks, I will wait for your rom and use aftvnew post the unbrick way to do factory reset.
looks like the usb keyboard could not make it get into factory reset area.
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
mrchrister said:
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
Click to expand...
Click to collapse
no way to solve it. bought another brand tv box.
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
mrchrister said:
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
Click to expand...
Click to collapse
If your bootloader isn't already unlocked and you bricked a FireTV 1, there isn't anything that can be done from a software perspective.
i was hoping to dd system.img through hardware emmc soldering. do you think this could work to revive it?
Sent from my iPhone using Tapatalk
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
dizzymon said:
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
Click to expand...
Click to collapse
Your own post says "up to ... 6.3.0.1". Any recentl tablet is going to be above that, so, no it won't work. The best way to debloat is with the "Toolbox"
I used toolbox but I can't seem to get other web browsers to install. Any ideas?
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I don't have an issue. Chrome is working fine on my HD 10 2019. OS ver 7.3.1.6
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I was able to install Vivaldi, from the Google Play Store.
Droid4200 said:
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Click to expand...
Click to collapse
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Droid4200 said:
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Click to expand...
Click to collapse
I am able to boot into the bootrom through the other exploits on fire devices, the bootrom is how every fire device has been unlocked in the last 2years. No one really has put much effort into unlocking it though. Running the exploit and plugging in to PC during the "waiting for bootrom" would boot it right into the bootrom (lsusb detects mediatek phone), but that is as far as i got as the exploit would have to be set up i believe similar to the firestick4k exploit. I have 2 rooted and one that is not rooted. The mtk-su exploit was blocked on first update. But the mtk-su is a temp root and you can not change the system folder. i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Michajin said:
... i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Click to expand...
Click to collapse
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
i dont know if anyone has tried to check to see if the bootrom is available on newer OS. But no one has written code to unlock if there is a bootrom exploit. I will update one this week and see if it will still boot into the bootrom. The mtk-su was just a temp root. The bootrom exploit has potential for full unlock, root, and TWRP... Has anyone try to access it on 7.3.1.6?
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
Michajin said:
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
Click to expand...
Click to collapse
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
newnewcomputer said:
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
Click to expand...
Click to collapse
i can give it a shot this weekend if i have a device that is on 7.3.1.1. But so few people got access to root or 7.3.1.1, unlocking may be moot if no developers have a want to make a rom. On that note, there should be a shorting method to access the bootrom. Amazon disabled the volume/power on trick somewhere between 7.3.1.2 and 7.3.1.7, not sure what version disabled the easy way. so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Michajin said:
... so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Click to expand...
Click to collapse
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Michajin said:
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Click to expand...
Click to collapse
Yeah there was a successful downgrade from 7.3.1.1 already, it has the same lk/pl as 7.3.1.0 but I haven't been able to get into the bootrom on 7.3.1.2, might need to look into shorting a pin.
I think bootrom through the volume button was killed before 7.3.1.7 though
I can confirm bootrom through the volume button on v7.3.1.7 is not working.
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Michajin said:
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Click to expand...
Click to collapse
@Michajin The bypass-utility will run fine on windows, check the README how to set up python and libusb on windows.
I'm not sure if the kamakiri-RPMB Downgrade will work on windows though.
You can use FireISO for both, it should have everything included.
Steps would be:
Run bypass-utility to disable authentication.
Use SP Flash Tool to flash 7.3.1.0
If it doesn't boot due to anti-rollback, run the kamakiri RPMB-downgrade
As for the shorting, there are some options on the back of the board.
Compare with suez (Fire HD 10 - 2017)
Hello, I am looking for firmware version 5.3.6.4 and cannot find it anywhere.
I have searched this forum, freaktab, 4pda and Hong Kong to Australia and back again..... Twice
Would be really great if someone may have. Bin file of this version stashed away on a drive or cloud somewhere (wishful thinking maybe lol).
Thank for your time reading my post.
Regards
Edit ### I managed to get back to factory version of 5.3.2.1 February 2016 Software version by using Rortiz2 Unbrick Giza Method here :
[UNBRICK]Fire HD8 2016 (giza)
This guide is only for the Fire HD8 2016 (codenamed giza.) This will not unlock your tablet, it will clear RPMB and flash original LK,TZ & preloader for restore it from ANTI-ROLLBACK. I am not responsable of any physical damage in your tablet...
forum.xda-developers.com
Although it appears to be daunting (opening the device) it is really easy to do.. Just be gentle is key.
Note to future bricks/Root seekers, anyone wishing to return to a rootable version of firmware can do this method to at least obtain root using @Diplomatics temporary root for a #shell and then obtain bootstrapped supersu
im also try o root this devies like your os
but im dont do i
789mod said:
im also try o root this devies like your os
but im dont do i
Click to expand...
Click to collapse
i got it working . i think you can brick i t and then do what i done in post above if you are on a unrootable version . i was on rooted 5.3.6.4 and deleted too much from priv-app system folder resulting in a brick . then flashed a totally wrong firmware on top of that lol
i unbricked it using the unbrick giza firehd 8 2016 method by Roger and that put me back to factory 5.3.2.1
worth a shot if you have same device, youl have to open your device up and short a resistor , then you can exploit with mtk-su for a temporary shell, then push su files and obtain bootstrapped Supersu binary which results in a more permanent root.
@789mod don't ever pm me again, you want to talk to me and call me out on pm??? If you'd posted your problem in civil manner I would have helped. Fool!
I have a fire stick tv 2nd gen (tank) on firmware 5.2.8.7. Hard to find current info for this device. Attempted unlock from my open media vault server with amonet-tank-v1.2.2.zip and got as far as 'identifying device' part however nothing happens while shorting. it says it cannot find series while i am not shorting. the guide says to 'update' to 5.2.6.9 (an older firmware). I am to understand that you can indeed downgrade this device via adb commands however any links directed to 'amzdigitaldownloads.edgesuite.net' are expired. Am I wasting my time? Is it too late to customize this device?
I also have a (sheldon) and it has been updated beyond 7.2.7.3. Are there any options left to return to that firmware? Also if I purchase a new one to manually update am I also out of luck considering the first stept before registration is updating?
I am obsessively researching this and wasting a lot of time out of fear for breaking rules or ridicule. Any help would be an asset. Tutorials often assume a lot. Thanks in advance.
rocklite said:
the guide says to 'update' to 5.2.6.9 (an older firmware).
Click to expand...
Click to collapse
the guide doesn't say downgrade This update was a thing from the early days... forget about it.
rocklite said:
Is it too late to customize this device?
Click to expand...
Click to collapse
The later tank sticks got a factory burned efuse to block the exploit. If you can't see a mediatek phone device in lsusb while shorted, the unlock won't work for your stick
rocklite said:
I also have a (sheldon) and it has been updated beyond 7.2.7.3. Are there any options left to return to that firmware?
Click to expand...
Click to collapse
Option is to sell... and buy another (vulnerable) one...
i will have to do my best to find one. thank you very much. you have saved me a lot of time.
i was lucky enough to get my hands on a 'Fire TV Stick Lite' w/ 'Fire OS 7.2.4.2 (PS7242/2897)'. how do i get 7.2.7.3 on here? (sorry for being a total noob.)