Pre-tense/irrelevant to problem:I was having issues with being able to hear calls (never had a problem with the pacman rom for the longest time) so I flash to another rom and then I got no reception period so, I flashed to stock rom to attempt to take it back to the store to which I learned my warranty experienced two months ago. some where in the process of being frustrated I ended up bricking it.
THE PROBLEM: My phone is soft brick/stuck in the loading screen/big text of SAMSUNG with a loading bar that fills up but, never ends up booting. I know my way around Odin since I did root her but, I'm having an issue just installing the stock rom again to get her working to a certain degree (I will trouble shoot my call issue once this is figured out) I referred too http://forum.xda-developers.com/showthread.php?t=1513359 to get the stock on it once again and the odin gave me a failed message. (with the others, that I have tired and can't reference since my mind is mush because of mid terms did succeed to download but, simple returned me to the problem of be stuck on the boot screen) I can probably figure it out if give enough time to work on it but, with school grinding on my brain I simply don't have the time (I really should be studying right now instead of typing this out) If you could point me to a link that contains the file to fix my problem I would be very happy.
p.s. if you didn't read the pre-tense I got soft bricked in my stock rom so no, I can't boot into recovery.)
also, thanks for navigating my typing/spelling as I am half asleep and my head hurts from 7 hours of study today. if you need more info on the problem just let me know.
sliding bandit said:
Pre-tense/irrelevant to problem:I was having issues with being able to hear calls (never had a problem with the pacman rom for the longest time) so I flash to another rom and then I got no reception period so, I flashed to stock rom to attempt to take it back to the store to which I learned my warranty experienced two months ago. some where in the process of being frustrated I ended up bricking it.
THE PROBLEM: My phone is soft brick/stuck in the loading screen/big text of SAMSUNG with a loading bar that fills up but, never ends up booting. I know my way around Odin since I did root her but, I'm having an issue just installing the stock rom again to get her working to a certain degree (I will trouble shoot my call issue once this is figured out) I referred too http://forum.xda-developers.com/showthread.php?t=1513359 to get the stock on it once again and the odin gave me a failed message. (with the others, that I have tired and can't reference since my mind is mush because of mid terms did succeed to download but, simple returned me to the problem of be stuck on the boot screen) I can probably figure it out if give enough time to work on it but, with school grinding on my brain I simply don't have the time (I really should be studying right now instead of typing this out) If you could point me to a link that contains the file to fix my problem I would be very happy.
p.s. if you didn't read the pre-tense I got soft bricked in my stock rom so no, I can't boot into recovery.)
also, thanks for navigating my typing/spelling as I am half asleep and my head hurts from 7 hours of study today. if you need more info on the problem just let me know.
Click to expand...
Click to collapse
Have you tried booting into recovery?, if not try that by holding both volume up/down and holding power until it vibrates, if able to get into recovery try factory reset (not sure what recovery you were using, so if its stock it would be just an option, if custom recovery then wipe > factory reset.
If you are unable to get into recovery, then I suggest booting to download mode (volume down + power) and flashing TWRP using Odin3 v1.85, depending which ROM (4.12/4.22/4.3 etc) you had last successfully booting, use one of the following links:
4.12, 4.22 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.0.0-hercules.tar
4.3 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
Select PDA in Odin and whichever recovery*.tar you downloaded, once that is flashed reboot into recovery and try wipe > factory reset, then reboot and see if still stuck in boot loop.
If you have trouble flashing the recovery make sure you have the right version of Odin and its a good idea to have the latest USB Drivers which can be found here: http://forum.xda-developers.com/showthread.php?t=2038555
Another thing I noticed is that the link you posted is not actually your stock rom, it can be found here:
Latest Official Koodo Stock 4.1.2 http://forum.xda-developers.com/showthread.php?t=2258338
or Koodo Stock 4.0.4 (scroll down on this page and find Koodo T989D 4.0.4 http://forum.xda-developers.com/showthread.php?t=1858435
It has the stock recovery too, if you want to truly go back to stock to return phone for repairs etc.
Almite said:
Have you tried booting into recovery?, if not try that by holding both volume up/down and holding power until it vibrates, if able to get into recovery try factory reset (not sure what recovery you were using, so if its stock it would be just an option, if custom recovery then wipe > factory reset.
If you are unable to get into recovery, then I suggest booting to download mode (volume down + power) and flashing TWRP using Odin3 v1.85, depending which ROM (4.12/4.22/4.3 etc) you had last successfully booting, use one of the following links:
4.12, 4.22 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.0.0-hercules.tar
4.3 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
Select PDA in Odin and whichever recovery*.tar you downloaded, once that is flashed reboot into recovery and try wipe > factory reset, then reboot and see if still stuck in boot loop.
If you have trouble flashing the recovery make sure you have the right version of Odin and its a good idea to have the latest USB Drivers which can be found here: http://forum.xda-developers.com/showthread.php?t=2038555
Another thing I noticed is that the link you posted is not actually your stock rom, it can be found here:
Latest Official Koodo Stock 4.1.2 http://forum.xda-developers.com/showthread.php?t=2258338
or Koodo Stock 4.0.4 (scroll down on this page and find Koodo T989D 4.0.4 http://forum.xda-developers.com/showthread.php?t=1858435
It has the stock recovery too, if you want to truly go back to stock to return phone for repairs etc.
Click to expand...
Click to collapse
okay, the 4.12, 4.22 rom has given me the hope now to not give up (the "teamwin" with a blue wavy background shows up but disappears to the vibration ever two seconds with the screen off this was the only thing that happened when I tried to boot into recovery before the odin flash, till I release vol up+down, and the power button to which the samsung and loading bar reappears.)
my last successful boot was on this http://forum.xda-developers.com/showthread.php?t=2485228&highlight=telus (I know I'm an idiot for picking a telus stock rom instead of a koodo one but, I wasn't thinking straight.)
also with the me being an idiot thing, I don't think I'm use odin correctly to simply flash a new stock rom (the ones you have listed in particular). I am using it as such: push PDA and select a file (I could select the TWRP and flash it successfully for the 4.12 easy enough) the only box I have checked off is auto reboot. but, with the stock rom's you provided the files are not showing up for me to select. I'm assuming this is me missing a simple step in the process and I would tinker with it till I could select it but, know I'm scared ****less to **** up the little progress I have made.
here is a picture if that was too wordy
{
"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"
}
and here is a direct link in case that looks as bad in the post as it did in the preview http://i.imgur.com/XKiXJ0h.png?1
but, so far THANKS SO MUCH, any progress in what looked hopeless makes me feel so much better.
sliding bandit said:
okay, the 4.12, 4.22 rom has given me the hope now to not give up (the "teamwin" with a blue wavy background shows up but disappears to the vibration ever two seconds with the screen off this was the only thing that happened when I tried to boot into recovery before the odin flash, till I release vol up+down, and the power button to which the samsung and loading bar reappears.)
my last successful boot was on this http://forum.xda-developers.com/showthread.php?t=2485228&highlight=telus (I know I'm an idiot for picking a telus stock rom instead of a koodo one but, I wasn't thinking straight.)
also with the me being an idiot thing, I don't think I'm use odin correctly to simply flash a new stock rom (the ones you have listed in particular). I am using it as such: push PDA and select a file (I could select the TWRP and flash it successfully for the 4.12 easy enough) the only box I have checked off is auto reboot. but, with the stock rom's you provided the files are not showing up for me to select. I'm assuming this is me missing a simple step in the process and I would tinker with it till I could select it but, know I'm scared ****less to **** up the little progress I have made.
here is a picture if that was too wordy
and here is a direct link in case that looks as bad in the post as it did in the preview http://i.imgur.com/XKiXJ0h.png?1
but, so far THANKS SO MUCH, any progress in what looked hopeless makes me feel so much better.
Click to expand...
Click to collapse
First off you're not a idiot!, the file you originally downloaded should of worked too, for our Jelly Bean roms prior to 4.1.2 we had separate official releases for Koodo 4.0.4 and Telus 4.0.3, once 4.1.2 was released it was only available thru Samsung Kies, until some great folks here on these forums made downloadable roms of the release, so Koodo SGH-T989D and Telus SGH-T989D are both the same rom when it comes to JB 4.1.2, here although is the difference you might of missed, the one you originally downloaded is a flashable ZIP which can only be flashed from recovery(TWRP), the one that I linked is a zip that has to be unpacked and flashed with Odin in Download mode.
So are you now able to get into recovery? btw, sometimes you might need to flash the recovery a couple times for it to actually work, because if you can get into recovery you might just need to do a wipe/factory reset to get phone to boot.
If you really want to flash that rom from my link you just need to unpack it and then go into download mode and use Odin to flash the file.
try flashing stock tar with odin, not just the rom but full stock, radio recovery everything. if you get stuck in a boot loop after flashing stock, go to stock recovery and choose master reset. Should fix your stock boot loop. if it does not work then attempt to flash twrp recovery, if you can get that then you can attempt to flash a rom which might work.
p.s. for issues with reception signal I usually just flash the latest radio after every rom flash, just incase a rom overwrites something necessary.
well, now I tried the TWRP flash (successful everytime) 5 times and after attempting to get into recovery I have had the same results as before.
now that I understand that the roms have to be extracted I attempted that and I got this (i.imgur) fRv6pP2.png (apparently I can't post links now) I attempted at least 3 times and got the same result. Am I doing something wrong? Also is there any other variants of the TWRP recovery you sent me, It seems like it is so close to getting into recovery but, falls short every time. At the moment I'm thinking that getting a recovery (once I'm in recovery I should be out of the woods.) is this phones best chance unless you have any other suggestions.
if the rom is a zip file, it should only be flashed using twrp do not extract roms. If trying to return to stock, it is a tar file you need, it should be flashed using Odin.
for the t989d koodo, with odin you should be flashing this file here for stock, http://www.hotfile.com/dl/203997277/0885f39/T989DTLUMC4_T989DOYBMC4_KDO.zip.html
extract this zip, which would give you a .tar file. Use that .tar file in odin under pda.
sliding bandit said:
well, now I tried the TWRP flash (successful everytime) 5 times and after attempting to get into recovery I have had the same results as before.
now that I understand that the roms have to be extracted I attempted that and I got this (i.imgur) fRv6pP2.png (apparently I can't post links now) I attempted at least 3 times and got the same result. Am I doing something wrong? Also is there any other variants of the TWRP recovery you sent me, It seems like it is so close to getting into recovery but, falls short every time. At the moment I'm thinking that getting a recovery (once I'm in recovery I should be out of the woods.) is this phones best chance unless you have any other suggestions.
Click to expand...
Click to collapse
That rom in the picture of Odin is not the official JB 4.1.2 rom for T989D, it's the T-Mobile T989 rom, which I'm not even sure if it's possible to be flashed onto the T989D.
I'd download the JB 4.1.2 T989D stock rom from either the link I posted or the link the person above this post, they are both the same file, it is the official release for our Koodo, Telus phones.
Another option you could try is to download and install Samsung Kies and see if it can fix the issue, but make sure you try to odin the official rom first, or Kies might not even recognize your phone.
SUCCESS!!! I flashed the odin file that mikeysmith281 posted and the original recovery right after that and I finally got into recovery and now everything is back to normal. thanks so much.
I will be going back to my beloved pac man rom once I get a little breather from my midterms but, in case I have an issue with reception/ the ability to pick up a call I understand now that I simply flash the lastest radio.
p.s. stupid question: are radios device specific or ROM specific? I can't say I look extremely hard for the pacman radios since I didn't quite understand how it could work for the longest time and simply stop working for no reason but, it would make sense why I never found them if they are simply on a per phone basis.
p.p.s once again THANKS SOOOOO MUCH!
sliding bandit said:
SUCCESS!!! I flashed the odin file that mikeysmith281 posted and the original recovery right after that and I finally got into recovery and now everything is back to normal. thanks so much.
I will be going back to my beloved pac man rom once I get a little breather from my midterms but, in case I have an issue with reception/ the ability to pick up a call I understand now that I simply flash the lastest radio.
p.s. stupid question: are radios device specific or ROM specific? I can't say I look extremely hard for the pacman radios since I didn't quite understand how it could work for the longest time and simply stop working for no reason but, it would make sense why I never found them if they are simply on a per phone basis.
p.p.s once again THANKS SOOOOO MUCH!
Click to expand...
Click to collapse
Good to hear!, as far as radios for our phone, there is only 2 possible radios that can be used if running a JB 4.1.2 or newer based rom, the radio is flashed from recovery, pretty sure that for Canada the Telus radio is best, here is a link you might want to bookmark.
http://forum.xda-developers.com/showthread.php?t=1895400
You will be on the Telus radio now since you just flashed stock 4.1.2 rom, if you ever run into issues with radio signal that are not your mobile providers issue, then just reflash the radio.
Related
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
Long time reader, first time poster.
I don't have anything worthy to contribute as most everyone on these forums is far more experienced than me. I do however run into problems - a lot. Working through those problems is quite possibly more enjoyable than experimenting with new ROMS, and I wouldn't be able to work through any of them without the help of this forum. That said, I'll give the short version of my problem first as I'm sure not everyone wants to read the lengths I've been to to unbrick this phone.
I used CyanogenMod's app to root my phone and flash CM10 (which felt like a bad idea at the time). I love CM10 on my Kindle, but I wasn't the biggest fan on my SIII. My phone updated to CM11; which I really hated, and in an effort to flash a new ROM I got stuck in a boot loop. Now I cannot boot into any recovery at all.
The long version:
I am a novice when it comes to flashing, but I'm learning as I screw up. This is the 4th device I've rooted and my second SIII. I have been using TWRP on my Kindle and I totally love it. After having CWM installed by CM's app, I was unable to flash any ROM, period. Rather than hurl my phone against the wall (which I really wanted to) I tried to flash the TWRP .img file, but no matter how I tried the only recovery I could get to was CWM. Finally I used CWM to flash the latest version of PAC-MAN - which I had bootloop problems with on my Kindle - and consequently found myself in a bootloop. I would get the regular Samsung screen, then the CM Samsung screen, then the PAC-MAN screen which it would stay in forever. Throughout all of this the only way I could access a bootloader was by restarting the phone into recovery from Android. Using the "Volume-up, Home Button, and Power" combo doesn't work. I can't remember it ever working to get me to recovery. Anyway, I now have the Dongle Jig which gets me to Download Mode and I can flash the Stock ROM through Odin, but now my boot is stuck on the black Samsung screen. I have also tried flashing the TWRP .tar file through Odin with no luck.
I'm open to any and all suggestions.
HELP!!!
GalaxyBob said:
Long time reader, first time poster.
I don't have anything worthy to contribute as most everyone on these forums is far more experienced than me. I do however run into problems - a lot. Working through those problems is quite possibly more enjoyable than experimenting with new ROMS, and I wouldn't be able to work through any of them without the help of this forum. That said, I'll give the short version of my problem first as I'm sure not everyone wants to read the lengths I've been to to unbrick this phone.
I used CyanogenMod's app to root my phone and flash CM10 (which felt like a bad idea at the time). I love CM10 on my Kindle, but I wasn't the biggest fan on my SIII. My phone updated to CM11; which I really hated, and in an effort to flash a new ROM I got stuck in a boot loop. Now I cannot boot into any recovery at all.
The long version:
I am a novice when it comes to flashing, but I'm learning as I screw up. This is the 4th device I've rooted and my second SIII. I have been using TWRP on my Kindle and I totally love it. After having CWM installed by CM's app, I was unable to flash any ROM, period. Rather than hurl my phone against the wall (which I really wanted to) I tried to flash the TWRP .img file, but no matter how I tried the only recovery I could get to was CWM. Finally I used CWM to flash the latest version of PAC-MAN - which I had bootloop problems with on my Kindle - and consequently found myself in a bootloop. I would get the regular Samsung screen, then the CM Samsung screen, then the PAC-MAN screen which it would stay in forever. Throughout all of this the only way I could access a bootloader was by restarting the phone into recovery from Android. Using the "Volume-up, Home Button, and Power" combo doesn't work. I can't remember it ever working to get me to recovery. Anyway, I now have the Dongle Jig which gets me to Download Mode and I can flash the Stock ROM through Odin, but now my boot is stuck on the black Samsung screen. I have also tried flashing the TWRP .tar file through Odin with no luck.
I'm open to any and all suggestions.
HELP!!!
Click to expand...
Click to collapse
You was not on the OTA MK3 build prior to all the flashing right? If not..
Flash TWRP 2.6.3.0 .tar in Odin (I read I am not the only one having trouble with 2.6.3.1)
Reboot Recovery
Saafir said:
You was not on the OTA MK3 build prior to all the flashing right? If not..
Flash TWRP 2.6.3.0 .tar in Odin (I read I am not the only one having trouble with 2.6.3.1)
Reboot Recovery
Click to expand...
Click to collapse
I'm not sure what OTA MK3 is, but I just tried flashing TWRP 2.6.3.0 via Odin with no luck. What is OTA MK3 and how would it affect my ability to flash?
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.
Okay so heres the dealio. I am not a noob been rooting, flashing etc. since Cyanogen was actually Cyanogen back in the G1 and Mytouch days. I have read every tutorial available. I have tried Kies, Odin, different USB cords, various drivers, nandroid backups etc. I was on the 5.0 unoffical cyanogen rom I think it was 12-08 or 06. NB4 "MODEM" had the coveted MDL Baseband. I was running CWM recovery. was setting alarms whole screen turned bright pink and froze so I pulled battery waited several minutes, rebooted and it would make it to cm splash screen then go pink and reboot.
First thing I did was try all of my nandroid backups none did any good. Of course I wiped everything before restoring
Second tried several Roms I know worked I always keep a couple on SD just in case ones I have tested and are working
Third I tried to Odin to MDL passed boot loop did this several times with sd and without I even uninstalled kies to make sure no interference
After that I just started climbing firmware mk2, NB4, NH7 all same results. I did each one multiple times evry which way you can imagine
I tried multiple Roms 4.4.2 4.4.4 etc to no avail
Finally I tried Kies. Kies Upgraded me to NK2 still boot loop. Odin NK2 still boot loop.
I have tried super wiping then installing boot loop
I can get into DOWNLOAD MODE AND RECOVERY MODE NO PROBLEM. I can flash custom recovery through odin no problem I have tried Cwm I have tried Twrp. Twrp gives me more options.
Now I have had some success.... If I do it perfectly I usually have to format everything with aromas mega wipe takes a few attempts I can get Danvdh GE 4.4.4 Rom to boot but it constantly vibrates if i do anything like reboot it or anything back to boot loop.
I have checked my pit file and compared to a stock pit everything matches perfectly so I dont think any partitions are screwed..
Knox is tripped who cares its past warranty I am on NK2 firmware. I dont care if I am stuck on stock or some custom rom. I need my phone to work just dont have money to buy a new one.
Please help me. I am not a noob if I have to rebuild the whole system using ADB I will just need some guidance.
****UPDATE***** Currently Have SOPK 4.4.4 from Unified Dev up and running.... No audio at all, much more stability, occasionally freezes will bootloop unless plugged into usb on computer.
***********LOGCATS************* https://drive.google.com/folderview?id=0B479jD3Q_BOvZWYtRDZ2bjBZN2M&usp=sharing
Try this. Flash MDL baseband, flash NK2 with Odin, reboot to recovery and factory reset. After that perform a reboot and see if it works. This has seemed to work for a few people that had updated just the baseband and then later tried to flash full firmware and got stuck in bootloops
do you happen to have link to MDL baseband I have the NK2 firmware
I did find this I want to make sure I have the right one http://forum.xda-developers.com/showthread.php?t=2282342
Also am I flashing these back to back then reboot or flash MDL reboot to download then flash NK2? Just dont want to screw myself any further. Thank you very much for your help Thanks button hit 100x
Yeah that's the one, and just flash the modem, once it's done, do a battery pull, boot straight back into download mode and flash it again. After that, flash full NK2 firmware
Tried it twice with Odin 3.07 and 3.09 still looping.
I do remember having to push the NB4 Modem with ADB while maintaining the MDL baseband if that has anything to do with it.
I saw a pink screen scenario once after water damage on my nephews s4 (not saying you have water damage ) but phone never recovered, not even after disassembly and clean, had limited function, had to be replaced.
Pp
There was never water damage. Its hard to believe that its hardware since I can get dl mode and recovery no problem. But anything is possible. I only get the pink screen now when I try to reflash the 5.0 Cyanogen
ok right now ive got Danvidh GE 4.4.4 pure nexus up and running. its doing a little vibration loop every 30-60 seconds. i have a bug report for whoever wants it. i also have a recovery log from twrp. i'll leave it up and running until i get some advice. i do know if i reboot itll kick into boot loop.......
Update: Ive got about 15 minutes of logcat. and it did reboot on its on back into rom still doing the vibration loop. it freezes randomly no audio. Ill keep running logcat and keep this puppy up till I hear from someone.....
Ok so I'm posting from my SGH-M919. The one with problems. Here's what I think happened, I think while on The 5.0 CM ROM I received the lollipop OTA. This is just a guess as I'm seeing people have been getting OTA notifications for this Device. I'm not sure what I should do. I've done extensive debugging. All hardware looks good from what I can tell. I have tons of logcats and debug files for anyone willing to help. As of now still running DanvidH. 4.4.4 GPE pure nexus version baseband NK2. The vibrations continue. Apparently its due to Google play service update in the last 24 hours and this ROM. Since its literally the only thing that will run on here I'll keep it for now. It freezes constantly, cannot use it as a phone either as it just freezes on the way to dialer. Anyway hopefully someone can help...... Thanks
Sent from my GT-I9505G using XDA Free mobile app
Can you share a link to this 5.0 cm rom?
Just curious.
### Edit ###
Never mind just found it in development.
Pp.
---------- Post added at 09:21 AM ---------- Previous post was at 08:35 AM ----------
Just looking over this 5.0 Cm rom I get the impression that this is chuck full of bugs, since the beginning back on 11/13 and just 2 hrs ago op posted an update with potential bugs still present. If I had to have a reliable operating phone this is one rom I wouldn't touch.
Any input from op?
Pp.
http://forum.xda-developers.com/showthread.php?t=2539361&page=458 just got uploaded last night follow instructions explicitly look at last or so post
Can you check what bootloader and modem you have now? Upload the logcat right before the reboot happened
OK so I am able to run the 5.0 much more stable. Dialer crashes no audio at all system or other wise. It froze then rebooted and back to bootloop which logcats do you want i couldnt get catlog to run on 5.0 but I have about 3 hours worth of logcats from the 4.4.4 pure nexus. what logcats would you like. I also have adb setup and http://www.xda-developers.com/android/advanced-logcat-published-as-a-standalone-tool/ it was running great on 4.4.4 but couldnt get it to retrieve on 5.0
I did get about 2 hours of smoothness from 5.0 just no sound and dialer crashes no one else reporting issue. Texts work fine
NK2 boot loader with Twrp recovery
whats really really weird is I have to connect the phone to computer after flashing to get it to actual start the rom
Hello, I have this SM-T520 galaxy tab pro 10.1 that I bought new some years ago. I had rooted it and ran with it for a while until I wanted to flash a custom rom. I can't remember how that went but I assume it went badly, since it hasn't been able to boot into anything for years. It tries to boot up as long as it has power (even without pressing the power button) but it doesn't do anything after you get to the Samsung screen. It just stays on a back lit black screen. I can get into the Android system recovery by pressing power and volume up, then releasing power. It says it has "K0T49H.T520XXUANAE" at the top but I'm not sure if I had changed that at some point. Anyway, even after wiping data/factory reset and wiping cache partition it still cannot boot. I tried updating from external storage a few times before but it kept failing. Maybe I had the wrong file? What can I do to fix this thing? Any help is appreciated.
Go to pc, download odin. Go to https://www.sammobile.com/firmwares/ enter device and look and download lastest offered firmware for your region. Flash downloaded firmware with odin. You should be on a booting stock rom now.
You can do this as often as you like (eg. when device is bad after playing with custom roms).
hamudistan said:
Go to pc, download odin. Go to [website] enter device and look and download lastest offered firmware for your region. Flash downloaded firmware with odin. You should be on a booting stock rom now.
You can do this as often as you like (eg. when device is bad after playing with custom roms).
Click to expand...
Click to collapse
That worked perfectly... I feel like that was too simple and I should have been able to find this online somewhere. Maybe I just couldn't find the right word combo in google.... Thanks!!
Now to try flashing a custom rom on this, since touchwiz makes me cringe.