Related
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 everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
dinomut101 said:
Hello everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
Click to expand...
Click to collapse
Hi, we'll walk you through it.
First off, use the PF4 firmware from here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Be sure to allow it to complete and it should reboot. If you continue to get NAND write errors you may need to try different ports on your PC or different cables.
Let us know when that completes for you.
Okay, so i just followed the steps on how to unlock and root my phone and all was going well as i followed all the steps to the letter, however at the end when i tried to reboot my phone it got stuck on the LG screen and will not load up.
I found a similar post on this forum here: https://forum.xda-developers.com/lg-g7-thinq/help/g7-doesnt-boot-flashing-modified-boot-t3872445. However in their case the phone ran out of charge and they were able to get into download mode, my phone however is on full charge so will take ages to die and i cannot seem to access download mode. In the current state the phone is completly unresponsive without me being able to turn it off.
The root guide i use this this one: https://www.theandroidsoul.com/lg-g7-root/ and the .img was also sourced from the link on that site.
Idealy I'd like help to fix this issue continuing with the root, but am happy to reset the phone if that is easier and give up rooting the phone.
For me it sounds like wrong boot.img. I mean from other version of firmware than you have.
If you unlocked bootloader, then you have LMG710EM, but...
What version of firmware you have?
For most of EM variant, newest firmware is v10q, so first try to flash img for q version.
https://drive.google.com/drive/folders/1NtbfxAbYLeQNryPg0odgLa8hBgabrH3j here you have boot images by LameMonster82, and for me it works.
There are two versions of boot.img. Original, and patched. If you want to have root, then flash patched boot.img
So if you don't know which version you have, then flash boot for v10q, if it doesn't work, then v10p etc etc.
Juat plugg the usb cable in the phone.
Hold power and - down for about 8 sec. When it reboot release power. And just hold down - (vol minus). It should Boot into download mode. Timing is everything so keep.trying untill u get it.
Also flash the correct Boot img.
Hello
I Bought from Ebay an S9 , that wasn't working when i recieved it.
I managed to flash it with the originals Samsung firmwares but the phone keeps rebooting all time .
It does show the Samsung logo for 1sec just when the phone is connected to an wall plug.
Otherwhise the phone doesn't turn on.
I can access to the download mode but not to the recovery mode.
I tried to flash TWRP but it says frp lock on
Could someone help me
Best Regards
Dear AcapulcoNueve,
I don't know if this is sufficiently related to your problem, but perhaps you could "build up" your s9 step by step, using first of all Odin to re-flash your BootLoader.
I would start by flashing your BootLoader by downloading it on a site like this one: androidfilehost.com/?w=files&flid=287896 and using it in Odin (BL). You never know.. perhaps that would already do the trick?
It's also the procedure I've used to get my s9 going again after it was totally stuck in the bootloader after flashing an image (logo.jpg) which was too large. (Couldn't even get into recovery mode!)
So:
1. Download Odin latest version
2. Download the right BL file for your s9
3. Start Odin in administrator mode
4. Put your phone in "Download Mode" and connect it to your (WINDOWS) computer
5. Select the BootLoader file within Odin using the <BL> button
6. Start the flashing procedure (and if you want to get into your TWRP, immediately when your screen goes black press <Bixby> + <Volume Up> + <Power> buttons).
Hope this helps..
Which CSC did you flash? Make sure you're not flashing HOME_CSC which doesn't clear data. If you flashed HOME_CSC and it's boot looping,
I had this FRP LOCK ON issue on my galaxy s7 edge way back when i tried to flash a rom with oem unlock enabled (or maybe disabled) i forgot about that detail.
what i did was reflashed the same firmware it was running on before, that fixed it.
I also remember a few versions of Odin werent working and that included the latest version at that time,
I tried different versions and i remember the older version odin worked. Hope this helps!
Hi there,
first of all, sorry for my bad english.
I want to remove the Stock ROM from my Tablet (Samsung Galaxy Tab S4 | SM-T830) and install something else (https://www.getdroidtips.com/android-12samsung-galaxy-tab-s4/).
For some Reason Samsung forced me to do a factory reset to unlock the bootloader (maybe I did it wrong, but now it happened, so it is how it is). Now the OEM Unlock Options says "Bootloader is already unlocked", but when I go into Download mode, I have multiple Problems:
1.: When I enter download mode by Booting into Recovery (adb reboot recovery) and choose "reboot to bootloader", OR by entering it directly using "adb reboot bootloader", I dont get the Warning Screen so I get into download mode directly.
2.: When entering Dowload mode as descibed in problem 1, I also dont get the informations at the Top left, I only see the Download Icon on a blue background but when restarting the tablet and holding Volume Up and Volume Down simuntainuasly, it will show the warning (in the correct cyan colors) and in the next step it shows me those status informations at the top left.
3.: However, regardless to how I get into download mode, the colors of the download mode screen will change to a blue filter version after one second. but I did never activate any blue filter on the device, and on any other device, the colors are displayed correctly.
4.: Any instalation with Odin3 failed on the device, regardless to how i got into download mode
In any online article I read, noone has any problems with installing something when in download mode.
Also, the KG-Status is displayed as "checking, I dont know if this is good or not.
What am I doing wrong, why can't I install anything on the device?
what is wrong with download mode? post a picture.
drivers installed correctly? check in windows device manager.
what does not work with Odin? what error message?
First of all, thank you for your reply!
1.: The Picture shows that the is something wrong with the Download mode of the Tab S4, because the Colors are not being displayed correctly (as you can see, the colors of the other devices are much more cyan), and I would not have mentioned that if the device would just be unable to show colors correctly, but in the Warning before the Download mode, the Colors are displayed as they are on the other devices, so the eventually the device wants to tell me something, but I dont know what.
2.: Well, I am pretty sure that the drivers are installed Correctly, because Flashing a Galaxy Tab S2, Galaxy S8 and Galaxy S5 worked perfectly with the same driver.
3.: I'l attach a Screenshot of Odin.
ALso, what does "KG STatus: Checking" mean? Is it the reason for the problem, or is it good? On the Web I could only find "Kg Status: Locked" and "KG Status: Unlocked". should I unlock it? If yes, how?
you say any installation with Odin3 failed. you are trying to flash TWRP.
try to flash something different.
https://topjohnwu.github.io/Magisk/install.html#instructions
not sure about the display, though.
Well, I have a porblem with the Program that is mentioned in the Guide you linked, Frija asks for a CSC, and I dont know what I have to enter there, I only know that the device is a SM-T830/gts4lwifi.
CSC is region code
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Well, if RMM/KG state is prenormal you would see message "Only official released binaries are allowed to be flashed"
Anyway, try to flash official ROM and wait for KG state while device is connected to internet.
you can download according to your region from https://samfw.com/firmware/SM-T830
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
Setting the 7 days back works
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
try this: https://forum.xda-developers.com/t/...-twrp-and-magisk.4059227/page-2#post-88134465