[Q] device hangs in black boot screen after ... - Samsung Epic 4G Touch

I screwed up my SPH-D710 big time (see details here ...). I am starting a new question thread here as this doesn't have anything to do with the device constantly booting anymore.
I have now manged to get the device into a state, that it doesn't boot anymore, neither regular nor into recovery, but hangs in the black boots screen that says "Samsung Galaxy S II" in white letters.
I can still boot into Odin mode though - and I hope that's a good thing.
Last thing I put onto the device (also mentioned in the other thread) was Garwynn's SXTP+Agat Recovery kernel v0.3.0 from Rwilco12's repository.
Can I still save the device and how.
I really want some expert advice before I do the next step ...
Thanks in advance!

OK, so my device is officially bricked. I think I can still get into Odin mode (if I find a charged battery, as mine drained / didn't charge any more in the mean time).
In case I find a charged battery and can still get into ODIN mode, I want to try a [rooted] stock ROM - does it matter which one?
Eventually I want to load CM11.
Thanks.

Please follow these directions to return to stock latest rooted.
Download these files and place them onto your desktop named EpicStockRooted.
Choose between whether you want Data wiped, or not.
GB27 Rooted Data Wipe
GB27 No Data Wipe
Samsung Drivers
Make sure Samsung Kies, or other versions of Samsung Drivers are uninstalled first. Then install the Samsung Drivers.
Once you're finished start the executable GB27 file as administrator mode and wait for it to load. Once you're done, proceed to put the device into download mode. Hold Volume Down + Power button until you're on a Android Firmware dialogue with the green android, press volume up to proceed to the next screen.
Now plug in the device to the computer ( USB 2.0, original samsung usb to micro plug ) and let the device be recognized. you'll see a [COM:##] show up within the first white box, doesn't matter about the ##, as long as it's reading [COM:]
Proceed to click START! and wait for it to be finished, appx ~15 minutes to do so.
Once done the device should auto-reboot. Let it load up.
Setup your device and proceed to the home screen of the launcher, SuperSU will force close on you, don't worry about that, press YES and setup your Google Account for Play Store.
Update SuperSU via playstore, then install as /system app in SuperSU, you're done setting up now.
You're issue was installing a custom kernel for the wrong type of Android version for your ROM.
The latest Custom Kernel for Jellybean GB27 is Agat's Source version 1.4.2f. Use Odin 3.07, within PDA slot to flash the custom kernel. But make sure you're fully loaded on stock first.
If you happen to think about loading CM11, Please feel free to see this post HERE

Thank you very much Spark!
That's pretty much what I did after some heavy research here on this - very helpful - forum.
I downloaded and installed a rooted one-click GB27 and am back up and running - learned a lot from that experience.
Thanks also for explaining what I did wrong.
I am now in the process of downloading the necessary stuff for going to CM11.
I installed Mobile Odin (Lite) and am putting EL26 CWM recovery (StockCWM-EL26.tar.md5), an ICS modem (FL24.zip), gapps and CM11 (I will start with the stable milestone version from here, and then maybe try the latest nightly, if success ...) on my sdcard.
I read (and read again ...) this post on the "one Stop FAQ for Noobs" thread and hope that I won't run into any issues.
Thanks again!

You're welcome, it's all about trial and errors here, People can read and read but most posts around here do get confusing on what you should do and it is A LOT of reading. But once you get used to it, you'll be up to speed on what to do from there on.

I managed to get the device to CM11 and everything is working.
I followed the instructions in the "One Stop ... for Noobs" thread and the OP in the CM one. The only hickup that I had was that the EL26 recovery kernel only has CWM5 and one obviously needs CWM6 (probably in order to flash a KitKat ROM ... (?)), so I had to find a CMW6 recovery that I could flash with CWM5.

Related

[Q] Need to find a stable ROM (i think) so that I can root and use Triangle Away

First, I realize there are a plethora of posts regarding this issue, and I assure the (hopefully) helpful people who respond that I have read through a lot of them; including posts on other sites. In the off chance I have missed an important thread somewhere, just remember that it takes the same amount of effort to suggest I look at said thread(s) as it does to respond with unhelpful replies. So let's go over the details...
Phone:
Sprint SGS2 SPH-D710
No service attached (can't be used to make calls or data usage)
Nothing to save; no problem with wiping (no matter how many times I need to)
Problems:
1. Didn't realize (until it was too late) there was a limit of flashes (brick bug), but Triangle Away should get me past this; I just can't seem to find a ROM that will let me get into recovery as described in this thread: http://forum.xda-developers.com/show....php?t=1501719
2. Odin3 1.82 will always fail with "Complete(Write) operation failed" when trying to flash ucle5_stock_rooted.tar
3. Odin3 1.82 succeeds with Siyah-s2-v4; however, phone will not boot past the yin and yang graphic. When trying to enter into recovery, all I get is the powered-off-battery-charging screen.
4. Odin3 1.82 succeeds with D710-HOME-D710.FH13_CL663858_REV02_user_low_ship.tar.md5 ; however, when trying to install CWM.zip (as per this thread http://forum.xda-developers.com/show....php?t=1501719 ), the result is a red triangle over the droid lying on its back
5. Odin3 1.82 succeeds with SPH-D710_Zedomax_Kernal.tar; however, I am unable to enter into recovery. When trying to enter recovery, all I get is "Samsung Galaxy SII GT-I9100" with yellow triangle; no boot.
6. The flash count is currently at 6
7. I have tried using these two one-click files: SPH-D710.EK02_CL704398-OneClick.exe and SPH-D710.FF18_CL663858_ROOTED-OneClick.exe; I get the red triangle when trying to apply update from zip.
Now for my question(s):
Will somebody please tell me what will help me to 1) Get into recovery to 2) install CWM.zip and SU-BusyBox.zip so that 3) I can finally install a custom ROM?
this is a one click odin rooted: http://rwilco12.androidfilehost.com/?dir=LeakSite/Leaks/Samsung Epic 4G Touch/FI27/ROM
then odin this kernel for custom recovery the 6.8 version: http://www.rwilco12.com/downloads.p...ls/ICS/Agat63 Recovery/Source Built/One-Click
Then you have a safe CWM recovery to flash what ROM you feel like.
Also, you need to be in download mode: power + volume down
for both of the odin one clicks.
Then you can use recovery mode: power + volume up
Problem Solved
Thank you, g_ding84. Your suggestions finally put an end to my problems. I didn't see a thank button to click on... Edit: Button appeared after submitting this reply.
All the roms you fisrt installed on your phone where built for i9100 GS2 phones not the Sprint Epic Touch varient, you flashed the wrong stuff.
Thats why you need to READ, , READ, and then READ some more, and understand what your reading.
Your going to need professional help to figure this one out.
Pp.
sent from a jellybean filled epic touch.
Kagemusha- said:
Thank you, g_ding84. Your suggestions finally put an end to my problems. I didn't see a thank button to click on... Edit: Button appeared after submitting this reply.
Click to expand...
Click to collapse
No problem. I know it sometimes can be a bit confusing. Just make sure to read the OP instructions on flashing a new ROM.
The EL29 direct boot kernel or EL26 CWM kernel will be your friend if you want to flash CM/AOSP type ROMs.
Both in development thread under kernel repository.

[Q] I think I may have screwed up switching recoveries..

I've been flashing nightlies for CM11 from their website for a while now using the latest CWM, and I've been reading up on Open Recovery scripts and apparently CWM isn't compatible which would make flashing nightlies so much easier.. So I used the goo.im app in the Play Store to flash the latest TWRP for my Note 2, it said flash complete and I went to go check it what the recovery looks like and it's not getting past the splash screen. I've tried putting it in download mode to see if there was anything I could flash to fix it, and my PC isn't picking it up through Odin. What can I do? I've let it sit at the splash screen for a while now and it's doing nothing. I've switch USB ports on my PC, I've even reinstalled the SAMSUNG_USB_DRIVERS, and it's still not reading the device through Odin, but it's sitting here at the Odin download mode. Thanks for any help in advance guys. Was there anything I was supposed to do before flashing the TWRP recovery .img?
Edit: and just for clarification.. I did Google search a few queries related to my question and got no real clear answers. I know I'm still kind of new, but I'm not dumb either. Haven't had too many issues switching roms etc, just switching recoveries.
Edit2: Another thing to add, is when you plug the Note 2 into the computer, it reads it as "Gadget Serial". I updated to Odinv3.09 and it's not reading my Note 2 so I could flash stock firmware.

Sprint GS3 Stock 4.3 firmware here!

I've managed to download a fully working 4.3 md5 for the Sprint Galaxy S3. I've uploaded it to Mediafire so you don't have to deal with slow download speeds. Took me 7 hours to download this from a different website. i hope you all enjoy PM me if the link gets taken down, and i'll re-upload it. This is Android 4.3 for the Sprint Galaxy S3. this firmware is to be flashed with Odin, (I've provided 3.07 on Mediafire as well) which you can download below, Samsung device drivers (Version 1.3.15.0000.0) are included as well, and the Stock 4.3 firmware in the link below. You will also need Winrar to extract and run Odin.
Samsung Drivers: http://developer.samsung.com/board/download.do?bdId=0000000700&attachId=0000000001
Sprint GS3 4.3 stock Firmware: https://www.mediafire.com/?nq2ugt0oo9tlj65
Winrar: http://www.rarlab.com/download.htm
Note: this is NOT rooted and it DOES have knox.
For beginners with flashing firmware on Odin, after you download the S3 firmware, put your S3 into Download mode. If you have a USB jig like me, you plug that in. If not, while the device is turned off, hold the volume DOWN, POWER button, and HOME button.
Run Odin as an administrator, make sure the Auto Reboot and F. Reset Time boxes ARE checked, the click the PDA button, navigate to the place where you downloaded the firmware too, and click it. It will take a second to check the md5 file, Odin will freeze and not respond, so let it load. if it takes 5 minutes, close Odin. If not, then Odin will unfreeze and the start button will be able to be clicked.
Click the button, sit back for 5-15 minutes, and let Odin work it's magic. Odin runs best if it is the only application running.
I have experienced when restoring from ROMs that sometimes the phone will not fully boot. if you are restoring from a ROM, go into Clockworkmod or TWRP, wipe data, cache, dalvik cache, and wipe system. Yes, wipe system. If you don't have CWM or TWRP, the try using the default recovery and wiping data and cache. If you don't know how to boot into recovery mode, hold the volume UP button, the POWER button, and the HOME button until you see blue text in the top right screen, then let go. when the text disappears, hold that button combo again until you see the android with an open chest. Then proceed to flash back to stock with Odin. This will ONLY work with Odin. I don't think it matters which version of Odin you use. You CANNOT install this straight from system recovery or Clockworkmod, or TWRP. I hope Sprint GS3 owners are happy with this. :3
I am in no way affiliated with Samsung. I am just providing a mirror for those of you stuck with really slow downloads because people want to make money with ads. I have played no part in making this software, i have not tampered or edited it in no way at all. This is literally stock Android 4.3 for the Sprint Galaxy S3. I also am providing the files for Odin and the Samsung drivers because people have trouble finding both of those files. they are not mine.
nice post and find but I've had this up for quite some time now lol
Oops sorry I never saw it when googling for the firmware yesterday or when looking through the forums.

[Q] update to 4.4 from 4.3 +clean some bugs

Hi all my name is Blake and I'm a noob. (Sigh) thanks in advance for answering my stupid questions and being the awesome intelligent human bada$$es you are and helping teach me to better understand and operate my phone! So I rooted my phone a while back (4.3) or at least attempted it but I think Knox or something along those lines was preventing the process from completing so I had a friend help me out to complete the root so I'm still not 100% on how to do this. So I want to upgrade to 4.4 assuming it's better but more importantly my phone has a lot of quirks and bugs that annoy the living crap out of me and I won't waste u r time listing them unless you need me to and I'm hoping updating will solve some of them and if not I'll be back to forum surfing... anyways I'm rooted and need to know how to get to where I can get the ota update and then root it or however would be easiest to get the update and back to being rooted? I tried reading and understanding the existing threads but I'm still learning the terminology and i couldn't quite understand the ones i could find. Also this is probably a stupid question but is there an app or anything that will magically go through my phone and fix any stupid bugs and stuff!
Also to show my appreciation if u guys have like a YouTube channel i can like and subscribe to or anything i can do to show my appreciation I'd be glad to do so just send me a link thanks again you're my hero!
magikalbum said:
Also to show my appreciation if u guys have like a YouTube channel i can like and subscribe to or anything i can do to show my appreciation I'd be glad to do so just send me a link thanks again you're my hero!
Click to expand...
Click to collapse
I know you wanted a video I don't have all of the equipment to do so .. this is just a lot of words but simple easy steps.
Best possible solution for you if you really wanted the 4.4 update (nothing really has changed except the basic updates (firmware/modem)
... nothing noticeable except when you click on About Phone lol and you see 4.4.2 and the description of your system. That's really it.
But if you really want to give it a try the best solution for you is:
1 ALWAYS BACK UP YOUR PHONE!
This WILL BE UNROOTED BUT WILL GIVE THE OPTION TO BE ROOTED IF YOU WOULD LIKE
2 Download Odin if you haven't already and download the .tar file for 4.4.2 (the OTA Update)
When you extracted everything and opened Odin make sure Auto Reboot and F Reset Time is the ONLY ones checked.
3 Put the .tar file in PDA on Odin and put your phone in download mode (home, vol down, and power) when it comes up press vol up and it will show downloading .. it may show NOT RESPONDING give it a minute it usually will load up
Attach the usb cable from computer to phone once it registers it (will say added) click start. let it finish and you will have a complete wipe of 4.4.2 STOCK ROM --- UNROOTED!
FOLLOW THESE STEPS (COLOR MATCH) TO BE ROOTED ..... 4.4.2 ROOTED OR 4.3 ROOTED
-THIS IS THE START FOR BOTH --
1 Download your custom recovery (Philz or TWRP) ... I use Philz it's simple and and does everything for you to make sure it goes through.
2 Open Odin once more (same checked) turn your phone off wait for the vibration to indicate it is completely off then put it in download mode.
3 Place your recovery in PDA then attach phone and click start.
It will reboot just turn phone off and enter recovery mode (home, vol UP, and power). If the recovery doesn't show (sometimes it won't due to knox again) Then try again this way:
Phone off, place recovery in PDA, attach phone, and UNCLICK Auto-Reboot and push start. It will show downloading wait for Odin to show pass then boot in recovery from the screen you are on by just pushing home vol up and power. It should load that time.
Once it's loaded...
FOR 4.4.2 - ROOTED
3. Factory reset/clean to install new rom ...
DO NOT wipe cache just simply factory reset ..wait.. done ... clean to install new rom .. wait .. done.
If you do you will get a Status 7 or an error message.
4. Flash rom
5. Reboot
-It may ask you if you want to disable custom recovery make sure you hit NO!
You will need to update SU on playstore. And you should be good to go (had problems the first few times).
FOR 4.3 - ROOTED
DO NOT TRY FLASHING .TAR THROUGH ODIN. It will fail everytime because you can not downgrade firmware through it.
1. You will need to go back to stock unrooted with this HERE (MC2 Download only)
2 Make sure you have the MC2 Download -- or you will receive a Status 7 .. which means you don't have the right rom to update from.
3 Once you're on the MC2 firmware I believe it is the 4.2 version.
4 Turn off phone, enter recovery mode and flash this MC2 to Mk4 Rooted (NEED TO HAVE MC2 first!)
5 Reboot - if it asks to disable custom recovery make sure you press NO or it will unroot it at start up.
.

[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.

Categories

Resources