Hi everybody. I was attempting to rollback by my Galaxy Tab S 8.4 (SM-T700) from Lollipop to KitKat so that I could root it. I was following the steps in this guide:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
I followed the steps with no problems until the end. I put my phone in Download Mode then plugged it in to the computer. Odin recognized it just find and I hit Start. Then it failed. I didn't screen capture the original fialure but I did a later one and it also failed, I have attached that one. Once it failed and my phone rebooted I got a screen that only says "Firmware upgrade encountered an issue. Please select mode in Kies & try again." I can't turn the tablet off via the power button and nothing else seems to have an effect. I ran Kies and first I get an "unsupported device" message, didn't get that before. Following the steps for recover, I go to Tools >> Emergency Firmware Recovery, the List of devices requiring emergency recovery is empty, my device is not there. Going by the guide, if I had a recovery code I could attempt via that, but I don't have the code. You only get a code from the original computer that tried to updated the tablet via Kies and failed. But since wasn't using Kies I don't have the code.
I did find one thread with a similar problem and I followed the steps there but I still get a fail when I run Odin.
http://forum.xda-developers.com/galaxy-tab-s/help/firmware-upgrade-encountered-issue-t3019438
I was able to get to the battery and unplug it and boot into Download Mode again and I tried flashing back to stock again and failed again (see attached image). I am still able to get into Download mode by unplugging the battery and booting into that but every time I try flash with Odin I get a failed message.
Questions:
1) Does someone have a recovery code so I can attempt via Kies? I've searched pretty thoroughly on the internet and couldn't find any.
2) Is there something I'm missing when I flash the new firmware via Odin? Or something else I can try to restore to any working version?
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didn't read your entire post because the solution to this and reason why it happens has been posted countless times.
I'm guessing it fails at hidden.img?
Boot into recovery and wipe cache.
It should then boot normally.
ashyx said:
I didn't read your entire post because the solution to this and reason why it happens has been posted countless times.
I'm guessing it fails at hidden.img?
Click to expand...
Click to collapse
Thank you for your post and I have seen that issue mention here and other places before. Looking at the picture that I posted, the last things that Odin reported before failing are:
system.img
__XmitData_Write
Complete(Write) operation failed.
And that's all. hidden.img was never mentioned in the log so I don't know where in the process that file is. If it is write after system.img then I guess that is where it failed?
I did try to boot into recovery mode just to make sure. Using Home + Volume Up + Power just brings me back to the "Firmware upgrade encountered an issue. Please select mode in Kies & try again" screen again. I tried multiple time to make sure I wasn't screwing up the button pushing, no change. The only thing I can boot into other than that is the Download Mode and like I said, every time I tired to flash with Odin I get more failures.
Any other thoughts?
Are you sure you are using AP to flash the firmware?
Can you post your device model number and the firmware you are flashing.
Also a screen shot of odin when it fails.
ashyx said:
Are you sure you are using AP to flash the firmware?
Can you post your device model number and the firmware you are flashing.
Also a screen shot of odin when it fails.
Click to expand...
Click to collapse
The OP has a screenshot with most of that information you are asking for. It shows that I am using AP to flash and it shows the firmware I used to flash and it shows everything in the log up until it fails. I am using a Samsung Galaxy Tab S 8.4 (no carrier) SM-T700. I did try a few other firmware versions after but I run into the same problem each time. I can get the list of those later today.
Thanks!
mrcherrio said:
The OP has a screenshot with most of that information you are asking for. It shows that I am using AP to flash and it shows the firmware I used to flash and it shows everything in the log up until it fails. I am using a Samsung Galaxy Tab S 8.4 (no carrier) SM-T700. I did try a few other firmware versions after but I run into the same problem each time. I can get the list of those later today.
Thanks!
Click to expand...
Click to collapse
There is no screenshot it doesn't work.
mrcherrio said:
Hi everybody. I was attempting to rollback by my Galaxy Tab S 8.4 (SM-T700) from Lollipop to KitKat so that I could root it. I was following the steps in this guide:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
I followed the steps with no problems until the end. I put my phone in Download Mode then plugged it in to the computer. Odin recognized it just find and I hit Start. Then it failed. I didn't screen capture the original fialure but I did a later one and it also failed, I have attached that one. Once it failed and my phone rebooted I got a screen that only says "Firmware upgrade encountered an issue. Please select mode in Kies & try again." I can't turn the tablet off via the power button and nothing else seems to have an effect. I ran Kies and first I get an "unsupported device" message, didn't get that before. Following the steps for recover, I go to Tools >> Emergency Firmware Recovery, the List of devices requiring emergency recovery is empty, my device is not there. Going by the guide, if I had a recovery code I could attempt via that, but I don't have the code. You only get a code from the original computer that tried to updated the tablet via Kies and failed. But since wasn't using Kies I don't have the code.
I did find one thread with a similar problem and I followed the steps there but I still get a fail when I run Odin.
http://forum.xda-developers.com/galaxy-tab-s/help/firmware-upgrade-encountered-issue-t3019438
I was able to get to the battery and unplug it and boot into Download Mode again and I tried flashing back to stock again and failed again (see attached image). I am still able to get into Download mode by unplugging the battery and booting into that but every time I try flash with Odin I get a failed message.
Questions:
1) Does someone have a recovery code so I can attempt via Kies? I've searched pretty thoroughly on the internet and couldn't find any.
2) Is there something I'm missing when I flash the new firmware via Odin? Or something else I can try to restore to any working version?
Thanks!
Click to expand...
Click to collapse
Like ashyx, I didn't read your entire OP because it seems that all you really want to do is root your tab. I apologize if I am incorrect. But IF this is the case I rooted my SM-T700 when it was LP 5.0.2 by using KingRoot. I know ashyx prefers download/adb/odin method, but I no longer have a PC and had no alternative than use an on-device method. I settled on KingRoot and everything went smoothly...oh, yeah, if you use KingRoot, at least the version I used (link below), you'll see a scary "device incompatible" or some such message. Ignore it [emoji6]
I also provide in that link an app to convert the super user app to SuperSu, if you wanna', and even the files to install v4a, if you wanna' [emoji6] Just flash the
ViPER4Android-supolicy.zip then the LolliViPER_TAB_S.zip
TiTiB (tweak it 'til it breaks)
Galaxy Tab S | SMT-T700 | klimtwifi
BlissPop 5.1.1 v4.0
---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------
TiTiB said:
Like ashyx, I didn't read your entire OP because it seems that all you really want to do is root your tab. I apologize if I am incorrect. But IF this is the case I rooted my SM-T700 when it was LP 5.0.2 by using KingRoot. I know ashyx prefers download/adb/odin method, but I no longer have a PC and had no alternative than use an on-device method. I settled on KingRoot and everything went smoothly...oh, yeah, if you use KingRoot, at least the version I used (link below), you'll see a scary "device incompatible" or some such message. Ignore it [emoji6]
I also provide in that link an app to convert the super user app to SuperSu, if you wanna', and even the files to install v4a, if you wanna' [emoji6] Just flash the
ViPER4Android-supolicy.zip then the LolliViPER_TAB_S.zip
TiTiB (tweak it 'til it breaks)
Galaxy Tab S | SMT-T700 | klimtwifi
BlissPop 5.1.1 v4.0
Click to expand...
Click to collapse
The link, d'oh!
https://drive.google.com/folder/d/0B8tvUtXZ--2aRWtLWVZwTlRIUjA/edit
TiTiB (tweak it 'til it breaks)
Galaxy Tab S | SMT-T700 | klimtwifi
BlissPop 5.1.1 v4.0
Odin Fail
ashyx said:
There is no screenshot it doesn't work.
Click to expand...
Click to collapse
Hmm... guess I should use a different image server. So according to XDA, and I understand, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Here is a link to the screen shot, you just have to remove all the spaces. I know it's a hassle but I appreciate the time!
http: // i.imgur . com / d6GVINx . jpg
TiTiB said:
Like ashyx, I didn't read your entire OP because it seems that all you really want to do is root your tab. I apologize if I am incorrect. But IF this is the case I rooted my SM-T700 when it was LP 5.0.2 by using KingRoot. I know ashyx prefers download/adb/odin method, but I no longer have a PC and had no alternative than use an on-device method. I settled on KingRoot and everything went smoothly...oh, yeah, if you use KingRoot, at least the version I used (link below), you'll see a scary "device incompatible" or some such message. Ignore it [emoji6]
I also provide in that link an app to convert the super user app to SuperSu, if you wanna', and even the files to install v4a, if you wanna' [emoji6] Just flash the
ViPER4Android-supolicy.zip then the LolliViPER_TAB_S.zip
Click to expand...
Click to collapse
Yes, the end result is to root my tablet but I'm broke at a stage where nothing is working. In summery, I can no longer do anything other than enter Download Mode and try to flash via Odin, which fails every time, or boot into the "Firmware upgrade encountered an issue. Please select mode in Kies & try again" screen which Kies is no help. I cannot boot into recovery mode. For more details see the attached screen shot of Odin as well as the OP. Thanks for the help though and I'll check out your process once I have a somewhat working tablet, hahaha!
mrcherrio said:
Hmm... guess I should use a different image server. So according to XDA, and I understand, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Here is a link to the screen shot, you just have to remove all the spaces. I know it's a hassle but I appreciate the time!
http: // i.imgur . com / d6GVINx . jpg
Yes, the end result is to root my tablet but I'm broke at a stage where nothing is working. In summery, I can no longer do anything other than enter Download Mode and try to flash via Odin, which fails every time, or boot into the "Firmware upgrade encountered an issue. Please select mode in Kies & try again" screen which Kies is no help. I cannot boot into recovery mode. For more details see the attached screen shot of Odin as well as the OP. Thanks for the help though and I'll check out your process once I have a somewhat working tablet, hahaha!
Click to expand...
Click to collapse
I'm stepping aside now. This is beyond my experience/knowledge. Good luck, you'll get there soon...
TiTiB (tweak it 'til it breaks)
Galaxy Tab S | SMT-T700 | klimtwifi
BlissPop 5.1.1 v4.0
That error is being caused by a break in the flashing process. It could be a bad cable, bad usb port or just corrupt firmware or simply the wrong firmware.
First thing I'd do is change cables and usb port.
If you get the same error download a different firmware. Ensure it is compatible for your device region.
ashyx said:
That error is being caused by a break in the flashing process. It could be a bad cable, bad usb port or just corrupt firmware or simply the wrong firmware.
First thing I'd do is change cables and usb port.
If you get the same error download a different firmware. Ensure it is compatible for your device region.
Click to expand...
Click to collapse
Thanks, I'll check out the cabel issue first. I know I looked up my device region before my first attempt but I didn't write it down nor do I remmeber what it was. When I looked at the list of all the regions US wasn't on there (or I completely missed something). Do happen to know what region is common for tablets sold in the US? I bought it on Amazon actually from Amazon, not a 2nd party. If not I've got a couple different firmwares downloaded I'll just try the original one then move on form there if I have to. Thanks and I'll let you know how it goes!
US is Cellular south, region code XAR.
I believe that US is called "cellular south" in the firmware.
ashyx said:
That error is being caused by a break in the flashing process. It could be a bad cable, bad usb port or just corrupt firmware or simply the wrong firmware.
First thing I'd do is change cables and usb port.
If you get the same error download a different firmware. Ensure it is compatible for your device region.
Click to expand...
Click to collapse
Everything is working again! Thanks ashyx for the help!!
mrcherrio said:
Everything is working again! Thanks ashyx for the help!!
Click to expand...
Click to collapse
The solution?
ashyx said:
The solution?
Click to expand...
Click to collapse
I replaced the cable and made sure I had the a new copy of the firmware at the same time. So a combination of those two.
Related
Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance
What is your Current android version ?
Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?
Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone
Glad its sorted out. I assume no issues now ?
Ok guys, I was an idiot and got a little greedy and opened a thread saying update your s4 mini LTE to an OFFICIAL 4.4.2 kitkat. Without even checking the comments I just downloaded and followed the instructions. It was a 4.2.2 "upgrade" and it didn't work.. Used Odin 3.09. and it showed the error "FAIL! (Ext4)"
Now my phone is stuck in download mode with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Well, that would all be nice if I could. Kies doesn't let me connect my phone to it, when I try Emergency recovery it doesn't show it in the list of devices, initialisation is not available for GT-19195 (??) (it's the option where i type in my phone model and serial number).
I can't put the phone itself into recovery mode, pressing volume up, home and power buttons, so that option is also out.
I have no idea what else to do right now, and I would appriciate any help you guys can provide.
What do I do to get my phone working again?!
Thanks in advance.
iwanvs said:
Ok guys, I was an idiot and got a little greedy and opened a thread saying update your s4 mini LTE to an OFFICIAL 4.4.2 kitkat. Without even checking the comments I just downloaded and followed the instructions. It was a 4.2.2 "upgrade" and it didn't work.. Used Odin 3.09. and it showed the error "FAIL! (Ext4)"
Now my phone is stuck in download mode with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Well, that would all be nice if I could. Kies doesn't let me connect my phone to it, when I try Emergency recovery it doesn't show it in the list of devices, initialisation is not available for GT-19195 (??) (it's the option where i type in my phone model and serial number).
I can't put the phone itself into recovery mode, pressing volume up, home and power buttons, so that option is also out.
I have no idea what else to do right now, and I would appriciate any help you guys can provide.
What do I do to get my phone working again?!
Thanks in advance.
Click to expand...
Click to collapse
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery
I've had this issue myself before and found flashing a cwm recovery via Odin then adb sideload either a custom or stock rom generally fixes the issue.
Hope all work's out for you
Sent from my GT-I9195 using Tapatalk
I have managed to find a 4.2.2 stock ROM from ny region, it's for the Telenor network, I am not on it but my carrier is another, although that does not seem to be a problem. Flashed it through Odin, v3.09, and I'm happy to say I'm writing this from my phone!
To answer your question, yes, the only thing i was able to start download mode on my phone, just turning it on, it went straight to that. Also, I had to wipe cache from recovery to stop it from looping the samsung logo and also had to do a factory reset & delete everything once i got past samsung logo loop. It's working as inteded now, and well, I guess a new fresh start is not that bad.
Thanks for your ideas guys.
GT-I9195 bRICKED SAME ISSUE
superkoal said:
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery
Click to expand...
Click to collapse
Hi i have the same problem. worried the phone is soft bricked. cant do any thing now. What do u mean by "try flash cwm recovery" how sould i do it any links would be helpful...
Please please help me...
Thanks...
---------- Post added at 03:52 PM ---------- Previous post was at 03:43 PM ----------
superkoal said:
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery
Click to expand...
Click to collapse
Scopewiz said:
I've had this issue myself before and found flashing a cwm recovery via Odin then adb sideload either a custom or stock rom generally fixes the issue.
Hope all work's out for you
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
Hi how do u do the cwm recovery andadb sideload the custom or stock rom... i am very new to this tech... please guide and help
Thanks & regards
Jeetesh
---------- Post added at 04:00 PM ---------- Previous post was at 03:52 PM ----------
iwanvs said:
I have managed to find a 4.2.2 stock ROM from ny region, it's for the Telenor network, I am not on it but my carrier is another, although that does not seem to be a problem. Flashed it through Odin, v3.09, and I'm happy to say I'm writing this from my phone!
To answer your question, yes, the only thing i was able to start download mode on my phone, just turning it on, it went straight to that. Also, I had to wipe cache from recovery to stop it from looping the samsung logo and also had to do a factory reset & delete everything once i got past samsung logo loop. It's working as inteded now, and well, I guess a new fresh start is not that bad.
Thanks for your ideas guys.
Click to expand...
Click to collapse
Hi dude,
please share the link and how to go about it as i am struck with th same issue... tensed & worried please help
Thanks & Regards
s4 mini bricked
Hi i have problem i tried to root my phone(cwm recovery i cant post link yet ) but this is only for android 4.2.2 jelly bean but my is 4.2.2 kitkat and i root the phone and i folowed the steps but when i try to power up the phone in top left corner it says set waranty bit:karnel and after that i hear samsung power up sound and then just black screen i tried everything can anyone help me please?
the guy 1950 said:
Hi i have problem i tried to root my phone(cwm recovery i cant post link yet ) but this is only for android 4.2.2 jelly bean but my is 4.2.2 kitkat and i root the phone and i folowed the steps but when i try to power up the phone in top left corner it says set waranty bit:karnel and after that i hear samsung power up sound and then just black screen i tried everything can anyone help me please?
Click to expand...
Click to collapse
Shouldn't be a problem if you use the arco recovery wipe cache, warranty bit kernel means h that you're using different kernel from the original that came with the phone, probably you have tripped Knox 0x1 voiding warranty, you could flash an kk kernel and will be fine
Frends please help i put bad TWRP via terminal and now I cant go to download mode so can some solutions for me
Lybross said:
Frends please help i put bad TWRP via terminal and now I cant go to download mode so can some solutions for me
Click to expand...
Click to collapse
I've never had this sort of problem and I am no expert but this is what I would try. The good news is it should be recoverable, lets hope one of the experts sees this. You really need to give more info!
If in a boot loop you may be able to get into download mode by just pressing the vol down & home key (not power as you are already powered up). If this doesn't work try all other key combos as you need to get out of the current reboot mode into something else.
If that doesn't work or you are not in a bootloop then use ADB to see if device shows up, if it does, then "reboot bootloader"
If that doesn't work make or buy a jig, that will allow you to set download mode.
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!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.
mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this
erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/
erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video
erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet
Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?
mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.
Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.
erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.