Need help, bricked during root SM-t560nu - Samsung Galaxy Tab E Questions & Answers

So I was following a walk through root using Odin and CM auto root. My computer froze up and blue screened, now my tablet is not letting me go anywhere but a page that says that I need to so an emergency recovery with Samsung side switch. Everything I have been seeing had shown me that Samsung kies might fix it, but currently no luck finding it yet. Can someone help get me to a point where I don't have a pretty glowing brick?

gititus said:
So I was following a walk through root using Odin and CM auto root. My computer froze up and blue screened, now my tablet is not letting me go anywhere but a page that says that I need to so an emergency recovery with Samsung side switch. Everything I have been seeing had shown me that Samsung kies might fix it, but currently no luck finding it yet. Can someone help get me to a point where I don't have a pretty glowing brick?
Click to expand...
Click to collapse
Ignore that message. You can still boot to Download mode regardless and repeat the procedure.

Thanks. My brain went haywire and didn't notice that Odin still recognized it.

Related

Stock DL17 ODIN Image With Root

I notices a few users have mentioned that they're dealing with trying to restore or unbrick their Continuum after flashing incompatible kernels and other problems.
I made this backup immediately after I got root, before I did anything else, to make absolutely sure I wouldn't be SOL if anything went awry. I've made absolutely certain this works, by unzipping and flashing on my own Continuum prior to uploading. It contains the system, recovery, and kernel partitions.
This file is also helpful if you need to get back to stock for warranty purposes, in which case you can manually un-root by using your favorite file explorer (I happen to prefer ES File Explorer), grant root permissions, mount system as rw, then manually delete SuperUser from /system/apps, su from /system/bin, and busybox from /systen/xbin. I hope this helps some of you who have been stuck.
You don't need to be rooted to flash this. Simply unzip, flash the .tar.md5, and you're golden. If you end up in restore mode after flashing, you probably need to do a hard reset, but this is unlikely as I tested it by flashing this a few times after installing various programs from the Market and never had to do a hard reset.
Don't forget to put your phone in Download mode by removing the battery, then holding the vol down button while inserting the usb cable. Good luck!
http://www.mediafire.com/?a897dbakz4j7k4f
Thanks for this. I had been messing around with the phone. I was able to get it back to stock.
Kay I try to flash this and it's telling me it's an invalid image type
Never mind, I got it. Thanks
Not a problem, glad I could help!
My phone was soft-bricked. This worked like a charm. Thank you so much!
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
kingtuk1 said:
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
Click to expand...
Click to collapse
Yup, gotta wipe! At first it's so easy to forget this step. When you get to customizing your installation, you'll get to used to having to wipe it'll become second nature!
I'm so glad to hear this is coming in handy for you all! Now that you got this done, get yourself froyo, courtesy of imnuts: http://forum.xda-developers.com/showthread.php?t=1197415
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Native89 said:
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Click to expand...
Click to collapse
Read the OP from pastorbennett here: http://forum.xda-developers.com/showthread.php?t=1203597 and try the unbrick process. You can do a search for pastorbennett and trailblazer. Both have posted "recovery processes", or at least links to others that have posted recovery processes. They've saved my butt a couple of times... Except on my first phone that wouldn't go into DL or Recovery Mode. It would just flash the Samsung logo, over, and over, and over again... That happened before pastorbennett posted the unbrick info. Oh well, Verizon replaced it under the hardware warranty. Thankfully.
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Native89 said:
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Click to expand...
Click to collapse
Okay, if you can, grab a different computer (either Windows XP or Windows 7) and install the samsung drivers from this post: http://forum.xda-developers.com/show....php?t=1203597. The hint here with ANY Windows computer is to install the device drivers FIRST! (I've been a system administrator for about 20 years.) Then plug in the hardware. It usually makes the installations go MUCH smoother.
If you have to use your computer, try installing the Samsung drivers first, then plug the phone in.
zzir said:
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Click to expand...
Click to collapse
The key to odin seems to be this:
1. Start odin.
2. Click the PDA button and select the odin TAR or MD5 file. (You can only do one. Not both.)
3. Make sure the phone is not plugged into the computer.
4. Make doubly sure the phone is not plugged into the computer.
5. Put your phone into download mode. (With the phone off, hold the Volume Down button and turn the phone on.)
6. Then plug the phone into the computer.
7. Start the odin flash and you should be good to go. Also, before unplugging the phone, make sure it says either success or failed. If it doesn't say anything, or says loading (or something like that), WALK AWAY! Go get yourself a cup of coffee, a soda, a nice cup of tea... Something. I recommend waiting at least 10 minutes. If the progress bar has not moved, in that time, okay, then pull the cable and the battery and start again.
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Tarheel487 said:
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Click to expand...
Click to collapse
Did you flash the CWM Recovery in Odin? (cwm_recovery_test4_adryn.tar) Can be found here if not http://forum.xda-developers.com/showthread.php?t=1230072
is it possible to flash this with heimdall or only odin?
ntien said:
is it possible to flash this with heimdall or only odin?
Click to expand...
Click to collapse
I don't know, however, pastorbennett posted this http://forum.xda-developers.com/showpost.php?p=16600453&postcount=29. It might help? I use Linux at home to build most of this stuff, then use my wife's Windoze machine to flash. It just seemed easier.
Yes, you can use heimdall, you just need to extract this .tar and put the extracted files in the corresponding location in heimdall xD
Sent from my SCH-I400 using xda premium
yeah i saw that but in heimdall 1.3 the UI is different. i don't know where to put any of the stuff. i have the .tar but i dont know where to put the other stuff. here's a screenshot

[Q] Help! I'm really stuck!

I don't think I've bricked my phone, I hope you can help me. Done some reading here, but still a big time noob! Trying to flash back to stock for the Verizon upgrade, my phone is stuck on the screen with a gold triangle and a exclamation point in the center of a cell Phone and a computer. I found a thread with a similar problem. I can't seem to have a successful flash in odin. I keep getting a fail when i flash the test file. I would be content if I could just get the phone to boot and have my Miunia Rom working again. Someone please help.
Al bergie man1 said:
I don't think I've bricked my phone, I hope you can help me. Done some reading here, but still a big time noob! Trying to flash back to stock for the Verizon upgrade, my phone is stuck on the screen with a gold triangle and a exclamation point in the center of a cell Phone and a computer. I found a thread with a similar problem. I can't seem to have a successful flash in odin. I keep getting a fail when i flash the test file. I would be content if I could just get the phone to boot and have my Miunia Rom working again. Someone please help.
Click to expand...
Click to collapse
That means you have no kernel our rom in the phone. Not sure what this "test file" you are trying to flash is, but I'm not surprised its failing. Flashing dl 17 should work. If not, flash the ec07 leak, with the proper pit file, repartition unchecked. Then flash dl17.
Dished out by my dumb digits
now it's worse, I hit the dark abyss
So, I flashed(with odin) the clean Eco7 stock with with the correct pit file. It seemed to be doing fine, it got all the way to recov.bin but then I froze there for about an hour. At this point i didn't think it was going to pass anyway so i unplugged the phone and stopped the program(oops?). Now my phone is even worse, it seems lifeless. The phone won't even go to down load mode. I found on another post where someone else was also getting nothing, no power just blackness, and I followed those directions. Still a black screen. It seems more grim than ever! One thing I have noticed that while attempting to flash, a few times my computer completely rebooted. Out of know where! This has happened about 5 or 6 times. I'm just about ready to turn on my old flip phone but I just don't want to give up yet! Any more suggestions?!
Oops, is right. You may have hard bricked yourself. I've tried helping people out of this one before, with no sucess. That is the reason I told you to make sure repartition was unchecked. You can try to power on, and issue an adb command, if you have it installed. But, I doubt it will work. The reason you don't have download, at this point, is because you don't have a secondary bootloader on your phone, anymore. It turns into a catch 22. Download mode is supposedly hard written on the chip. So, you could use a jig to force it into download mode. I'd say that that is your best bet, at this point.
did uncheck repartition
I did uncheck repartition but obviously with no avail. I Will try the"jig" but I don't know anything about it. Is this a file I can download or what?
No matter what happens, thanks soooo much for the efforts to help me!!! Especially wolf??
No. A jig is a piece of hardware. Do a youtube search for 'download mode jig' and you''' get some good hits. You'd have to construct it, or get ahold of some of the devs that have. I don't recall the name, but one dev made one for the Fascinate. I'd imagine it would work for our phone too.
If anyone can remember who it is (I want to say Adam Outler, but I might be wrong) pipe up.

[Q][SOLVED] SGH-1337 wiped system, can't restore phone

After getting past the painful MF3 firmware and rooting my Galaxy S4, I loaded Safestrap and proceeded to do a simple Factory Reset, I was too excited about moving forward to notice the 'system' Checkbox was checked and my simple factory reset turned into a full system wipe :c
Fortunately I made a backup before I did anything and it's still on my external SD Card, however, I can't get to the Safestrap Recovery(assuming it's still installed on my phone after the wipe) and trying to boot the phone just causes it to shut off, freeze at the Galaxy S4 splash screen or go straight to the stock download mode.
I downloaded Kies to try and proceed with that but I get a "Device not responding" error.
Now literally all I can do is go into the Stock Download/ODIN mode, is there ANYTHING I could do from here or am I screwed?
SOLVED
Attempted an emergency recovery which caused the yellow triangle to appear then brought it back to Best Buy when different reps were working, told them it was a problem with Kies, and they flashed the stock firmware back onto my phone, now I'll just be impatiently waiting until someone finds a method to load CWM or TWRP after the MF3 update since I'm not exactly a fan of Safestrap ^_^
When it boots into download mode can you cancel,vol down? It might boot, but without system I doubt it
Bestbuy with a Samsung experience can flash the mf3 firmware. They're probably your best bet.
jd1639 said:
When it boots into download mode can you cancel,vol down? It might boot, but without system I doubt it
Bestbuy with a Samsung experience can flash the mf3 firmware. They're probably your best bet.
Click to expand...
Click to collapse
I can hit cancel but because it has no system files it just hangs at the Galaxy S4 splash screen. I heard about Best Buy and was going to go there as a last resort and just claim it was a Kies issue.
jd1693 is correct, your best bet is best buy... I only had an issue with my build.prop file in the /system folder, but I could do nothing to recover. My local best buy Samsung "specialist" was unhelpful and wouldn't touch it. I drive an hour and a half to the next nearest one and the guy there was knowledgeable and helpful. He fixed it in 10 minutes. Before I went, I "put" mine in the yellow triangle screen that you get from a kies update fail by trying to restore in kies first. This requires an "emergency recovery" which is a full system flash. I've read others had better experiences with this at best buy over making the employees there put the phone in download mode.
I hope you get a decent Samsung rep. Good luck!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
jd1639 said:
Bestbuy with a Samsung experience can flash the mf3 firmware. They're probably your best bet.
Click to expand...
Click to collapse
Brought it to Best Buy, they said they couldn't do anything for me since my phone was rooted but I told them my problem and they just told me to come here(XDA) or use ODIN or if all else fails, brick my phone and have AT&T replace it.....
So far I haven't gotten any major help here and I'm not very savvy with ODIN and I don't know what use I could make of it with only the Stock download mode and a backup I made before everything went to hell. would really not want to resort to bricking my phone and bringing it to AT&T...
dustyhughes said:
Before I went, I "put" mine in the yellow triangle screen that you get from a kies update fail by trying to restore in kies first. This requires an "emergency recovery" which is a full system flash. I've read others had better experiences with this at best buy over making the employees there put the phone in download mode.
I hope you get a decent Samsung rep. Good luck!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I don't have a yellow Triangle, just the padlock with "custom" under it which appeared after I rooted it. also I can't get my phone to connect to kies :/
EDIT: Managed to do an emergency recovery via Kies and get that yellow triangle screen, I'll bring it back to Best Buy in hope that there's different employees working who I can feed an alibi saying Kies messed up my phone when attempting to do a firmware upgrade.

Bricked, cant move past Download mode Help!

So im pretty sure my phone is soft bricked when i tried to flash a rom, all i can do is put it in the download mode, and the screen is on but just barely you can't really even tell. So im stuck here, i saw that the one click unbrick is for samsung phones. And does this mean that i have to return to stock, and will it mean that i will also be unrooted as well? Has anyone unbricked their device successfully? Any advice is appreciated. I really need to fix my phone quickly.
Check this out.
http:// forum.xda-developers.com/showthread.php?t=2432476
Just flash it back to stock and start over.

[Q] SGH-I337 Download Mode Problem?

Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.

Categories

Resources