yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S7 Questions & Answers] Illogi.xbone:
Just the messenger lol. But honestly I can live without root. If I desperately needed root I wouldn't have bought a Samsung device as they are not the best for it. If you NEED root next time look more towards Nexus Phones, now Pixel and WAY over priced imo. Or research which phones have good root with an unlockable BL. For that I would stray from VZW branded devices and buy an unlocked version from the manufacturer that is compatible with VZW

It was used for internal testing for Samsung. This was an early version of the first kernel they had for the S7, I believe and correct me if I am wrong anyone. It was fine tuned and then released but the engineering kernel was left in the dust.
[Verizon Samsung Galaxy S7 Questions & Answers] spearoid:
I don't need to have root. I bought this phone fully expecting to never be able to root it again. After several months of non root usage, it was very nice to enjoy some of the luxuries of a rooted phone again. I'm still torn as to which direction to go. I use the hotspot feature daily, and it works much better now than in the unrooted world for me at least.

I just wanted to see if there was any hope for having the best of both worlds.
[Verizon Samsung Galaxy S7 Questions & Answers] Illogi.xbone:
I was too until the pokemon update lol then I decided no root.
[AT&T Note 7  Questions & Answers] mayonesa01:
From my understanding you can add pictures by pressing on a picture and checking it. Then on the settings there should be a "move to secure folder" but i dont have that.

College is the last thing i have
[AT&T Note 7  Questions & Answers] illa215:
Go to your secure folder settings and uncheck "Hide Secure Folder"
[Verizon Note 7  Guides, News, & Discussion] Mibuix0r:
I'm not sure how seriously to take this because the phone was dropped and was only smoking but here is the article:

http://www.theverge.com/2016/10/5/1...te-7-fire-replacement-plane-battery-southwest
[Verizon Note 7  Guides, News, & Discussion] dottat:
Dupe thread.
[Verizon Note 7  Guides, News, & Discussion] the Doctor:
Please search before posting and do not create duplicate threads :good::good:

THREAD CLOSED
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Nooooxa:
Hi, I'm fairly new to custom ROMs and would just like some help with finding some. I was looking over Dirty Unicorns but had no clue on how to install it, or if it was even usable on my phone's model (SM-G928T). Any help or suggestions will be appreciated thank you!
[Fire HD 6 and 7 Android Development] powerpoint45:
Testers wanted: Anyone who uses this method, let me know if you can access stock recovery after this method.

Summery

Thanks to the amazing work by our active member @bibikalka, a method was found to unbrick these devices Thread link here. The method he found was slightly tedious for some people, so I've decided to put together a Linux iso that you can boot into on your computer with everything you need to get your device running again. It uses the same methods proposed but makes things easier. This comes with all the necessary drivers, scripts to do everything you need, all the img files needed to flash, a hex editor for advanced users, and more. Before the scripts included in this OS, determining the option (A, B, or C) to take in order to unbrick the device required .part files to be evaluated manually. Now with the custom script, it can quickly evaluate what option to take.

Video Instructions

Brief Instructions

1. Download the Linux iso:

Linux ISO

2. Burn the iso to a USB drive or cd

3. Boot into the operating system

4. Type "root" at the login prompt

5. Right click on the desktop and choose file manager. Go to "aftv2-tools" folder

6. Right click on file manager and press "open in terminal"

7. From device turned off, enter command "./handshake.py", then plug in device. You may need to do this a couple times to get a connection. Try pressing volume keys & power etc to get it connected. See video if you have problems

8. After handshake is complete, run "./reader.sh"

9. After all addresses are read in, run "./determineOption.sh". You should get back a result of A, B, or C

10. Depending on the option returned (A,B,or C), run "./readerSpecialOptionA.sh", "./readerSpecialOptionB.sh", or "./readerSpecialOptionC.sh". This is an optional step but may be useful if you want to back up part files or their were no options available. Back up part files to a usb drive if you want to be safe.

11. Now the actual unbricking. Run "./unbrickOptionA.sh", "./unbrickOptionB.sh", or "./unbrickOptionA.sh" depending on your option. This can take about 40 minutes

12. hold volume up and run "./complete.sh" at the same time to get into TWRP

13. boot into your default operating system on your computer

BE VERY CAREFUL FROM NOW ON

13. We will be installing Fire OS 5.3.1. If you are not installing this ROM, make sure you know what you are doing. Download the ROM:

update-kindle-20.5.5.2_user_552153420.bin

14. Download 5.4.1_1133_stock_recovery_uboot.zip: 5.4.1_1133_stock_recovery_uboot.zip. Without this you could turn your device into a paperweight. This installs stock recovery and a uboot version that MUST be installed. This file was taken from the thread here: how-to-upgrade-to-lollipop-root-gapps

15. Rename the ROM extension from .bin to .zip

16. Transfer the two files to the Fire

17. Do a factory reset. Flash the ROM and uboot&recovery file

18. Reboot! Your device should now be working. It will take about 15 mins to boot up.

Big thanks to @bibikalka for helping work everything out and for the initial unbrick method.

Edit 10/13/21: Fixed Google Drive Link
[Fire HD 6 and 7 Android Development] powerpoint45:
Linux ISO Changelog

Updated 10/5/16:

*Optomized scripts

*Added "complete.sh" This reboots the device

Updated 9/27/16:

*Added script to auto-detect which unbrick option to use (determineOption.sh)

*Added scripts to write img files to correct addresses ( unbrickOptionA.sh, unbrickOptionB.sh, and unbrickOptionC.sh)

*Added scripts to read in and label part files (readerSpecialOptionA.sh, readerSpecialOptionB.sh, and readerSpecialOptionC.sh)

*Nemo open in terminal fixed

*.part files set to open with ghex by default

Updated 9/24/16:

*Nemo as default file manager

*Updated html page with instructions from forum
[Fire HD 6 and 7 Android Development] gascomm:
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.

feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for [MENTION=4469251]powerpoint45[/MENTION] for an excellent & well thought through tool and walkthrough. special mention also goes out to [MENTION=6680544]bibikalka[/MENTION]
[Fire HD 6 and 7 Android Development] powerpoint45:
great to hear! I hope everything works for you! After you get everything done, can you check if you can get into recovery.
[Fire HD 6 and 7 Android Development] gascomm:
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!

i tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.

I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
[Fire HD 6 and 7 Android Development] powerpoint45:
Good to hear everything is working. Ya TWRP does not work with 5.x bootloader. Good to hear you can get into stock recovery because I had some incidents where I could not get into it. Thanks for responding. The only custom ROM ATM is CM13.
[Fire HD 6 and 7 Android Development] gascomm:
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..

I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?

I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.

cheers.
[Fire HD 6 and 7 Android Development] powerpoint45:
I meant to say CM11. This guide is probably one of the best http://xdaforums.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page1

This is a bit older one: http://xdaforums.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351/page1

In order to have TWRP, you must have a 4.x bootloader so CM11 would work with it.
[Fire HD 6 and 7 Android Development] PRInCEI7:
Thank you

I have a question I can work downgrade from 5.3.1 to 4.5.3

I'm currently on version 5.3.1
[Fire HD 6 and 7 Android Development] powerpoint45:
yes you should be fine doing that
[Fire HD 6 and 7 Android Development] PRInCEI7:
Unfortunately, did not respond

I worked

MacBook-Air-2:ROOT IP$ ./handshake.py

Waiting for preloader...

Found port = /dev/cu.usbmodem1420

Handshake complete!

In the second step does not respond to the order ./reader.sh

Also tried

/.read_mmc.py 0x0000000 0x1000 0x0000000.part

Does not respond

By the way tried way on more than one device

And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result

MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3

Is there a solution to my problem

[/SIZE]
[Fire HD 6 and 7 Android Development] gascomm:
[MENTION=4469251]powerpoint45[/MENTION] thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
[Fire HD 6 and 7 Android Development] powerpoint45:
sweet!!!
[Fire HD 6 and 7 Android Development] nai1ed:
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
[Fire HD 6 and 7 Android Development] powerpoint45:
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
[Fire HD 6 and 7 Android Development] draxie:
Confused

First you say it should be OK to downgrade:

Although, it's unclear how, since reports indicate that sideloading older

firmware bricks the device (or, does that only apply to 5.x?).

Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:

[root@archbang aftv2-tools]# ./handshake.py
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
[root@archbang aftv2-tools]# ./reader.sh
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^Z
[1]+ Stopped ./reader.sh
[root@archbang aftv2-tools]# kill %1
[root@archbang aftv2-tools]#
[1]+ Terminated ./reader.sh
[root@archbang aftv2-tools]#

The above is for a 4th gen HD7 with this device showing in 'lsusb':

Bus 001 Device 006: ID 0e8d:3000 MediaTek Inc.

BTW, are we sure that this is *disabled* as opposed to _tweaked_?

(e.g. by changing the protocol slightly by, say, requiring an extra byte

or two "confirmation" before execution? has anyone bothered reversing

the bootloader? [Please excuse my ignorance, but would this be handled

by UBOOT, TEE1, or some other component?])

So, what's the current best option for 5.3.1?

---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------

OK. So, I found this post by [MENTION=3411776]zeroepoch[/MENTION],

which makes it very clear that said exercise has been performed for the AFTV2...

No reason to believe that this would be different for the Fire HD7...
[Fire HD 6 and 7 Android Development] powerpoint45:
My understanding is that you only need to worry about bricking if You are downgrading to another lollypop ROM. We found out that the device has a fuse that is set in later lollypop ROMs where it will check against the current version. But this check only seems to be on lollipop ROM's. As for the aftv2 protocol, you might be right but I don't know enough about that yet to know. Currently we have no unbrick method for latest bootloader. If you can get into recovery then you could sideload but most can't get into recovery during brick.
[Fire HD 6 and 7 Android Development] mrthtung:
I've followed the steps but not into twrp, only screen amazon and reset. I'm not good at English
[Fire HD 6 and 7 Android Development] kingwill101:
error trying to unbrick hd6

[root@archbang aftv2-tools]# ./complete.sh

1: 0xd1

4: 0x00 0x00 0x00 0x00

4: 0x00 0x00 0x00 0x01

Traceback (most recent call last):

File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read

'device reports readiness to read but returned no data '

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./read32.py", line 69, in <module>

ret = read32(addr, size)

File "./read32.py", line 45, in read32

print_hex_byte(dev.read(2)) # status

File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read

raise SerialException('read failed: {}'.format(e))

serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

[root@archbang aftv2-tools]#
[Fire HD 6 and 7 Android Development] PRInCEI7:
You are on any version.

You can access to recovery now
[Fire HD 6 and 7 Android Development] kingwill101:
not sure i get what should be done now. the device went to the amazon logo at first and was in a loop, now im not able to go that far anymore
[Fire HD 6 and 7 Android Development] jpr9845:
I have burned the iso to a USB drive and cannot get my PC to boot up on it. Any suggestions? I have tried three different programs to burn the ISO to USB and have used the option Windows bootable and just bootable to no avail. I have my PC setup to boot 1st from USB Drive/storage but apparently my Windows 10 machine just does not see it.... any HELP would be appreciated.

I even tried holding down shift & restarted my system, this gave me the option to boot from my USB device, did not boot. I must be doing something wrong in the creation of the USB drive.
[Fire HD 6 and 7 Android Development] PRInCEI7:
It does not need to burn the iso

You can work directly from Windows or Mac OS.
[Fire HD 6 and 7 Android Development] jpr9845:
how do I use the Linux ISO on my Windows PC? I mean If I am not booting into a different OS (ie. linux) then how do I use the ISO to unbrick my tablet?
[Fire HD 6 and 7 Android Development] PRInCEI7:
if you have windows Pc

python

https://www.python.org

and

http://www.mediafire.com/file/lps7qrz7d47bqqr/aftv2-tools.zip

or you can used LinuxLive USB Creator

for Linux ISO

http://www.linuxliveusb.com
[Fire HD 6 and 7 Android Development] jpr9845:
Too Novice

The Python route just was really over my head. I tried the LixuxLive USB Creator - selected my USB Drive (a 32GB OTG drive) and then chose your ISO as the file.

When I go to my Windows Explorer and get open the drive it has a folder (Portable-VirtualBox) and 2 .exe files VirtualBox.exe and Virtualize_This_Key.exe

When I select the latter, a box appears that says Portable VirtualBox and then it disappears and a little dialog box comes up saying Exit Portable VirtualBox Please do not unplug your key !

Nothing else occurs, am I doing something wrong? Do I need to install VirtualBox on my computer?
[Fire HD 6 and 7 Android Development] carderel:
I've followed this and it works great! Thanks for the ISO everything works fine except for when I run the ./complete.sh it throws some error codes (I will get them shortly) but I am still able to get to TWRP which is where i run into problems. I wiped the cache and dalvik, then do a normal reset. I install the update-kindle-20.5.5.2_user_552153420.zip and the 5.4.1_1133_stock_recovery_uboot.zip attached to this thread, then restart. It never reboots. Just sits at the blank unactive screen. What am I doing wrong?
[Fire HD 6 and 7 Android Development] carderel:
I don't have Ethernet connected to the computer I'm using the LiveUSB on so I had to just take a photo of the error.

I realized its the same error on page 2 so all is good.

I retried following your method in the video and still no go. When I have it hooked to the computer I can hear it connecting and disconnecting which I believe is the MT65xx Preloader cycling.
[Fire HD 6 and 7 Android Development] PRInCEI7:
use. this program UNetbootin

Burn the Linux ISO to a USB drive

And then restart the machine and entered the BIOS

and Choose Boot from USB

It will work.

You do not need to VirtualBox
[Fire HD 6 and 7 Android Development] carderel:
***UPDATE***

After running the scripts again and loading TWRP i was able ADB sideload the latest version from Amazon and at least get the tablet working again.
[Fire HD 6 and 7 Android Development] lynnux:
Thanks! My bricked HD 7 was sitting in a drawer for the past year, and I'd given up on it. Came back here to see if some genius had come up with an advanced unbricking method, and here it was. Worked like a charm. One dicey moment at the end when it didn't boot into twrp right away, it finally did after a few tries.

Bought your app as a donation. Many thanks for the time you put into this and for explaining it so clearly.
[Fire HD 6 and 7 Android Development] jpr9845:
Fixed my brick

My Fire came with 4.4.2 on it and I got it stuck in a boot loop trying to install CM11. The LixuxISO tool not only got it running again it got it running on 5.3.1.

Prior to this the update screen said it was up to date at 4.4.2. Very nice, thanx for your work!
[Fire HD 6 and 7 Android Development] Cartman971:
>> Excuse my english please, I'm french !

Does not work for me... Nothing happens when I run "./reader.sh".
[Fire HD 6 and 7 Android Development] Drevenu:
How long does reader.sh typically runs for? Running for about an 30 min now in a VM (Fire HD 7 8 Gb)
[Fire HD 6 and 7 Android Development] Hariiiii:
Was fooling around with bootloaders and soft bricked my device. The ISO worked flawlessly. Option A for me.
[Fire HD 6 and 7 Android Development] crickyo:
HI , Cant say thanks enough this is awesome!!!, i bought a hd 6 and started updating with root , got to the twrp and rebooted instead of installing the zips accidentally.

Tried the other guide including trying to figure out python faulty windows updates..... somehow id missed your guide and set about it straight away booted up the iso on a spare computer and followed the video its a great guide , easy to follow and it fixed my tablet :D now its just running through the set up :D

Ive 14 open tabs just to get this far if only id seen this first lol

Thanks again!!!!
[Fire HD 6 and 7 Android Development] Nick11358:
Thanks!

This worked well, i appreciate the work and effort that went into making this!
[Fire HD 6 and 7 Android Development] eric2112:
Two questions:

1.) Do I need to use a factory fastboot cable for this?

2.) Should the device be in Fastboot mode for the handshake?

Been fooling around with a few utils for days to no avail.

Thanks ~E
[Fire HD 6 and 7 Android Development] Killa8:
No need for factory cable

Read the instructions again concerning the handshake, it says that the devices simply need to be plugged in and the script launched, no fastboot whatsoever needed
[Fire HD 6 and 7 Android Development] ieatabiscuit:
Same here

Update: Nvm, I figured it out. The answer is on page 2.
[Fire HD 6 and 7 Android Development] Jrhotrod:
I have had a bricked Fire HD 6 for months now, and didn't even want to try bibikalka's original method with stuff that looked WAY too complex! Anyway, I just installed the ZIPs . Thank you to Powerpoint45 for such an easy, comprehensive, and noob-friendly guide!
[Fire HD 6 and 7 Android Development] davarman:
Dear Powerpoint 45. . The method fix my Fire HD 7 4th generation. A summary here:

1. The kindle bricked after I tried to install FireOS 5.3 from a rooted device with CM11

2. The kindle was completed death. Not turning on at all

3. I create the Linux USB in windows 10 from a Surface Pro 3. I couldn't get the USB boot in the surface, so I changed to an ASUS laptop and the system booted perfect.

4. I followed the instructions. I had to press the volumen down button to be recognized by the PC.

5. The procedure stopped during the unbrick process and I got an error. The Kindle now was showing just the Amazon logo. I was happy that it was turning on again.

6. I decided to make the procedure again and this time the TWRP was installed with not problem, and the procedure finished with any problem.

Thanks so much for your contribution
[Fire HD 6 and 7 Android Development] tlacuache:
Thank you so much for all of your work on this. It's great.

EDIT: I was able to get it working by leaving the 4.5.3 bootloader in place and restoring a backup I'd made from TWRP previously after I downgraded. Thanks again!

I've been able to go through these steps several times but I'm getting stuck on the VERY last step. The handshake, read, and unbrick scripts all run correctly. I am able to get it into TWRP. I flash the ROM and bootloader/recovery zips, then select reboot.

But then I just go back to the black screen. I'm thinking it must not be the right bootloader. If I start all the way over at step 1 I can go through everything again and get back to TWRP. Any ideas?
[Fire HD 6 and 7 Android Development] Jamalama:
Thought you should know

previously before the brick i had downgraded from Fire OS 5.3.1.1 (With this problem it is basicly the same as 5.3.1 :o )

To 4.5.3 now i used exactly what u used and did what you said, however i found this after bricking my device with twrp for the unbricking process (ironic :laugh: ) and then while doing your unbrick again and i saw this in the TUT

Update3.5 : Updates for 5.3.1 !!! Please use 5.5.2_1534_stock_recovery_uboot.zip if you downgraded from stock FireOS 5.3.1 to 4.5.3 for rooting, meaning that you now have 5.3.1 bootloaders

so im trying that now instead of your recovery uboot

other people might need to know this because this could become a common problem

i will let you know if it works

[MENTION=4469251]powerpoint45[/MENTION]
[Fire HD 6 and 7 Android Development] powerpoint45:
I don't recommend using that one because if I recall correctly that is the newer one that breaks the ability to use this unbrick method. Meaning, if you brick your device again after that then your device is hard bricked and unrecoverable. Using the one I mention does not break the ability to use this unbrick method so you can always recovery it again.