Related
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop
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.
I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
roll-back said:
I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
Click to expand...
Click to collapse
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Flashing Kernel did not help
cnote74 said:
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Click to expand...
Click to collapse
I run Linux and don't really have access to a Windows box and have been using heimdall to flash things. When you said
"Try to odin the stock firmware"
Click to expand...
Click to collapse
is that the same as trying to loading a kernel image and then going to recovery before it fully boots? If so, I tried that with the following command using the image I downloaded from sammobile.com. This is the command that I ran:
Code:
heimdall flash --kernel KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 --verbose
That resulted in the same as when I tried to flash a new CWM recovery. It doesn't allow me to access the recovery, it just boots and shows the white Samsung logo and hangs there till you pop the battery & remove the USB cable.
If what you are suggesting is something different than the flash that I did with the image from sammobile.com, please let me know. This is my first attempt to fix something like this. Many many thanks.
OK, I did search and found nothing. So, I need to ask this somewhere, hopefully this is the place. The similar threads search did not seem to help much.
I have a Tab S 8.4 WiFi. I rooted it and was running Cyanogen 12. I noticed the TWRP 2.8.3.0 update, so I went to install it. TWRP manager kept crashing, so I went to the TWRP site and downloaded the SM-T 700 klimti wifi img file. I used Flashify to flash this, as I have done numerous times. I wish I'd extracted and flashed the zip in TWRP, but I did not. Everything acted normal but when the tab went to boot up it got to the Black screen that announces Samsung Galaxy S, SM-T700, Powered by android. This was it. It flashed this screen constantly every second or so. Non stop. There was nothing any button combination would do. Except it will go into download mode. Nothing else. No hard reset, nothing. Download mode is it. I spent lots of time looking at various tutorials to see what I'd missed, nothing but download mode. So, I had Odin on the computer and the latest firmware from SamMobile, so I figured I could start over and get the tablet functioning. I've used Odin a fair amount before, including the original Galaxy, S III, S4, so I'm not unfamiliar with the process. I've yet (until now) had the privilege of having a wreck like this one.
So, Odin acts like it is doing its thing, runs through all the steps, says at the end Pass and all threads succeeded, none failed. At the end of the Odin process the tablet acts like it is booting. Up comes the Samsung name with the Bluish sparkly oval along with the standard Samsung tones we hear heading into the boot. That is as far as it goes. The blue and pink colors fade out and I am left with a black screen with SAMSUNG in the middle. Again, no button combination except download mode works at all. It just stays there. Pass showing proudly on the Odin screen (EDIT: I left it there for an hour or so to see if boot would finish before disconnection). I downloaded and tried flashing all of the various firmwares, same result. I even let the battery drain to zero hoping that would shut it off. It seemed to, but the results were the same, only the download mode combination will do anything. The power button starts up the phone in an initially normal manner, but it goes right to SAMSUNG in a black screen.
EDIT 2: I used the Cellular South firmware, saw nothing else US and thought I remembered reading this was what worked here.
There is likely user error here (and realize I might kick myself in the end...Oh wait, I already have), but I've run in circles enough to realize I'm probably doing the same sequence with the same error and I not able to see what it is.
Does anyone have any idea what is wrong or how to fix this? I hope it is fixable. I had hope since download and Odin at least go through the motions. I would greatly appreciate any advice, suggestions, or help. Thanks in advance.
Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?
DUHAsianSKILLZ said:
Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?
Click to expand...
Click to collapse
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.
SteveC485 said:
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.
Click to expand...
Click to collapse
What I mean is to flash twrp with odin then flash zips with twrp. If you cant reboot into recovery, if you installed adb then yoi can do adb reboot recovery.
I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.
senel said:
I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.
Click to expand...
Click to collapse
Thanks. When Christmas stuff winds down, I will give Odin a go. Thanks to both of you who answered. Merry Christmas.
OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.
SteveC485 said:
OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.
Click to expand...
Click to collapse
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.
DUHAsianSKILLZ said:
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.
Click to expand...
Click to collapse
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.
SteveC485 said:
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.
Click to expand...
Click to collapse
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
DUHAsianSKILLZ said:
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
Click to expand...
Click to collapse
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
DUHAsianSKILLZ said:
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
Click to expand...
Click to collapse
Thanks, that's what I thought.
For whatever reason, this time the power, home, and volume up combination booted me into TWRP. Restored a backup and everything is up and running normally (at least so far).
I'm perfectly willing to admit error,but don't quite know where my error came in. I would swear I used the power, volume up, and home combination when I hit the download mode. But maybe not. I don't know why it worked now, except that I was inadvertently hitting the wrong combination, thinking I was doing it right. I remember thinking the first time it went to download mode, that I just did it wrong and used the wrong volume key. Thought I was more careful the succeeding tries.
At any rate thanks for the help. I will remember this particular lesson for a while .
hard brick
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...
faztecnyk said:
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2838473
DUHAsianSKILLZ said:
Try this http://forum.xda-developers.com/showthread.php?t=2838473
Click to expand...
Click to collapse
Thanks.. but I said hard brick and not soft brick..
SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
A lot of Tab S owners have had issue with TWRP 2.8.3. There is another thread on it. I installed 2.8.3 with Odin and it was pretty wonky. Went right back to 2.8.1.
If none of the methods worked for anyone try this. If your tablet keeps trying to boot into twrp or stuck at the galaxy tab s screen try this if you cant boot into download mode.
Let completely die. Then put it in the charger and quickly press the combination of buttons to get into download mode. That should over ride booting into twrp. another way is to plug it into your computer and try different combinations of buttons.
I have the samsung galaxy tab s 8.4 and I rooted it a few days ago and I thought to myself lets install a custom recovery, but before I did that I backed up my stock kernal and my stock recovery through flashify, also im on stock firmware, after I backed those things up I installed twrp 2.8.3.0 and I booted into recovery to back up my rom and data just in case I soft bricked my tablet like I used to do on my nexus 7, when trying to boot into twrp it went in to boot loop I have tried all button combination I know and have seen in this thread but none works except for going into download mode. I dont know if I should flash an older version of twrp and see if it works or should I install stock firmware on my device and im not sure what version of odin I should use if I flash a older version of twrp. The version I used to root my tablet is 3.07 of odin.