yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 Q&A, Help & Troubleshooting] jed_thephoenix:
Hi,

I have the SM-T310 Galaxy Tab 3 8.0 variant with stock android 4.4.2 and was rooted with Xposed Framework installed. I need some help and advice on how to fix it, if possible, or whether it's beyond fixing.

A few days ago my tablet was working fine and there was no indication of anything wrong. I put it on charge as the battery was getting low from watching YouTube. I came back to it a couple of hours later to find it stuck on the Samsung boot screen, but was able to get into Odin mode after some time (I tried to get into recovery but it wouldn't work). It had some trouble being recognised in the computer at first. I tried flashing the stock ROM again several times, but it failed each time with no useful error code.

I then tried rebooting which came up with a firmware upgrade error and asked me to recover it with Kies. I tried that to no avail. Firstly tried with Kies 3 which said the device wasn't compatible, even though I have plugged it into Kies before and it has been recognised and worked fine. I then tried the older Kies which wouldn't work either. Then, I opened Odin again and found it was being seen even with this error screen instead of Odin mode. I tried flashing again but still didn't work and had a COM port error instead. I did make sure that Kies was completely shut before attempting to flash. I even attempted to perform a proper Nand erase and repartition but that also didn't work and failed.

I couldn't do anymore after that due to it being so late at night, and had no choice but to let the battery drain. It now won't power on at all, nor does it appear to be charging, although there is something under a metal plate (not entirely sure what it is but possibly the memory or CPU chip), that gets warm when plugged in and slightly warmer when trying to power it on.

I did try a different computer, different cables and different operating systems to ensure none of those were contributing.

I have also tried to use ADB to get the device to be 'seen' but that didn't work either (used 'adb devices' command), but I'm new to ADB so don't understand it too well yet.

I appreciate any help given and hope I've given enough detail. Thank-you for your time,

Jed.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] wbb1:
If all else fails try this

https://youtu.be/m2VJ_VRIRSI?t=201

Remove back cover and reattach the battery. Worked for me when my tablet wouldnt charge/turn on.

Maybe after this you can get it to be read by the computer.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] jed_thephoenix:
I tried this to no avail, with multiple chargers and leads. Thanks for the suggestion though.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] CodeJACK:
I'm in the same boat myself and have not been able to get the tablet to power on at all.

Tried disconnecting the battery

Purchased a new charge/usb port

Any number of key combination tried for extended periods of time.

I think the tablet has officially eaten the dust.

I didn't even use it all that much. Only for ROMing and Readly.

Oh well...
[Galaxy Tab 3 Q&A, Help & Troubleshooting] jed_thephoenix:
Yeah, I've lobbed everything I had for it, just gotta get a hammer and smash it up. It died with personal data on it and I'd rather not take any chances.
[Verizon LG G4] Funnyfish8684:
I have been searching all over to find out if it's possible to root the Verizon lg g4 on the latest update...some say yes and some say no....I basically want access to my file system and to change fonts and such....not worried about roms unless it is possible to get these on the newest update. Please let me know for sure if its possible. Thanks in advance ...

Tiffany
[Verizon LG G4] Funnyfish8684:
264 views and no one can tell me?
[Verizon LG G4] ninjazx:
13B (Lollipop) is rootable. MM is not
[Verizon LG G4] LASERWOLF452:
Www.youtube.com/lasertechcomputers

It has 13b root method. Screw mm there is no root for mm. If there was you see alot of post here on xda about it
[Desire HD Q&A, Help & Troubleshooting] aliakil:
Hi,

Anyone can help me to return to stock???

thanks all :good:
[Fire HD 6 and 7 Android Development] kirito9:
I have a bricked Fire HD 6 (4th Gen) and would like to try this, but this wasn't my device. I'm just trying to help a friend. I'm not even sure what android/amazon version it was on before bricked. All he told me was he updated to 4.5.5 and then it bricked.

I will probably edit this as I get more info from him. Good thing you've started here [MENTION=6680544]bibikalka[/MENTION] ;)
[Fire HD 6 and 7 Android Development] bibikalka:
OK, the key data are the addresses. The info is from these posts :

http://xdaforums.com/fire-hd/development/uart-port-fire-hd6-t2991474 (thank you [MENTION=4469251]powerpoint45[/MENTION] !!!)

http://xdaforums.com/fire-hd/help/internal-memory-structure-hidden-t3122246

So these are hex values for 512 byte sectors :

[PART] 1: 00000100 00000040 'PRO_INFO'
[PART] 2: 00002000 00000800 'PMT'
[PART] 3: 00002800 00002800 'TEE1'
[PART] 4: 00002800 00005000 'TEE2'
[PART] 5: 00000400 00007800 'UBOOT'
[PART] 6: 00004000 00007C00 'boot'
[PART] 7: 00004000 0000BC00 'recovery'
[PART] 8: 00000800 0000FC00 'KB'
[PART] 9: 00000800 00010400 'DKB'
[PART] 10: 00000400 00010C00 'MISC'
[PART] 11: 00008000 00011000 'persisbackup'
[PART] 12: 00258000 00019000 'system'
[PART] 13: 001B8000 00271000 'cache'
[PART] 14: 018F3FDF 00429000 'userdata'

This leads to :

Note, these are not correct, see post #1

Part Address Length

TEE1 0x0500000 0x0500000

UBOOT 0x0F00000 0x0080000

recovery 0x1780000 0x0800000

And, these commands should save the partitions (if my math is correct !!!) :

./read_mmc.py $((0x0500000)) $((0x0500000)) tee1.part

./read_mmc.py $((0x0F00000)) $((0x0080000)) uboot.part

./read_mmc.py $((0x1780000)) $((0x0800000)) recovery.part

One may read only the first few blocks, and see if the addresses are good.
[Fire HD 6 and 7 Android Development] Gimzie:
Wow, nice to see that more progress has been made! The thread title states that this guide is for if you downgraded to an older lollipop version, but would it also work if you upgraded to 4.5.3 - 4.5.5.1? That kindle that I bricked was sent to Amazon and they sent back a refurbished one. I would be happy to post the addresses later though! :D
[Fire HD 6 and 7 Android Development] bibikalka:
Yahoo !!! I could try the steps, and everything seems to be working! See post #1 for updates.

Fortunately, I did not have to unbrick anything, so we'll wait for reports where this is actually useful.
[Fire HD 6 and 7 Android Development] hwmod:
Happy to hear this method work on the Fire HD 7 !!!

As i said in a previous post of the OT it seems this method could work on the entire line of Mediatek new SoCs.

We have to say thanks to [MENTION=3411776]zeroepoch[/MENTION] for these Python helpers, they are really useful and will save many "bricked" devices.

.:HWMOD:.
[Fire HD 6 and 7 Android Development] Liz-kawa:
Hi,I'm Japanese. Sorry,I,m not good at English

I instlled mtk-drivers to my PC.

(http://xdaforums.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033)

I tried

1. handshake.py is OK

2. read_mmc.py 0x0F00000 0x1000 tee1.part

read_mmc.py 0x1400000 0x1000 tee2.part

read_mmc.py 0x1900000 0x1000 uboot.part

read_mmc.py 0x1980000 0x1000 boot.part

read_mmc.py 0x2180000 0x1000 recovery.part

is OK

3.write_mmc.py 0x0F00000 453_tee1.img is OK about 10min

write_mmc.py 0x1900000 453_uboot.img is OK about 1min

write_mmc.py 0x2180000 453_twrp.img is OK about 15min

4.read_mmc.py 0x1400000 0x1000 tee2.part is OK

5.write_mmc.py 0x1400000 tee2.part is OK

6. read32.py 0 1

Log is this

1: 0xd1

4: 0x00 0x00 0x00 0x00

4: 0x00 0x00 0x00 0x01

0:

<===

Traceback (most recent call last):

File "D:\aftv2-tools\read32.py", line 69, in <module>

ret = read32(addr, size)

File "D:\aftv2-tools\read32.py", line 49, in read32

data = dev.read(4)

File "C:\Python34\lib\site-packages\serial\serialwin32.py", line 269, in read

raise SerialException('call to ClearCommError failed')

serial.serialutil.SerialException: call to ClearCommError failed

I can't unbrick yet.

HD6 stuck on black screen...

Please tell me the step-by-step instructions！
[Fire HD 6 and 7 Android Development] bibikalka:
First, please hold "Pwr" button for a really long time, like 1 minute. Try it a few times, perhaps, it'll come up?

Then, please do this :

read_mmc.py 0x0F00000 0x1000 tee1.part2

read_mmc.py 0x1900000 0x1000 uboot.part2

read_mmc.py 0x2180000 0x1000 recovery.part2

Then make a *zip of these 3 files (*.part2), and upload it here. I want to see if the new images were indeed written to the Fire.
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

Then make a *zip of these 3 files (*.part2), and upload it here. I want to see if the new images were indeed written to the Fire.[/QUOTE]

I ｔｒｙ your advice. I attached here.
[Fire HD 6 and 7 Android Development] bibikalka:
If you still have old pieces of partitions from the commands below that you ran last time, please zip them and post them here (all *.part files):

read_mmc.py 0x0F00000 0x1000 tee1.part

read_mmc.py 0x1400000 0x1000 tee2.part

read_mmc.py 0x1900000 0x1000 uboot.part

read_mmc.py 0x1980000 0x1000 boot.part

read_mmc.py 0x2180000 0x1000 recovery.part

I want to make sure that the addresses are the same on your Fire, and that these *part files look OK.

Your short pieces of partitions look OK (part2 files you've uploaded). Just to be double sure, try to write them again (unlikely to work, but hey, it's simple!) :

(First, delete lastaddr.txt file in the aftv2-tools folder if it's there)

write_mmc.py 0x0F00000 453_tee1.img

write_mmc.py 0x1400000 453_tee1.img

write_mmc.py 0x1900000 453_uboot.img

write_mmc.py 0x2180000 453_twrp.img

(the address @ 0x1400000 will also have TEE2 updated)

Then hold Power button for 1 min several times.

If we still cannot get this to work, it'd be probably helpful to get the UART port output. This requires more than software, but would provide some useful diagnostics :

http://xdaforums.com/fire-hd/development/uart-port-fire-hd6-t2991474
[Fire HD 6 and 7 Android Development] Liz-kawa:
Thank you for your analysis. I will attach the necessary files. For the second half, I will try later.
[Fire HD 6 and 7 Android Development] bibikalka:
OK, for some reason your tee2.part looks like junk. I wonder how it happened. Can the write command be failing ? Or Tee1 file is too long ? Still, it should not matter ...

In the list of your commands you first wrote to TEE1, and then read from TEE2 again. So could the 1st write command screw up the TEE2 address range ?

Update: I've removed TEE2 address from the new instructions, I am not sure what's going on there ...
[Fire HD 6 and 7 Android Development] Liz-kawa:
I ran your advice twice, but my machine can not be recovered after all.

Thank you for your help.
[Fire HD 6 and 7 Android Development] kirito9:
[MENTION=6680544]bibikalka[/MENTION] I've started trying to unbrick the Fire HD 6 that I have here but I'm having a bit of trouble with the first part...handshake. I know you need the preloader drivers which I installed and do have (see attached images) but I'm not sure if there is a different way of installing the preloader drivers for Amazon.

I tried the handshake with my other MTK device to make sure that I do indeed have the preloader drivers but it's was working (see attached images).

Any help you can provide would be great.

EDIT: I solved it.

What I did was use "mdmcpq.inf" or "usb2ser_win7.inf" (I'm sorry, but I'm not sure which because I was just trying all) from the win_drivers of the aftv2-tools folder. I right clicked on the MT65XX preloader and manually installed the driver by selecting the .inf file previously mentioned.
[Fire HD 6 and 7 Android Development] bibikalka:
Are you still around ???

I want to understand why your TEE2 looks nothing like what it should be. Do you mind running a few commands for me ? Thanks!
[Fire HD 6 and 7 Android Development] Liz-kawa:
It is still there. I would like to respond to your wish.
[Fire HD 6 and 7 Android Development] bibikalka:
OK, please read this data:

read_mmc.py 0x0A00000 0x8000 00.part3

read_mmc.py 0x0A08000 0x1000 pro_info.part3

read_mmc.py 0x0B00000 0x1000 pmt.part3

read_mmc.py 0x1400000 0x1000 tee2.part3

read_mmc.py 0x13FF000 0x1000 tee2_pre.part3

Then zip all these *part3 files, and post them here. I still cannot figure out why your TEE2 is full of junk ...

By the way, do you have an 8 Gb or 16 Gb Fire ?

Update :

It looks like one could read the UART log via the micro-USB connector :

http://xdaforums.com/showpost.php?p=65585385&postcount=16

http://xdaforums.com/showpost.php?p=65587440&postcount=17

http://xdaforums.com/showpost.php?p=65588189&postcount=18

We really need to get this for a bricked Fire HD, otherwise it's all work in the dark ... Unfortunately, this route still requires a bit of special hardware ...
[Fire HD 6 and 7 Android Development] Liz-kawa:
Now late, but it will send the necessary files.

Before you erase(#10), I ran once "write_mmc.py 0x1400000 453_tee1.img".

I have 8GB　Fire.

Thank you for your analysis and help.
[Fire HD 6 and 7 Android Development] bibikalka:
So it seems that there is garbage data in many key partitions. So either your addresses are different than mine. Or, the whole bunch of partitions got somehow corrupted. At this point it's not possible to tell ... Perhaps, we'll get another data point soon, and then we can revisit this issue.

It does not seem like there could be much progress without being able to read the UART logs via :

http://xdaforums.com/showpost.php?p=65585385&postcount=16

http://xdaforums.com/showpost.php?p=65587440&postcount=17

http://xdaforums.com/showpost.php?p=65588189&postcount=18

Btw, it seems like it'd be a $3-4 budget (and ~ 1 month of wait), to get the materials to build the serial port reader from eBay. An easy route is to hook up :

1) USB OTG cable to Fire, converting 5 pin micro USB to the regular USB (female)

2) USB (male) to serial (4 split pins)

3) FT232RL USB-to-TTL-Serial adapter hooked up to 2)

4) another male-male USB cable connecting 3) to a computer
[Fire HD 6 and 7 Android Development] bibikalka:
OK, I think I may have good news for you. I've tried my 2nd Fire HD (with Lollipop), and the addresses appear different ! Please run these commands, zip the files, and post them here :

read_mmc.py 0x0C80000 0x1000 tee1.part

read_mmc.py 0x1180000 0x1000 tee2.part

read_mmc.py 0x1680000 0x1000 uboot.part

read_mmc.py 0x1700000 0x1000 boot.part

read_mmc.py 0x1F00000 0x1000 recovery.part

If the new addresses are correct, we may be able to still unbrick !!! But before we write anything, let's make sure that the addresses are correct.

Update : I think KB and DKB partitions got destroyed with the earlier attempts, so if the unbrick does not work, I'll provide you with new ones to overwrite KB and DKB.
[Fire HD 6 and 7 Android Development] bibikalka:
Do you hear any USB clicks when you plug in your dead Fire ? Basically, does Windows try to load the drivers, etc ? What you describe is very weird, at least you should get something. I suspect you don't have the correct drivers. Use USBDeView to remove whatever you have installed for the device, and see if it asks you for the drivers again.
[Fire HD 6 and 7 Android Development] gascomm:
no, never heard any clicks on connecting the usb cable. the MT65preloader shows as present briefly on device manager but has never asked for a driver installation. I've right-clicked the .inf files as instructed and installed that way. from device manager the fire isn't connected long enough to allow installation through the update driver option.

the bootloop goes as far as the silver amazon logo & then reboots again & again & again .... I've deleted (with usbdeview) previous driver installations each time I've installed fresh drivers.
[Fire HD 6 and 7 Android Development] diskopat:
[MENTION=3961705]gascomm[/MENTION]

Use ubuntu :D i had same issue and passed with using ubuntu
[Fire HD 6 and 7 Android Development] FumundaSaq:
New here and trying to unbrick. No success.

Hello, I have recently bricked my kindle fire hd 6 4th gen because I didn't do enough research before hand. Now I am trying to unbrick it. I have tried most of what I can find with no results. My fire is currently only booting to the Amazon logo, then rebooting 4 or 5 seconds later and repeating that sequence. I have what was sold on amazon as a fastboot cable but since it doesn't do anything different with or without that "fastboot cable" I don't know that it really is one. I have also tried this process http://xdaforums.com/showthread.php?t=3405797 . I have gotten as far as running handshake.py and seeing waiting for preloader.... but cant go any farther. The kindle is viewed under device manager in windows 10 as android composite adb device, so I got the drivers installed correctly, finally. Followed the instructions for installing python 3.5 and then installed pyserial via cmd and then ran handshake.py from the aftv2 directory. I cannot go any farther than waiting for preloader though. My kindle just goes round and round with the amazon logo and the windows sounds when it connects and disconnects and device manager shows it connect and disconnect but the waiting for preloader doesn't ever find it.

What now?
[Fire HD 6 and 7 Android Development] my2k2zx2:
I'm also having the same issue as the post above. Windows 7 shows the MT65XX entry for about 2 seconds and then disappears and comes back as the composite adb. I've also set up a ubuntu laptop and no luck there either. Both show "waiting for preloader" but nothing more ever happens.
[Fire HD 6 and 7 Android Development] bibikalka:
Unfortunately, the drivers under Windows are very fussy. And there is no known solution, just a bunch of semi-random re-installs which could eventually fix it.

A few points here :

1) If you hear clicking sounds from the preloader under Windows, that means somewhere out there you can provide the preloader driver. It's not much, just an inf file, so look this up elsewhere how to handle the quick driver situations

2) If the handshake is waiting, that means that Python/serial are good to go, but the driver is missing

3) Try to turn on hidden devices in "Device manager", see if you can find the preloader, and update the driver for it when it's not connected, so that when you do connect it, it will pick up the corrent driver.

Unfortunately, I don't even have the Windows machines to debug all kinds of crazy driver situations for the unbricking ... My workhorse is still Windows XP, oldies, but goodies ! ;)
[Fire HD 6 and 7 Android Development] my2k2zx2:
I dug out an old XP laptop. I do get it to handshake, but nothing happens with the read_mmc.py commands. I'm typing out the first line from the 1st post and it appears to lock up the command prompt. It does error out if I remove the cable.
[Fire HD 6 and 7 Android Development] bibikalka:
Did you install the VCOM driver ? Does the Fire screen stay dark ? It could also hang immediately, that's why you get no reads. Although often it does read something, and then it hangs ...
[Fire HD 6 and 7 Android Development] my2k2zx2:
I used the MediaTek PreLoader USB VCOM (Android) driver from the link in the first post in the cdc folder. The screen does stay dark.
[Fire HD 6 and 7 Android Development] FumundaSaq:
Same here

I also used the mediatek vcom driver though I am still stuck at an amazon reboot loop. I also don't hear any clicks. The sounds to which I was referring were the windows peripheral connect/disconnect sounds. Just stuck at waiting for preloader. Don't know what to do now.

I have tried installing win 10 drivers from this thread http://xdaforums.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033 but they didn't work either. Even though it was the VCOM drivers. It just created yet another device with a yellow triangle on it in device manager. So I have uninstalled all drivers and now cannot get it to recognize the original driver that I got to work in the first place..... Oh my gosh this is frustrating.

Is there even a realistic chance of unbricking this thing????
[Fire HD 6 and 7 Android Development] bibikalka:
OK, the dark screen is good news, it means it did connect. But the inability to read anything without hanging is not good, so you will probably need another Windows box, or USB Linux ...

Yes, it is realistic to unbrick this, but requires effort with no definite success, and there is a warning to this effect in post #1.

Your situation is less defined, if you see Amazon reboot loop, you did not handshake, so your drivers are not being picked up. Did turning on "hidden devices" in "Device manager" help ? Can you find Fire preloader there ? Can you check the version & update the driver ???
[Fire HD 6 and 7 Android Development] FumundaSaq:
Yes I did turn on hidden devices in device manager but I do not see fire preloader. I only see the mt65xx preloader that I cannot seem to get installed correctly.

Incidentally I do have a Linux mint box that I can use but I'm not very well versed in linux. I have adb and fastboot installed on the linux box but am not sure how to install the drivers for the media tek. Using lsusb I see the media tek for a second and then It's gone. If it's easier to do this via linux I'm gonna need specific instructions cause I'm a noob to linux. Thanks for the patience and help.
[Fire HD 6 and 7 Android Development] bibikalka:
Well, so I actually never did it under Linux myself. Re-read post #1 with the links to the 2 other people, and read their posts. They describe how to do things under Linux. It's actually fairly straightforward, or so it seems ...
[Fire HD 6 and 7 Android Development] FumundaSaq:
Yatta! I decided to try this on my linux box and Success! I finally got the handshake and now I have read from all the blocks. Now what? Im not sure how to compress them and put them up here. Once I figure that out i'll send them to you. The parts dont mean anything to me so Id rather have someone who knows what they are looking at read them.

Ok figured it out and heres the zip.
[Fire HD 6 and 7 Android Development] bibikalka:
Your addresses are in post #1, Option B. LK @ 0x1680000

It seems you already have 4.5.3 bootloaders, so just write TWRP (1 file out of 3), and that should be enough !
[Fire HD 6 and 7 Android Development] FumundaSaq:
Ok thats sounds great. Which files do i need to download then. Sorry if I am making this more difficult then it should be but I dont want to screw this up again. lol

Nevermind. Figured it out again. Sometimes Im slow......

---------- Post added at 10:19 AM ---------- Previous post was at 10:01 AM ----------

This is the error I get trying to write the img. What does this mean?

python write_mmc.py 0x1f00000 453_twrp.img

Traceback (most recent call last):

File "write_mmc.py", line 338, in <module>

size = int(os.path.getsize(sys.argv[2]) / BLOCK_SIZE) # num blocks

File "/usr/lib/python2.7/genericpath.py", line 49, in getsize

return os.stat(filename).st_size

OSError: [Errno 2] No such file or directory: '453_twrp.img'

Sometimes I really am dumb. I forgot a letter... should be 453p_twrp.img......................
[Fire HD 6 and 7 Android Development] my2k2zx2:
Well, I've tried 3 different XP machines, all handshake but hang on the read_mmc command.
[Fire HD 6 and 7 Android Development] Killa8:
Hi, great job tho

But can someone explain to me what to do, cause i'm like 300% lost

I made a successful handshake with the device in Kali linux, but now no idea on what to do, any help?:confused:
[Fire HD 6 and 7 Android Development] bibikalka:
Which specific command ? Please paste it here.

You should copy/paste the commands in post #1 to get the block headers, then zip the files you get, and upload them here.
[Fire HD 6 and 7 Android Development] FumundaSaq:
When trying to send command to disconnect this is what i get:

fumundas-saq aftv2 # python read32.py 0 1

File "read32.py", line 24

print(len(data), end=": ")

^

SyntaxError: invalid syntax

Now what?
[Fire HD 6 and 7 Android Development] Killa8:
Thx for the quick response, i'm gonna do it as fast as possible