Develop Bugs

[GUIDE] Heimdall - BOOTLOOP RECOVERY, STOCK RESTORE! SM-N900T only!

This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Thanks:
Benjamin Dobell for Heimdall - http://forum.xda-developers.com/showthread.php?t=755265
DeezNutz1977 - Original 4.3 Build
allenjthomsen - KK Build files
Phil5739 - Philz CWM Advanced Recovery
bigbiff - twrp always in progress
dragonstalker - for his ROMS and contributions.
ghibli3 - for this guide which allowed me to pull and edit the KK pit file successfully.
There were a ton of threads I read through, I cant remember them all, but thanks pretty much goes out to all who contribute here. The XDA community is great!
Bootloop Recovery Heimdall Guide
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download 4.3 JB Recovery Zip Here
Upload for 4.4.2 in progress
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7) <-- this will trip knox if you haven't already done so.
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download Stock JB MI7 here.
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.

noobtoob said:
This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Bootloop Recovery Heimdall Guide
http://youtu.be/-huMP5ZaMiw
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download this First: https://www.dropbox.com/s/oc534gzr5usbivi/BootLoop Recovery.zip
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7)
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
http://youtu.be/hXtZDUD7MYQ
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download this First: https://www.dropbox.com/s/m9dpb7ya0umvrzl/Stock_SM-N900T_MI7.tar.gz
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.
Click to expand...
Click to collapse
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...

kuroy301 said:
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...
Click to expand...
Click to collapse
Seriously? I just put this up. Any mirror suggestions? I don't really post/share much since I started school a year ago.
Edit: Only 3 views, must be from the youtube videos...LOL. I will search for a mirror.
Dropbox sharing has been denied due to bandwidth usage. Uploading to mediafire now. Should be up in about 2 hours. Sorry everyone.
EDIT: OP Updated, new links added. Hope you all get the help needed.

Heimdall install
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help

Fates_Warning said:
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help
Click to expand...
Click to collapse
Have you tried installing both the 32 bit and 64 bit visual c++ applications? I installed both because i want sure which one heimdall would use.
Sent from my SM-N900T using Tapatalk

Thank you. was missing install the 32-bit. :good:
The problem is now being with the cache file. It hangs at 52% and not flash. Any ideas, my friends?

What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk

i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate

jboy619 said:
i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate
Click to expand...
Click to collapse
In the files you downloaded when you got heimdall, there is an .exe that allows you to replace the USB driver for you device. You have to follow the directions in the read me file they gave you.
You have 3 driver choices to replace the one to flash for yours. There is a windows driver, a libusb driver, and a libusb (k) driver. One of these will allow the phone to flash.

noobtoob said:
What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .

Fates_Warning said:
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .
Click to expand...
Click to collapse
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk

noobtoob said:
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?

Do not proceed from here! I just noticed you are trying to flash a sm-n900t to a sm-n9005. That is why it is not working. The recovery you are trying to flash is not meant for your phone model.
Sent from my SM-N900T using Tapatalk

Fates_Warning said:
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?
Click to expand...
Click to collapse
See above post.
Sent from my SM-N900T using Tapatalk

Hi!
Thanks for your work!
Does it trigger KNOX please ?

noobtoob said:
See above post.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
true .. the problem is that my shows the same bootloop problem are you trying to solve?

"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!

thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?

Nemorensis32 said:
"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!
Click to expand...
Click to collapse
Do not click on repartition. Do not proceed from here if you do not have the sm-n900t. This forum is posted under the "T-Mobile Samsung Galaxy Note 3" which is the sm-n900t. It is possible for you to have this device on a different network, but you should already know what model you are trying to fix.
The .pit file in my recovery zip will not work for you because the phone is not the same. Please go to your respective forum, and look for the files there.
Knox will trip if you flash the recovery I provided.
Sent from my SM-N900T using Tapatalk

jboy619 said:
thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?
Click to expand...
Click to collapse
Try using libUSB, and libUSBk drivers. Mine specifically likes the libusbk. But every phone is different. I believe I had the same error when trying to use the win32 and the libusb drivers.
Other than that, it may be a heimdall issue that I am unfamiliar with.
EDIT: Also I should mention, when mine did all of this, I had to use the recovery zip first, then move onto the stock restore portion. I can't necessarily say why I had to, but I did. If you already have knox tripped, I recommend doing that. While in recovery, I performed an advanced wipe. Wiped system, cache, dalvik and internal storage. The internal storage part may not be necessary, but I wanted to start fresh.
Sent from my SM-N900T using Tapatalk

[Q] note 8.0 cm11 problem installing. Bricked?

Hey guys, I'm currently having problem with my note 8.0 iI tried installing cm11. Downloaded and followed the steps but after wiping and formatting all the stuff that was in the step I'm having this prob see pic below. It says that I'm using n5110 instead of n5100. Now it keeps rebooting and nothing can be done anymore as I already format everything.. and yea forgot to backup ofc ...

amersnap said:
Hey guys, I'm currently having problem with my note 8.0 iI tried installing cm11. Downloaded and followed the steps but after wiping and formatting all the stuff that was in the step I'm having this prob see pic below. It says that I'm using n5110 instead of n5100. Now it keeps rebooting and nothing can be done anymore as I already format everything.. and yea forgot to backup ofc ...
Click to expand...
Click to collapse
I assume you did not install a custom recovery???
If you did you need to download the right firmware package and load from the recovery.
You may try Odin 3.7 if you can manage to get into stock firmware upload.

Its not bricked - your recovery is probably a cwm - flash twerp if you want to install cm11 - or stock recovery..anyway cm11 is great but no phone...so not great for us 5100

gooberdude said:
I assume you did not install a custom recovery???
If you did you need to download the right firmware package and load from the recovery.
You may try Odin 3.7 if you can manage to get into stock firmware upload.
Click to expand...
Click to collapse
How do I install custom recovery? What do you mean? Download stock firmware? How do I install odin. Now when I connect to pc.. it cannot be detected anymore
kzintz said:
Its not bricked - your recovery is probably a cwm - flash twerp if you want to install cm11 - or stock recovery..anyway cm11 is great but no phone...so not great for us 5100
Click to expand...
Click to collapse
Thw note cannot be detected anymore in pc. How do I flash or root again :3

Download and install Odin 1.85 next search the stock firmware for your model here http://www.sammobile.com/firmwares/
Get your Note into download mode ( Press and keep holding the Volume Down, Home and Power ) and connect it to your PC, Odin should "see" it the first slot under ID:slot should turn a different color if so you are in good shape, now put the Firmware you download from above mentioned site click PDA*button and select the downloaded .tar.md5 file, Important: In Odin, make sure Auto Reboot and F. Reset Time options are enabled. Also, ensure that the Re-partition checkbox is not enabled and hit start and let Odin do the rest and you should be up and running in no time and now you can start over from scratch
Sent from my SPH-L900 using xda premium

amersnap said:
Hey guys, I'm currently having problem with my note 8.0 iI tried installing cm11. Downloaded and followed the steps but after wiping and formatting all the stuff that was in the step I'm having this prob see pic below. It says that I'm using n5110 instead of n5100. Now it keeps rebooting and nothing can be done anymore as I already format everything.. and yea forgot to backup ofc ...
Click to expand...
Click to collapse
Did you fix the problem?

[Q] SM-P600 Bricked (no recovery)

Hi,
SM-P600 without ROM, without recovery, Kies and Odin doesn't work.
How can I reflash stock ROM or CM12 rom ?
Device : SM-P600 (with samsung rom stock 4.4!?)
I root my tablet with odin and teamwin 2.8.0.0 (PDA field + tar file)
the root flash should success.
I restart in recovery and install custom rom CM12 + Gapp
the tablet restart and stay to CM12 loading during all the night.
I come back into recevery mode
I try to wipe cache/dalvik => unable to mount cache/dalvik
I try to wipe cache => unable to mount cache
I try to wipe system => unable to mount system
I install Kies on my computer and try to restore the official rom with it.
The download of the rom is ok and Kies try to send the rom to the table a transfer is running during 15min (progress bar into computer windows, but no progress bar into tablet).
After that a second transfer progress bar into computer stay to 0% during 1 hour. I unplug my tablet.
Now I have got a table without recovery. I have access to download mode.
But I cannot transfer stock rom (PDA field) with Odin.
Thx for your help.
Staying at your disposal

I can flash recovery mod (TeamWin) with Odin.
But I cannot send Kies tar file by Odin.
I am downloading old stock rom (*tar) to transfer by Odin 3.09
How can I convert a CM12 zip file in tar file to tranfer it (I haven't SD card)

You could use a USB OTG cable (micro USB plug on one end and a socket like the USB ones on a computer on the other), one of these:
http://m.ebay.com.au/itm/301542874539?nav=SEARCH
And use it to plug a USB stick with the zip file on it into your tablet. You would have to mount it in twrp before flashing the zip.
They are a very useful cable to have, if your screen breaks and touch doesn't work you can use it to plug a mouse into the android device and use that for things like backing up your data before repair or disposal.

Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English

Hi Dribounet
Dribounet said:
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Click to expand...
Click to collapse
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers

p600 bricked
kafencetu said:
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
Click to expand...
Click to collapse
I have the same problem! There is download mode only - NO recovery, NO rom! ((
I have tried to flash original rom from sammobile via Odin. No results.
Who can help???

uno mas said:
I have the same problem! ((
Who can help???
Click to expand...
Click to collapse
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk

kafencetu said:
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
In other words - should I go to the service?

uno mas said:
In other words - should I go to the service?
Click to expand...
Click to collapse
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk

kafencetu said:
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266

uno mas said:
I have rooted also. No the warranty. But it doesn't matter if you have a bricked. ((
The Odin starts writing but no finish.
Click to expand...
Click to collapse
yep this is the case , Odin start process of writing and then suddenly - error - in the middle of the procedure.
I have tried to install only custom bootloader - pass successfully ,but then I am not able to go in bootloader mode ( I am trying with Volume down + Power , do not know is that correct - do you have an idea? )

uno mas said:
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
Click to expand...
Click to collapse
Hello uno mas
would you advice what tools you have used and also what order you have follow.
First update PIT and then installed the ROM or other
Thanks in advance for time and efforts!

[Q] Nand write fail for rom flash SM-T805

Hi, I am in need of assistance. I have a Tab S 10.5 SM-T805 with rom XXU1ANF8
I am struggling to flash firmware for my sm-t805 using odin and stock roms downloaded from sammobile. I have tried various version of the stock roms as well as different versions of odin, but they all have the same result.
The result is either "NAND Write Start! FAIL!!" or "Setup connection.. Can't open the serial(COM) port." The order in which I do things might impact which error I receive, such as attaching the tablet first or selecting the ROM file first in PDA box.
Here is why I am desperate. Since this result was pretty consistent, I flashed TWRP successfully and wiped all the partitions, including the system partition. Now, there is no OS installed. Using TWRP I have attempted the 'Install' method of flashing ROMS, but now my error is exclusively the first type.
I read some of the other threads and attempted any advice relevant posted there. This is sort of relevant to what I am trying to do, but my system partition has been wiped. (http://forum.xda-developers.com/galaxy-tab-s/help/odin-flashes-fail-t3028264), so there is no relevance to enabling USB debugging for disabling reactivation lock. This is a guy who can do what I am trying to do. (http://forum.xda-developers.com/galaxy-tab-s/help/roms-flashing-advice-t805-t3031963)
Please help!

eeekw0 said:
Hi, I am in need of assistance. I have a Tab S 10.5 SM-T805 with rom XXU1ANF8
I am struggling to flash firmware for my sm-t805 using odin and stock roms downloaded from sammobile. I have tried various version of the stock roms as well as different versions of odin, but they all have the same result.
The result is either "NAND Write Start! FAIL!!" or "Setup connection.. Can't open the serial(COM) port." The order in which I do things might impact which error I receive, such as attaching the tablet first or selecting the ROM file first in PDA box.
Here is why I am desperate. Since this result was pretty consistent, I flashed TWRP successfully and wiped all the partitions, including the system partition. Now, there is no OS installed. Using TWRP I have attempted the 'Install' method of flashing ROMS, but now my error is exclusively the first type.
I read some of the other threads and attempted any advice relevant posted there. This is sort of relevant to what I am trying to do, but my system partition has been wiped. (http://forum.xda-developers.com/galaxy-tab-s/help/odin-flashes-fail-t3028264), so there is no relevance to enabling USB debugging for disabling reactivation lock. This is a guy who can do what I am trying to do. (http://forum.xda-developers.com/galaxy-tab-s/help/roms-flashing-advice-t805-t3031963)
Please help!
Click to expand...
Click to collapse
Is activation lock off? That what causes it not to flash. The only thing I can suggest is transferring a custom zip rom and flash it with twrp. Or try another firmware from a different country.

Thanks for your response.
DUHAsianSKILLZ said:
Is activation lock off? That what causes it not to flash. The only thing I can suggest is transferring a custom zip rom and flash it with twrp.
Click to expand...
Click to collapse
It was my observation that this activation lock is off by default on the stock rom. In order to turn this on, you have to register with a Samsung account.
DUHAsianSKILLZ said:
Or try another firmware from a different country.
Click to expand...
Click to collapse
The versions I hav already tried are from different countries as well as from different update dates.
Please help!

Here's lollipop for T805, someone took out a few files which should fix NAND Write. http://forum.xda-developers.com/showthread.php?p=59828324

Have you got the Samsung USB drivers installed? If you don't get the 'added' message when connecting the tab you wont be able to flash anything.
Sent from my SM-T805 using XDA Free mobile app

I am having a very similar problem, except my device is working properly. The only thing is that I can't flash the new Lollipop firmware because of this error.
Does anyone know how to solve it?
Thanks!

vrgimael said:
I am having a very similar problem, except my device is working properly. The only thing is that I can't flash the new Lollipop firmware because of this error.
Does anyone know how to solve it?
Thanks!
Click to expand...
Click to collapse
Try flashing this? http://forum.xda-developers.com/showthread.php?p=59828324 Someone took out the hidden.img and cache imgs and tar it back together. You can take a look at the thread for more info

DUHAsianSKILLZ said:
Try flashing this? http://forum.xda-developers.com/showthread.php?p=59828324 Someone took out the hidden.img and cache imgs and tar it back together. You can take a look at the thread for more info
Click to expand...
Click to collapse
Just tried it. Odin doesn't recognize it as a firmware for some reason. Is there anyway to fix this? Also, what is knox warranty void?

Hi, i have also this problem, Original and the cleared .tar (swisscom) comes with this "fail" information in Odin ...... no plan what that for a problem. I am from Germany and i use a 805 LTE. Wich Odin version is the best for flash 5.0.2 i use 3.10.6 eventuelle is that an problem

meexx said:
Hi, i have also this problem, Original and the cleared .tar (swisscom) comes with this "fail" information in Odin ...... no plan what that for a problem. I am from Germany and i use a 805 LTE. Wich Odin version is the best for flash 5.0.2 i use 3.10.6 eventuelle is that an problem
Click to expand...
Click to collapse
Is reactivation lock off as shown here

This is my odin screen ..... no entris with reactivation. 4.4.2 runs with cf-autoroot and twrp recovery

meexx said:
This is my odin screen ..... no entris with reactivation. 4.4.2 runs with cf-autoroot and twrp recovery
Click to expand...
Click to collapse
Idk then, I guess you got to wait for another firmware that comes to your country

Just flash the Swiss Rom then after it fails, boot into download mode again then Install and boot into twrp.
Twrp will wipe the cache and auto reboot. The device should then boot normally.

Is TWRP 2.8.6.0 chagallwifi ok for this procedur ? and can i flash the original swisscom ? or the cleared .tar without the two files ..... and when i in download mode ... wich kombo can i use for reboot in download mode again

meexx said:
Is TWRP 2.8.6.0 chagallwifi ok for this procedur ? and can i flash the original swisscom ? or the cleared .tar without the two files ..... and when i in download mode ... wich kombo can i use for reboot in download mode again
Click to expand...
Click to collapse
Twrp for chagallwifi should do it. Flash swisscom odin firmware then flash twrp and wipe. Reboot into Download by holding power+volume down+ Home buttons

I have tested this procedure and it dont work for my tab .... i must wait for a no branding rom. It dont boot .... hangs on system.img in odin. Twrp is ok now i cant boot after flash twrp, it stay at samsung logo and no boot .... i have 30 minutes wait. Ok i will wait for a other lolipop rom

meexx said:
I have tested this procedure and it dont work for my tab .... i must wait for a no branding rom. It dont boot .... hangs on system.img in odin. Twrp is ok now i cant boot after flash twrp, it stay at samsung logo and no boot .... i have 30 minutes wait. Ok i will wait for a other lolipop rom
Click to expand...
Click to collapse
There is no branding in the system image. I don't see why it won't flash. Can you post a screenshot of Odin. Also what is your official firmware build number?
German Vodafone firmware is up: http://samsung-updates.com/details/43138/Galaxy_Tab_S_10.5_LTE/SM-T805/VD2/T805XXU1BOCC.html

ashyx said:
Just flash the Swiss Rom then after it fails, boot into download mode again then Install and boot into twrp.
Twrp will wipe the cache and auto reboot. The device should then boot normally.
Click to expand...
Click to collapse
I had the same issue today, when using the UK 5.0.2 ROM. These steps helped and it worked afterwards, thanks!

[a520f] Bricked after flashing boot partition with heimdall no Downloadmode/Recovery

Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
i cannot acces Download mode or recovery or boot the phone
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response

wolkengold said:
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
Click to expand...
Click to collapse
Can you boot to download mode? If you can, flash latest oreo.

iloveoreos said:
Can you boot to download mode? If you can, flash latest oreo.
Click to expand...
Click to collapse
no i cant... at least not with button combinations...

wolkengold said:
no i cant... at least not with button combinations...
Click to expand...
Click to collapse
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.

iloveoreos said:
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
Click to expand...
Click to collapse
thanks, i will try if smart switch will help me.

wolkengold said:
thanks, i will try if smart switch will help me.
Click to expand...
Click to collapse
There is a small chance.

iloveoreos said:
There is a small chance.
Click to expand...
Click to collapse
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...

wolkengold said:
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
Click to expand...
Click to collapse
Cool! Now what happens when you reboot to download mode from twrp?

SnowFuhrer said:
Cool! Now what happens when you reboot to download mode from twrp?
Click to expand...
Click to collapse
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.

SnowFuhrer said:
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
Click to expand...
Click to collapse
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Flash stock firmware using Odin?

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.

SnowFuhrer said:
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
Click to expand...
Click to collapse
sorry for the late response. You were right, i accidentally downloaded an older oreo release and thats why i could not flash it. I now downloaded the newest stock rom from updato.com and it worked perfect.
Thanks for your support

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked

jack364030 said:
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
Click to expand...
Click to collapse
You are correct but...He sorted this 4 months ago.