Develop Bugs

I have no idea wat to do heeelp!!!

Here is my problem. It all started a few days ago. My phone's drivers on the computer got all messed up. I reinstalled it and thought nothing of it. Today I was guna flash a new rom on. I odin my phone to do a clean install. Then i rooted it to ext4. (After the fact i realized i had clicked the wrong file and loaded di18) However then my bro wanted to use my computer for his epic to odin it too. So i can't load my phone cause its in ext4. I can't fix the drivers because its in download mode and can't get into regular mode. And I can't odin it back because odin wont' recognize it because of my drivers. Its a circle of pain. Is there anything I can do?
After thinking about it will loading a di18 ext4 rom work to fix it?

Reinstall the drivers. And odin ec05 pre rooted. If ur in download mode its fine. Just delete the drivers reboot your pc re install the drivers put your phone into download mode and connect too your usb cable. Your phone doesn't have too be in "regular" mode as you callled it

There aren't any DI18 EXT4 roms. There isn't any EXT4 support for Eclair.
Redownload the Drivers then run ODIN. Install one of the pre rooted .tars.

http://www.multiupload.com/A9VPX4G2ZW here's the ec05 ext4 pre rooted tar

driver
i already redownloaded drivers it kept on not installing saying failing to install.

Ok download the link I gave u for ec05 tar. Put the tar in pda. Make sure u have the pit file selected as well.

And when u open odin. If your phone connects it'll be a yellow box saying com whatever could be com 6 or com 8. Also only have auto reboot checked nothing else

Sounds like your not using odin properly. Here Is a video showing you exactly what too do.http://www.youtube.com/watch?v=YQ2g6J1JgjU

samdsox said:
i already redownloaded drivers it kept on not installing saying failing to install.
Click to expand...
Click to collapse
Uninstall the drivers first and reboot.

fixed but new issue
I managed to. Fix it by using another computer and my dads phone to install drivers. Btw I already knew how to get in dl mode use odin root flash roms and all of that. My problem came from the fact thatb odin didn't recognize my phone in dl mode on my main computer. Now onto my new issue. Last night after I fixed the phone I had a small pinl blotch on the topleft o my phone. Now the blotch. Has spread to my whole phone along with blue and purple dots almost like its leaking. Is the lcd broken? Any ideas?

Ditch odin and learn to use heimdall
Sent from my SPH-D700 using XDA App

best way to fix this is to uninstall the usb root hubs in the device manager and reboot. that's for the driver issue...

[Q] Unrooted, partially rooted purgatory? Please help!!!

Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!

I will donate to any developer that can get my phone back to working order!
bigmtnskier said:
Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!
Click to expand...
Click to collapse
I am desperate at this point , I have spent 2 almost 3 days trying to get my phone back to stock or rooted state. I have scoured Google, XDA and other Android phones. If anyone wants to volunteer and help me on or offline I will gladly donate generously.

I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:good:thank you, I will give it a go and try it as you describe.

Fixed after almost 3 days!!!!
shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:laugh:FIXED!!!!!!!!!!!!!!!!!!!!!!!
I did what you said, but only after I figured out that I was using the wrong driver, correct device, wrong model. I used a USB driver cleaner, cleaned them all off, wiped the device, installed the driver and reconnected then I followed your instructions!:good:
I found these instructions on the AT&T Samsung forum for how to clean your drivers:
http://forums.att.com/t5/Android-Di...ix-for-Windows-7-at-least-for-me/td-p/3369515
Samsung Galaxy S3 MTP USB Fix for Windows 7(at least for me)!!
Post Options
‎11-30-2012 02:55:21 PM
Here's what worked for me after literally trying everything under the sun (compiled steps from various sources):
Steps to Safely Cleanup and Remove old USB Mass Storage Drivers on your PC
Shut down your computer. Unplug your USB storage devices: USB Disks, flash, cams, CD/DVD, etc.
==> Other USB devices like keyboards, mice and LAN adapters can stay plugged in
Boot computer back up. Click for how to determine whether you are running 32 or 64 bit Windows
Download drivecleanup.zip, unzip and save to your desktop. Move the 32 or 64 bit version of DriveCleanup.exe toC:\Windows\System32
Open a command prompt window as follows:
==> For XP only: You must have Admin privileges. Click Start->Run, enter cmd
==> For Vista and Windows 7: You must open an elevated command prompt window!
After the command prompt enter: drivecleanup.exe
==> Your command prompt window should be similar to my example below.
==> If, instead, you get an error message like Command not recognized it means you didn't move Drivecleanup.exe to the right directory
Reboot.
Download the latest USB drivers here:http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT Click the tab at the bottom that says "Manuals & Downloads" then Software then the link for the Device(Install),USB Driver (Software) (ver.v1.5.14.0)
Intstall Drivers
Reboot
Unplugged or disable your internet connection ***CRITICAL***
On your S3 go to Settings>About device>Check for updates and install the update (eventhough we next do a hard reset the new firmware is worth it if only for the brightness feature added to the notification drop down).
Do a hard reset on your Galaxy S3 instructions for that here: http://www.hard-reset.com/samsung-galaxy-s3-hard-reset.html
Turn on S3 (without USB plugged in) and don't login to your Android account ***CRITICAL***
Plug in USB and it should install all the drivers at long last ***SIGH***
Login to your Android account with the USB plugged in and you should be good to go!
Thanks again for helping me out!

my android is partially rooted or partially unrooted
Before three days I was think to update my android.so I done to unroot my android.after update my device is not root again.it says failed again and again.i also try to unroot again but this is also says that root required first.how can I do.i want to root again.please help me.:crying:

[Q] Need some help with my Rogers root

So I'm running 4.1.2 on my Rogers gs3 and am using the MrRobinson method to root (http://forum.xda-developers.com/showthread.php?t=1739426)
Since I am using a mac, I am running VMware to run Windows 7. I followed the steps in the thread/related video:
-shut down phone/run download mode
-Open Odin
-plug phone in using micro usb that came with phone
-under PDA, find xxx.tar.md5 file for Rogers 4.1.2
-let Odin do some verification (automatically happens once i select the md5 file)
-Click start
at this point nothing occurs - I get the 0/0 message that is seen in the video. However, nothing happens to the phone, it remains in download mode with no changes on screen.
I've tried restarting the phone and restarting Odin, but nothing seems to work.
Does anybody have any idea where I should go from here? I am hardly an expert with technology and am terrified of bricking my phone (the phone is working normally at the moment, it is not in download mode).

mikeclaws said:
So I'm running 4.1.2 on my Rogers gs3 and am using the MrRobinson method to root (http://forum.xda-developers.com/showthread.php?t=1739426)
Since I am using a mac, I am running VMware to run Windows 7. I followed the steps in the thread/related video:
-shut down phone/run download mode
-Open Odin
-plug phone in using micro usb that came with phone
-under PDA, find xxx.tar.md5 file for Rogers 4.1.2
-let Odin do some verification (automatically happens once i select the md5 file)
-Click start
at this point nothing occurs - I get the 0/0 message that is seen in the video. However, nothing happens to the phone, it remains in download mode with no changes on screen.
I've tried restarting the phone and restarting Odin, but nothing seems to work.
Does anybody have any idea where I should go from here? I am hardly an expert with technology and am terrified of bricking my phone (the phone is working normally at the moment, it is not in download mode).
Click to expand...
Click to collapse
have you tried easy root, or researched and found other methods simpler to root or load up custom Roms because bricking is a bad thing but am sure you have to search how to put in download mode, idont know if its the same with the AT&T Galaxy S3 i747 but if it is then
hold volume up button + power button + home button at the same time until you get into download mode then load up some stock rom with ODIN and just about 5-10 later depending on your phone it will boot up but before all that ODIN has to verify on the top right box that its working and ready to go with the process
icant say alot since am too lazy just search how to do it on google, youtube, other forums or even here on XDA am pretty sure yu will learn and fix your problem in just about time to enjoy the goodness of rooting/customs
bear with me i was like that once i started rooting but months and i feel like i can do anything but not messing with files, scripts etc or the kernel am still learning the ways of rooting and customs roms
yu just need to take your fast step , man up and yu will conquer rooting, that is much do your thing remember dont brick it

Help me root my at&t samsung galaxy s3 sgh-i747 android 4.3 jellybean!!!

Alright guys I am a noob.
But from watching videos and reading manuals, I was able to flash Odin (about 10 times).
I did everything right:
-I set USB Debugging
- I downloaded the CF Auto Root
- I downloaded Odin
- I download the Samsung USB Drivers
-I put Download Mode.
- I did the PDA file and selected the CF Auto Root.
-I The ID:COM box changed color (which I struggled to manage at first).
-The Message Box says, "Added."
-I pressed Start
It restarted like of nothing. I didn't get Supersu. Root Checker Basic says it is not rooted.
Framaroot doesn't work on my phone so that is not an alternative.
Any other uncomplicated methods I can try?
Does anyone know what I am missing to root my phone?
Please help I have been trying for a whole week and nothing

Juanitocm said:
Alright guys I am a noob.
But from watching videos and reading manuals, I was able to flash Odin (about 10 times).
I did everything right:
-I set USB Debugging
- I downloaded the CF Auto Root
- I downloaded Odin
- I download the Samsung USB Drivers
-I put Download Mode.
- I did the PDA file and selected the CF Auto Root.
-I The ID:COM box changed color (which I struggled to manage at first).
-The Message Box says, "Added."
-I pressed Start
It restarted like of nothing. I didn't get Supersu. Root Checker Basic says it is not rooted.
Framaroot doesn't work on my phone so that is not an alternative.
Any other uncomplicated methods I can try?
Does anyone know what I am missing to root my phone?
Please help I have been trying for a whole week and nothing
Click to expand...
Click to collapse
Did you try installing supersu from the playstore? Maybe you are rooted but supersu wasn't installed. Weird glitch i know but its happened before.
Sent from my SGH-I747 using Tapatalk

Florad77 said:
Did you try installing supersu from the playstore? Maybe you are rooted but supersu wasn't installed. Weird glitch i know but its happened before.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
if you install CF root you need to get super user . to OP did Odin say "Pass" with green light

Thanks both
I managed to root my phone by installing Supersu from the Play Store.
Thank you guys!

[HELP!] Odin Firmware flash failed at hidden.img. Stuck in DL Mode. T700. Plz Help Me

Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.

Private Message UpInTheAir and see what he thinks.

Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.

The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.

eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.

I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet

Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.

eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....

And make a Nandroid first this time

Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.

Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.

ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot

ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....

pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.

ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?

pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))

TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.

My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.