i tried to update my phone (i474) to jellybean (4.1.4), but i have a mac. so i downloaded odin on my older pc and started the process. it failed and my phone said to connect to kies and enter recovery mode. i did and kies said connecting for several hours. i then went and tried to flash it with the standard firmware (4.0.4) and that failed as well. now my phone wont even start up if i try to enter download or any other mode it vibrates and then does nothing. i can reset it because it wont start up the menu either. is there any way to hard reset it completely, or is it still covered in warrantee. can i fix it
Read this carefully
ete565 said:
i tried to update my phone (i474) to jellybean (4.1.4), but i have a mac. so i downloaded odin on my older pc and started the process. it failed and my phone said to connect to kies and enter recovery mode. i did and kies said connecting for several hours. i then went and tried to flash it with the standard firmware (4.0.4) and that failed as well. now my phone wont even start up if i try to enter download or any other mode it vibrates and then does nothing. i can reset it because it wont start up the menu either. is there any way to hard reset it completely, or is it still covered in warrantee. can i fix it
Click to expand...
Click to collapse
First of all I just want to let you know there are hundreds guys, like you, that don't bother to read the installation instructions and then beg and plead for the forum to fix your problems which the disclaimer states that the OP is NOT responsible if you brick your device or cause damages to it. Second, if you bothered to read the "Rules" for the forum you would know that the General section is meant for such and the Q&A(Questions and Answers) section is meant for such. Please read something. At least once. Please.
I'm not burning you man all I'm saying is calm down and have patience with flashing custom roms because as you found out it can, and will, brick your device, sometimes permanently.
Okay now back to business, the "Odin" program(version3.07) I believe, don't quote me, does NOT work on a Mac at least to my knowledge.
If you have a windows xp computer please get on there and download the Odin software then go to here, http://samsung-updates.com/device/?id=SGH-I747, and then while that is downloading go to the AT&T Galaxy Slll Android Development section, not the "Original" section, and download the [Samsung Galaxy S3 QCOM ToolKit v2.3] and install it.
After it's started and it asks to update type, yes, and press enter. After that is finished press the number, 1(one), for AT&T SGH-I747 and then enter. If you have the drivers installed already skip this step, if you don't have the drivers installed press the number 1(one) and install.
Afterwards you can press the number 8(eight), Download, Extract + Flash Stock ROM via Odin, then after entering the #8 section select #2.
In this section it asks you to put the Stock ROM into, put_odin_images_here, which can only hold one file at a time.
Go to your downloads folder, on your PC, and drag the Stock ROM file onto the desktop. Next go to my computer and locate your Samsung Galaxy Slll QCOM program files, check where you downloaded it to, and then click on the folder to open it.
You should see something like...
backups
drivers
INPUT
mods
OUTPUT
etc.
Drag the Stock ROM to the put_odin_images_here folder and then go back to the Galaxy Slll QCOM program.
Type the letter, R, to refresh the list and it should show 1 file found and also FILE NOT FOUND(ignore this message).
It asks if the file you put into the folder is the one you want to extract. Type, yes, and press enter.
After it's finished it will put the extracted file into OUTPUT, I believe =P, and then you return to the QCOM program.
Go back to the main screen and then press number 8(eight) then enter and then press number 4(four), Flash Stock ROM via odin, press enter.
Press the number 1(one) and let it do it's thing. If it doesn't want to enter your custom recovery then skip this step.
Afterwards press the number 2(two), Flash Stock ROM via odin, and then follow the steps.
If this doesn't work for you consult with the original poster of the ROM in a private message and let him know that you screwed up and that it's your fault for not reading and you would really appreciate his help.
I'm sorry I seem mean about all of this by the way it's nothing personal and in fact I was treated much worse back in the Sprint Epic 4G Touch forums way back when and I learned a lot from their criticism.
Keep learning the terminology and skills and you'll get it down soon enough.
A bit of advice as well...don't flash a ROM that isn't the same O.S. level as your stock phone. (Ice Cream Sandwich stock/ ICS custom ROM)
Maybe it's because you tried flashing Jellybean 4.1.4.
Sent from the future on my Galaxy S4 using Tapatalk 3
For the most of us upgrading to 4.3 goes without a hitch but for a small handfull of users they experience problems that should not exist given that they have followed the steps verbatim. I had UID issues, fc issues a plenty and with some research I developed this method to fix my problem.
A number of other users have had these issues and others that I have helped either privately or on a forum and this method also worked out for them too so I thought id share it here for anybody else to try.
Basically my line of thought is that the last 412 update also included core system updates that prepares the handset for 4.3 but at the end of the day i dont know why the success but it has helped
Bear in mind that this will only work if you have MJ9 installed or older, newer bootloaders wont allow downgrading.
First download all the files below on your pc and make sure the samsung usb drivers are installed. Also download the rom you wish to flash.
1) put phone in download mode (vol down + home + power) and use odin pda tab to flash the blpatch
2) use pda tab in odin to flash dmg1
3) boot phone to setup screen
4) put back in download mode and flash the MJ5 BL with the pda tab
5) flash TWRP with pda tab
6) boot to TWRP (vol up + home + power) to flash rom.
7) hit thanks or buy me a beer
Odin Http://goo.gl/hW8vGr
Blpatch http://d-h.st/7me
Dmg1 http://d-h.st/s9I
Twrp Odin Http://goo.gl/SSyv53
MJ5 BL Http://goo.gl/95w2ev
Thanks goes to @T.G.A @morr_1228 @ecsjjgg and a few others I cant find right now for running the process and basically confirming it worked for them too
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.
hello master developer
This is my first post here. Right away, I have a Samsung Tab3 8.O smt311 with the state has been my roots and replace cmll Rom. I want to restore to official firmware using Samsung Kies But a long time to connect your device for hours still looking device. Please Master solution.
Don't use Kies
Syaiffurroizt said:
hello master developer
This is my first post here. Right away, I have a Samsung Tab3 8.O smt311 with the state has been my roots and replace cmll Rom. I want to restore to official firmware using Samsung Kies But a long time to connect your device for hours still looking device. Please Master solution.
Click to expand...
Click to collapse
Hey, @Syaiffurroizt
You're better off using Odin to restore the stock image for your phone. May I ask what region you are in? Reply in 2-letter format so I can give you the right advice. (example: My region is US [United States]).
Don't use Kies. It will detect root and refuse to install or restore backups. Odin can be found here. Typically, on Samsung devices, in order to access Bootloader, as you reboot the phone, hold Volume Down and Home while it reboots. It should take you into download mode. Ignore the warning and Continue.
Before you connect your SM-T311 to your PC, make sure the drivers work (If you have Kies installed you can skip this step).
Connect your USB cable AFTER you open Odin. It should display a COM:## added! near the top of the window.
Put the md5 sum for your stock ROM in the PDA section of Odin. ( This is where I need to know your region so you are getting the right software)
PLEASE BACK UP ALL YOUR DATA, AS THE NEXT STEP WILL SURELY WIPE YOUR EXISTING ROM ALTOGETHER, INCLUDING INTERNAL MEMORY. I SUGGEST EJECTING ALL EXTERNAL STORAGE PRIOR TO REBOOTING YOUR PHONE.
Now check off F. Reset Time, Auto Reboot, and hit Start. Avoid interrupting the flash process as you can brick your device, rendering it useless. I suggest you use AC power even if you are using a laptop for a safety net.
When it's done, you will have your stock ROM back and original (factory) binary, too.
Please hit thanks if this works for you.
Messed up good this time.
I had just upgraded to Android 10 and after twice failing to install TWRP I thought, "Oh yeah I can patch AP with Magisk."
Sure enough there was a new thread just for that.
Only problem is now I can only flash BL, CP or CSC (home too). And only individually. AP will fail at system.img or Vendor.img
Any 2 or more will fail. Only get a pass (except AP of course) on their own
Bootloader is unlocked, OEM unlocked and model is SM-A705MN CHO
Latest firmware was fresh install (working just great before my antics) Android 10
Any help would be appreciated. It's been over 24 hours and I don't think I can do this without help. I've tried every Odin patched or not.
Heimdall? Please no more of that. Jodin? umm not so good.
Thanks
*Phone will go to normal download mode after any of the 3 available successful flashes if I immediately boot back into download mode after the pass. Otherwise I have the update error smart switch screen.
**I had also recently read somewhere that this may be a vaultkeeper issue. I can't find where I saw this! There was a post that had the exact same issue. I apologize for having a terribly slow laptop and patience... what's patience?
I tried again and it worked.
Maybe it was a low charge issue.