Related
so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
What happens when you try to go into download mode from Frostys reboot menu?
Maybe flash the UVALH2 deodexed stock rom and try odin again.
But use either the regular fw from sammobile or root66 from MrRobinson.
Where did you get the fw you've been trying to flash?
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
boot-insecure-tmo-t999uvalem-cwm
Is this just a kernel? You had said you were trying to odin back to stock, but this looks to be a cwm flashable file which I doubt is gonna work in odin.
Sent from my SGH-T999 using xda app-developers app
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
nicky9door said:
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Aerowinder said:
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
Click to expand...
Click to collapse
It wasnt ODIN that wiped my storage. It was running the factory reset from the Samsung 3e Recovery (which I got after I used ODIN to go back to stock)
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Getting into recovery can be tricky as there's a short window where you have to release the buttons. The most successful way for me is, with the phone off, hold home+power+vol up. When you see the Samsung logo, look at the top of the screen for a line of blue text. If you see this line, immiediately let go of all buttons.
Another option (might be a longshot) would be to try using ADB during the CodenameAndroid (CNA) boot animation. Search for ADB standalone to get the files you need. While your phone is on the CNA bootscreen, plug it intop your computer and try running "adb devices" from the command line (you'll need to be in the same folder as the ADB executable). If you see a serial number, then try running "adb reboot recovery" which should get you into recovery mode
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Did you remember to wipe everything including factory reset in recovery?
If you're already rooted just press reboot recovery in goo manager. Otherwise try what the above post says.
Sent from my SGH-T999 using xda app-developers app
ishred11 said:
so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
Click to expand...
Click to collapse
Did you make a Nandroid (Backup) of your ROMS? Always make a Backup before flashing anything on your phone. If the solutions the users have posted doesn't work, then USB JIG can be used as a last resort. I would also like to let you know some kernels corresponds to some ROMS. For an example, Frosty is based on TW (Touch Wiz) and can only be flashed with kernels that supports Touch Wiz. Flashing Ktoonzer kernel with, for an example, CM10 would only result in the phone not being able to boot due to CM10 ROM not supporting Touch Wiz. Make sure you flash a kernel that supports the ROM and before any flashing, make a backup via recovery.
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
I went through the normal procedure of installing a new ROM, I wiped w/factory reset, got hit with a "status 7" error. I looked it up and it's apparently a problem with conflicting recovery manager files. That makes sense because I have CWM recovery and it asked me to install TWRP. I guess you can't have both?
I followed a tutorial explaining how to edit the userscript file to bypass the error and it seemed like it was going to install at first but I still got hit with it. Now my computer doesn't recognize my s3 (d2spr) so I have to put the files on an external microSD. I tried to restore from CWM but it wouldn't let me. I'm pretty new to this stuff so I'm not sure how to proceed from here.
Your best option is Odin back to stock and start over again.
Sent from my SPH-L710
Im having the same issue. Can someone please help. I tried flashing the stock sprint rom using ODIN but i'm also stuck in recovery boot loop. Would some one direct me where i can maybe find the correct .tar to flash with ODIN
this is the one i used: L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME
Thanks
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
exarkun631 said:
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
Click to expand...
Click to collapse
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
yeah I tried that
BWolf56 said:
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
Click to expand...
Click to collapse
So I am able to boot into recovery but it's the stock recovery, not the one I intalled after root.
I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
exarkun631 said:
So I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
Click to expand...
Click to collapse
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
what about...
BWolf56 said:
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
Click to expand...
Click to collapse
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
exarkun631 said:
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
Click to expand...
Click to collapse
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Strange
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
BWolf56 said:
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Click to expand...
Click to collapse
lol
exarkun631 said:
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
Click to expand...
Click to collapse
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
exarkun631 said:
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
Click to expand...
Click to collapse
Did you do a clean flash? Sounds like you didn't factory reset.
Make sure you backup your apps before doing so if you wanna keep your app data.
Hi guys. Brand new to this whole rooting thing. Long story short, I rooted my device (Galaxy S3 sgh-t999) a while back and was just living off stock touchwiz just with all the bloatware deleted. I had the most recent version of TWRP installed and my recovery was based on that. I then downgraded TWRP to 2.3.3.0. It asked me to reboot and I did so. Now I'm stuck at the Samsung logo screen but it doesn't get past that. The device seems to boots up, but the moment the little Samsung jingle starts to play (you know the swirly blue mist that encompasses the Samsung logo), it stops in the middle of the jingle and the phone won't get passed it.
I tried rebooting back into TWRP via up, home, power and was able to get into TWRP recovery good enough, I can access everything in the menu and tried wiping dalvik, cache, factory reset and system and restored from my backup, but upon trying to restore from my custom backup, it just stalls on the Samsung logo screen. Any ideas if this is fixable? Sorry if this is in the wrong forum guys.
Also, I should make mention that whenever I try to hard power off my phone by holding down the power button, it turns off for a moment then boots back on again. I actually have to remove the battery in order for the phone to turn off. Don't know if that helps.
That's normal when you hold the power button down. It's a hard reset so it's supposed to boot back up.
As for your other issues, why did you downgrade twrp? If your backup was made with another version I suggest using the same to restore it.
Most of the time a factory reset will fix this type of problem, but it sounds like we are beyond that now. If the restore and another reset don't work, go to my firmware thread (sticky in development) and download the same or newer firmware as what you had before. Flash via Odin and factory reset from the stock recovery. ( This will wipe the internal sd)
That should get you going again.
For the future, please do not ever manually wipe /system. You could end up with no O/S to boot into and a hell of a headache! There is simply no benefit to doing so. Only risk.
Let me know if you have any other questions.
Good luck!
Sent from my SGH-T999 using Tapatalk
I downgraded TWRP because I was having issues flashing a new ROM. Every ROM I tried flashing came up with an error and people said they were most successful with 2.3.3.0 so I tried it out. I suspected it might have screwed something up but stupid me always has to be sure. I would try and re-use an upgraded TWRP version if possible but I don't think I can access that from the TWRP menu itself and that's just about the only function my phone has at this point. Just booting into TWRP and playing around with the menu.
Do you have a link to your thread? Thanks for the time by the way.
The link should be in my sig. But it's stickied at the top of the development section. Can't miss it.
If you go to twrp's Web page you can download a newer one in .zip format and flash from your current version.
Or get the .tar.md5 one and flash from Odin.
In the newer versions you can actually flash the .img file itself. After choosing install and are browsing for the file, look for a button to use the .img.
I don't believe this is available in the older ones though.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
The link should be in my sig. But it's stickied at the top of the development section. Can't miss it.
If you go to twrp's Web page you can download a newer one in .zip format and flash from your current version.
Or get the .tar.md5 one and flash from Odin.
In the newer versions you can actually flash the .img file itself. After choosing install and are browsing for the file, look for a button to use the .img.
I don't believe this is available in the older ones though.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You are a LIFESAVER! I was sure I messed something up permanently that would cause me to have to get a new phone. THANK YOU THANK YOU THANK YOU!
You're welcome! Glad I could help! So I take it you've got it up and running again?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You're welcome! Glad I could help! So I take it you've got it up and running again?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup! It was really a simple matter of updating TWRP via Odin. I don't know why it never crossed my mind to use it. Maybe I'll have more luck using different ROMs through Odin instead of TWRP as well.
Odin is really only just for flashing full firmware for updates and returning to stock, and for flashing recovery. Pretty much everything else (all custom roms, for example) is meant to be flashed in a custom recovery like twrp. If you're ever unsure, reread the op of whatever you're flashing, and if your answer isn't there feel free to ask about it.
In a nutshell: Odin only flashes .tar and .tar.md5 files. Recovery flashes .zip.
I do highly recommend an app called Mobile Odin by chainfire. Search xda for his thread and make sure you read all the info if you're interested. It can make flashing super easy!
Sent from my SGH-T999 using Tapatalk
I am having a similar issue. I have never modified any of the original specs and this is a new issue as of 48 hours ago. In short, my device was on, auto shutdown and then froze on the Galaxy S3 load screen. Attempts to boot in recovery,safe, and soft/hard reset have not worked. I can access Odin mode. After reading the above thread I went to the link you suggested and went directly to the firmware my SGH-T999 started with(T999UVDLJA) and worked my way up the list to see if any of them would take. Unfortunately none achieved a 'PASS' via Odin. So, my question is, what do you do when all the steps have been followed and the firmware doesn't work. Any help would be greatly appreciated.
What error are you getting in Odin?
Do you see anything about warranty bit on the download screen? If you are, the flash is probably failing because you are trying to flash old firmware over new firmware. I suggest flashing the latest firmware for your T999 from here: http://www.sammobile.com/firmwares/database/SGH-T999/