A Rather Complex Problem

kstehling79 · Sep 14, 2019

Hello All!
Over the last two weeks I've been struggling to fix my tablet. Other forums have tried to help and the local mobile repair shops wont touch it. Long story short I messed up flashing the Xposed framework got caught in a bootloop and then somehow pretty much erased everything except the Odin Download screen. I've tried flashing many different firmwares (stock, custom and combo) with Odin v3.13.1, v3.12.5 and v3.12.7.... different USB cables, 2 different computers with different versions of Windows and every USB port between them. I've tried with and without the PIT file, with every option checked and unchecked. I've looked at Miracle Box Cracked and Samsung Tool Pro. I've just started with Heimdall.
Basically the end result it the same: No PIT partition, Complete Write Failed, or most recently on Heimdall I recived and Error -1 Failed to Send Data, "Odin" something, or other. I've only been playing with custom Roms and the like for about 3 months. Two weeks ago I didn't know what Ubunto was. I really have no clue what I'm doing at this point. Can anyone help? I have screen shots and there are more details here, https://forum.xda-developers.com/galaxy-tab-a/help/sm-t580-hopeless-t3965037
Thanks in advance for advice.

ocnbrze · Sep 15, 2019

first off welcome to AF!!!!!!!!!!!!!

looks like you have some guys over at xda helping you out. i agree that i think your partition has been corrupted and that i do not think it can be resurrected. i'm not sure what else you can do. if anybody can, though ashyx would be the guy. i have seen him around xda all the time.....dude is legit.

kstehling79 · Sep 15, 2019

Thank you for such a nice welcome

The guys over at XDA have been great, especially to a novice like me. Just an update for ya....I'm not 100% sure what I did, but I got it to boot into the android recovery menu! It's not TWRP recovery, but I'll take it. Now I"m just not sure if I sure install the firmware from the SD card or Odin. Should I try the TWRP file first or just stick to the stock firmware? Do I need to flash with PIT or not? In Odin should I check the repartition option if I use the PIT file? Was if one of the files I tried to flash that got me here? And which one? My head is FULL of questions.. :thinking:

I'll take any guidance one has to offer.

Thanks in advance!

ocnbrze · Sep 15, 2019

If you have a custom recovery, I would make a nandroid backup before u do anything else.

kstehling79 · Sep 15, 2019

ocnbrze said:
If you have a custom recovery, I would make a nandroid backup before u do anything else.

I did have TWRP...but it doesn't seem to be there now.

GameTheory · Sep 15, 2019

kstehling79 said:
Hello All!
Over the last two weeks I've been struggling to fix my tablet. Other forums have tried to help and the local mobile repair shops wont touch it. Long story short I messed up flashing the Xposed framework got caught in a bootloop and then somehow pretty much erased everything except the Odin Download screen. I've tried flashing many different firmwares (stock, custom and combo) with Odin v3.13.1, v3.12.5 and v3.12.7.... different USB cables, 2 different computers with different versions of Windows and every USB port between them. I've tried with and without the PIT file, with every option checked and unchecked. I've looked at Miracle Box Cracked and Samsung Tool Pro. I've just started with Heimdall.
Basically the end result it the same: No PIT partition, Complete Write Failed, or most recently on Heimdall I recived and Error -1 Failed to Send Data, "Odin" something, or other. I've only been playing with custom Roms and the like for about 3 months. Two weeks ago I didn't know what Ubunto was. I really have no clue what I'm doing at this point. Can anyone help? I have screen shots and there are more details here, https://forum.xda-developers.com/galaxy-tab-a/help/sm-t580-hopeless-t3965037
Thanks in advance for advice.

Normally there's 3 ways to flash partitions on an android device. Twrp, fastboot, or some software like odin.

In your case a corrupt partition is not allowing odin to work and you do not have twrp installed.

I don't know if you have access with ADB and if so does this tab have access to fastboot. If fastboot is an option, then your tab can be saved. With fastboot you can just flash twrp from a terminal and then flash any rom in twrp for your tab to get it working.

It would look like this...

Code:

adb reboot bootloader
fastboot flash recovery twrp.img

If nothing mentioned above works or is an option, then your tab has reached its end of days. Sorry.

kstehling79 · Sep 16, 2019

GameTheory said:
Normally there's 3 ways to flash partitions on an android device. Twrp, fastboot, or some software like odin.

In your case a corrupt partition is not allowing odin to work and you do not have twrp installed.

I don't know if you have access with ADB and if so does this tab have access to fastboot. If fastboot is an option, then your tab can be saved. With fastboot you can just flash twrp from a terminal and then flash any rom in twrp for your tab to get it working.

It would look like this...

Code:

adb reboot bootloader fastboot flash recovery twrp.img

If nothing mentioned above works or is an option, then your tab has reached its end of days. Sorry.

I do have access to ADB and Fastboot. And it was recognizing my device. I was mostly uncertain what to try first.. So, if ( and that's a big if) I can get TWRP flashed correctly, I can then use any ROM? I was under the impression it had to be stock.

OK, I'm going to give it a shot and see what happens. I'm still going to make funeral arrangements just in case, LOL.
Thanks for your help!

ocnbrze · Sep 16, 2019

kstehling79 said:
I do have access to ADB and Fastboot. And it was recognizing my device. I was mostly uncertain what to try first.. So, if ( and that's a big if) I can get TWRP flashed correctly, I can then use any ROM? I was under the impression it had to be stock.

OK, I'm going to give it a shot and see what happens. I'm still going to make funeral arrangements just in case, LOL.
Thanks for your help!

not just any rom. the rom needs to be custom made for specifically for your phone model.

you can go here:
https://forum.xda-developers.com/galaxy-tab-a/development

make sure to read the rom's op and verify that it was made for your model number.

after flashing the rom make sure that you use twrp to make a nandroid backup, before doing anything else.

GameTheory · Sep 16, 2019

kstehling79 said:
I do have access to ADB and Fastboot. And it was recognizing my device. I was mostly uncertain what to try first.. So, if ( and that's a big if) I can get TWRP flashed correctly, I can then use any ROM? I was under the impression it had to be stock.

OK, I'm going to give it a shot and see what happens. I'm still going to make funeral arrangements just in case, LOL.
Thanks for your help!

That's great that adb and fastboot work. 9 out of 10 times if those work, a device can be recovered. I skimmed through the xda thread and to my surprise, noone mentioned fastboot to repair your device. No idea why.

Now that we know adb and fastboot work, I can give you more details...

So first power on your tab and connect it to your PC.

1. You'll need to open your command prompt in the directory where you have your twrp file. If I recall, in windows you hold shift and right click the directory, then select open command prompt here.

2. Now check if the tab is being recognized by adb with this command...

Code:

adb devices

If successful, you'll get a serial number output for your tab.

3. Now reboot into the bootloader...

Code:

adb reboot bootloader

4. Flash twrp recovery...

Code:

fastboot flash recovery twrp_filename.img

5. Reboot from bootloader to twrp recovery...

Code:

fastboot reboot recovery

Ideally you should have a rom made for your tab and magisk in an external SD card to flash once in twrp recovery.

If you need more assistance, we'll be here. Feel free to ask.

Cheers

kstehling79 · Sep 17, 2019

ocnbrze said:
not just any rom. the rom needs to custom made for specifically for your phone model.

you can go here:
https://forum.xda-developers.com/galaxy-tab-a/development

make sure to read the rom's op and verify that it was made for your model number.

after flashing the rom make sure that you use twrp to make a nandroid backup, before doing anything else.

LOL, my apologies. I should have worded that better. I meant more like Custom, Stock ect....not that I was going to try a ROM for a different device.

GameTheory said:
That's great that adb and fastboot work. 9 out of 10 times if those work, a device can be recovered. I skimmed through the xda thread and to my surprise, noone mentioned fastboot to repair your device. No idea why.

Now that we know adb and fastboot work, I can give you more details...

So first power on your tab and connect it to your PC.

1. You'll need to open your command prompt in the directory where you have your twrp file. If I recall, in windows you hold shift and right click the directory, then select open command prompt here.

2. Now check if the tab is being recognized by adb with this command...

Code:

adb devices

If successful, you'll get a serial number output for your tab.

3. Now reboot into the bootloader...

Code:

adb reboot bootloader

4. Flash twrp recovery...

Code:

fastboot flash recovery twrp_filename.img

5. Reboot from bootloader to twrp recovery...

Code:

fastboot reboot recovery

Ideally you should have a rom made for your tab and magisk in an external SD card to flash once in twrp recovery.

If you need more assistance, we'll be here. Feel free to ask.

Cheers

Thank you SO much! I've been hesitating to connect to my computer until I got as much info as possible. Now to make a complex situation even more extreme....here's the fun part.
When I first got the bootloop problem, I went to my PC to download the FW from (if I remember right) SamFrew. While waiting for the dl to finish I had my tab plugged into the PC in Odin mode ready to go. My battery, I think, must have drained completely during this time, because it did shut down about 10 minutes before the download finished. I plugged it in and booted it strait to Odin mode, started the flash and that's when my dog disconnected the USB. After that I couldn't get the battery charged enough without it trying to start and very quickly shutting down or doing the loop thing. On my old tablet sort of the same thing happened (the dead battery part) and I just took out the battery until I got a replacement. The old one worked fine just being plugged (hard wired?) into the PC or charger. Is it a possibility that I got that "Could not do normal boot. Invalid Kernel length" error as a result of taking the battery out. Meaning that I've pretty much been barking up the wrong tree this entire time? I also don't get why sometimes the FRP is ON and other times it OFF, without changing the cord or USB port between booting?
Sorry more the longish post and all the questions, I just want to make sure I understand the "why" behind it all. and to make sure I don't do it again

Heres a few screenshots, probably not very helpful, but eh...cant hurt

kstehling79 · Sep 20, 2019

Ok boys and girls, another update.

So, for what ever reason, now my tablet is only recognized when it's in Odin mode or the ADB sideload option from the recovery menu. I checked the drivers for it and they are now installed as something other that what they were a week ago. If anyone is curious, let me know and I will find out what they are. At the moment I don't remember.
When using Odin or Heimdall, both detect that the device is there, but flashing is unsuccessful. I'm guessing because of the drivers. Putting FW, repair files, TWRP and CF on to an SDcard and trying to update from external storage didn't work either. Said it was disabled.
Looked at trying to boot from an SD card......not gonna happen, I'm not that smart. I even found a video about how to get an Unbricking File, but the download link takes you to a locked dropbox account where you cant get the tool to make the file.
Currently when I turn it on I get these choices in recovery:

Reboot
Reboot Downloader
Apply Update from adb
Apply update from SD
Factory Reset
Wipe cache/data
Mount/System
Graphics Test
Lacking storage boot (or something like that)
Power off

#failed to open recovery, cause (No such file or directory)#

#Reboot Recovery Cause is [UNKNOWN]
No Support SINGLE-SKU

File based OTA
E: failed to mount /efs (Invalid argument)
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: failed to mount /efs (Invalid argument)
dm-verity verification failed....
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /system (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_locale

Lets see, what else....tried to run the graphics test. That came up with the image of the dead android robot saying error, then it erased something. I don't know what.
The low storage booting got me a lit up screen that said nothing.
If i try and let it boot by itself...I get the Samsung Galaxy screen and then it goes to that really bright yet empty screen and stays there. This I found drains the battery VERY fast. I do believe that I have exhausted every option to revive my electronic buddy. My new one will be here by Monday.
In closing, I'd like the say "Thank you" again to everyone that helped me out. I wouldn't have learned what I have if not for you guys. If there's anything that anyone can suggest that would fix it, or if there's something to risky to try on a working device that you would like me to try, feel free to let me know. I don't think I can break this one more than it is.

Thanks again-
Kim

kstehling79 · Sep 22, 2019

I'm am pleased to say that my stubbornness paid off. Two days ago I got my tablet to start. And today it's back up and running LiquidRemix with Android 9 with no problems. It's actually running better than before. I'm not positive what exactly it was that worked, but I'll explain everything I did and hopefully someone can get some use out of it.
I first plugged it back into my PC running Windows 10, used Odin 3.13.1 and tried flashing TWRP. Again got all the same errors. Not sure if an OS was even still on the device and double checked Device Manager. The drivers that had been in place looked like the ones previously installed but showed that the devices were not running correctly. I uninstalled everything relating to Samsung that I could find on my PC. Drivers, SmartSwitch, Kies etc.
After downloading new drivers I plugged my tab back into the same USB port but with a different cable (not stock) and let windows detect and install the recommended drivers.
Out of curiosity I started heimdall frontend and was able to get my tab recognized and extracted the PIT file successfully! After that I started Odin and flashed TWRP and got the green "Passed!" mark for the first time since I broke it. From there I was able to flash the most recent FW (Oreo 8.1) and after a few little hiccups she started up good as new. After that, rooted with Magisk, flashed a few ROMs before settling on LiquidRemix and then put on a few mods from Magisk.
I can't say of it was the cord, drivers, or just lucked out but this is what ended up working for me. Figures that the new one will be delivered tomorrow. At least I'll have a back up. LOL

Amit saha · Apr 12, 2020

kstehling79 said:
I'm am pleased to say that my stubbornness paid off. Two days ago I got my tablet to start. And today it's back up and running LiquidRemix with Android 9 with no problems. It's actually running better than before. I'm not positive what exactly it was that worked, but I'll explain everything I did and hopefully someone can get some use out of it.
I first plugged it back into my PC running Windows 10, used Odin 3.13.1 and tried flashing TWRP. Again got all the same errors. Not sure if an OS was even still on the device and double checked Device Manager. The drivers that had been in place looked like the ones previously installed but showed that the devices were not running correctly. I uninstalled everything relating to Samsung that I could find on my PC. Drivers, SmartSwitch, Kies etc.
After downloading new drivers I plugged my tab back into the same USB port but with a different cable (not stock) and let windows detect and install the recommended drivers.
Out of curiosity I started heimdall frontend and was able to get my tab recognized and extracted the PIT file successfully! After that I started Odin and flashed TWRP and got the green "Passed!" mark for the first time since I broke it. From there I was able to flash the most recent FW (Oreo 8.1) and after a few little hiccups she started up good as new. After that, rooted with Magisk, flashed a few ROMs before settling on LiquidRemix and then put on a few mods from Magisk.
I can't say of it was the cord, drivers, or just lucked out but this is what ended up working for me. Figures that the new one will be delivered tomorrow. At least I'll have a back up. LOL

Bro i need your help. I had same problem. But i could not find pit file and appropiate twrp . Could you help me out? Please....

A Rather Complex Problem

Lurker

DON'T PANIC!!!!!!!!!

Lurker

DON'T PANIC!!!!!!!!!

Lurker

Android Expert

Lurker

DON'T PANIC!!!!!!!!!

Android Expert

Lurker

Attachments

Lurker

Lurker

Lurker

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads