Related
Galaxy note 2 I317M can’t flash, stuck on Samsung galaxy logo
On this one can’t flash anything
With Odin gave error on modem partition (when start to flash). I can flash the recovery partition
With any box on sboot partition
I can go in download mode but CAN’T go in recovery mode, stuck in Samsung galaxy logo
I don’t know anything about the history
Is supposed to be a phone with cracked LCD but after replaced I’m stuck
Thanks for any ideas
P.S
please don't ask me to wipe or entry in recovery mode because the phone is not able, just in download mode
thanks again
Did the device boot up correctly after you received it?
about getting into recovery, just flash one with odin in download mode and see if you can get into it (home + power + volume up (or down, can't remember which of the 2 are for download mode, haven't used it in ages) ) I would recommend TWRP, as that one has a file manager in it you could use to see if there's anything on the device already.
make sure you get the official rom for your device
Code:
sammobile.com
most likely has what you need, downloads are slow though and you need to register but its a good site nevertheless.
make sure the file of the rom isn't corrupted, do a md5 check before you try to flash it. After downloading the rom zip file you need to extract it and point odin to the tar file with the "PDA" button, do not select anything besides "Auto Reboot" and "F. Reset Time" (they should be selected when opening ODIN, leave the other setting checked off)
What settings did you use in odin if i may ask? if you choose to repartition or erase nand or whatever they call it in the newer versions, you might have a serious issue as you have to have a special PIT file to get the partitions back. It also would explain why odin can't flash to the boot partition as its simply not available. If i'm not mistaken the PIT file for our devices isn't available.
could you perhaps explain a bit more in detail what steps you took after you got the device/replaced the screen in combination with odin and such? If you can't flash recovery or a rom through odin, then my best bet would be your device is ready to be thrown in the garbage.
i have the same prob once, and solved it...
here's what i did.
-reflash stock rom via odin
-reboot (boot loop acheived!)
-flash TWRP
-wipe cache/dalvik
-reboot but this time stuck at sammy logo for a while...
i left it alone for a while, about 15 mins. came back, and saw i was at the initial setup screen. try it... it may work for you too.
msk514 said:
i have the same prob once, and solved it...
here's what i did.
-reflash stock rom via odin
-reboot (boot loop acheived!)
-flash TWRP
-wipe cache/dalvik
-reboot but this time stuck at sammy logo for a while...
i left it alone for a while, about 15 mins. came back, and saw i was at the initial setup screen. try it... it may work for you too.
Click to expand...
Click to collapse
he tried flashing with odin though, but he got an error while flashing about the modem partition, either something is broken inside the phone,(missing partitions due to wrong wipe in odin perhaps) or the rom he downloaded is corrupted. Also he seems to have issues with the recovery being unable to be flashed to the device.
as soon as you get the samsung boot logo (not the initial galaxy one where your device model is mentioned) the rom is booting up, first time always takes a while being stuck on the galaxy logo however means there's probably not any boot partition written with a boot.img by odin This could also mean either corrupted rom file or lack of partition to write too. No boot partition means the device simply doesn't know it should load something.
If i understand his post correctly he bought a second-hand device where only the screen was broken. i don't know how the screen got broken in the first place, but if the device took a hard fall, there's a big chance its not only the screen but also some hardware got broken.
i have more details
actualy is a AT&T version (someone changed the screen from a canadian phone but forgot to change the label
I'm able to flash the AT&T rom I317ATTALJ2 from sammobile with odin 9reboot and F. reset time checked) but is stuck on samsung galaxy note 2 logo
I CAN"T entry in recovery mode (don't know why)
only download mode
contramundi said:
If i understand his post correctly he bought a second-hand device where only the screen was broken. i don't know how the screen got broken in the first place, but if the device took a hard fall, there's a big chance its not only the screen but also some hardware got broken.
Click to expand...
Click to collapse
i bought the phone with cracked screen
after tried many times i asked the owner and he told me the label is from a Canadian phone but the motherboard is from at&t
i can flash ONLY with odin and only I317UCALJ2 firmware. Any other firmware from at&t or not i have error when flash the system partition
i tried also with Octopus Box and Z3x Box. Same error
after flash successfully with odin is stuck in Samsung logo and NO RECOVERY MODE
so don't ask me to wipe
maybe with some Linux commands?
thanks
Sounds like you need the pit file and re partition checked i would look for a pit file for your phone when you find one check repartition
32dave said:
Sounds like you need the pit file and re partition checked i would look for a pit file for your phone when you find one check repartition
Click to expand...
Click to collapse
can't find pit file
i don't know if is the same like i317m or n7105
even like this i think i need a rom with modem, csc, pda and bootloader separated
thanks
nickmatine said:
can't find pit file
i don't know if is the same like i317m or n7105
even like this i think i need a rom with modem, csc, pda and bootloader separated
thanks
Click to expand...
Click to collapse
try to flash http://forum.xda-developers.com/showthread.php?p=37688128 or if you have a different model than 7105 do a google search for a pit file for that phone.
afterwards flash the stock rom for your model (att/tmobile/etc) the rom itself should contain everything you need.
Found a pit file i will upload it here but it is from this thread http://forum.xda-developers.com/showthread.php?t=2376405 hope this helps
32dave said:
Found a pit file i will upload it here but it is from this thread http://forum.xda-developers.com/showthread.php?t=2376405 hope this helps
Click to expand...
Click to collapse
seeing as the motherboard is from AT&T should he still use the canadian PIT file?
(don't wanna sound like a noob, and don't have the slightest clue about how the hardware inside the phone actually works so i'm just trying to learn new stuff )
I don't think it makes a difference as far as the pit goes
just let you know i was able to flash a stock rom from at&T and the phone work well now
thanks to everybody:good:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
gica69 said:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I found out that the phone had 4.1.1 on it and the guy tried to flash 4.2.2 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
gica69 said:
I found out that the phone had 4.11 on it and the guy tried to flash 4.22 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
Click to expand...
Click to collapse
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3
PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Larry2999 said:
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Click to expand...
Click to collapse
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
gica69 said:
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
Click to expand...
Click to collapse
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Larry2999 said:
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Click to expand...
Click to collapse
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
gica69 said:
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
Click to expand...
Click to collapse
You didn't mention if you tried the Kies option. I had a similar problem once when upgrade to 4.1.1 via Kies failed during the process and that was how I was able to recover. However, since you bought this from the secondary market, there is no way of telling for certain what the previous owner did wrong which would have been useful for recovery options.
One of the nice things about Odin is that you usually know the results immediately. If it says Pass, therefore, that's likely what it means. So Odin did flash something. But what did it flash? The counter you saw in download mode shows how many custom system installations there have been and 6 does show there has been some previous heavy tinkering with the phone. As you are still able to get into download modes, I would suggest you try flashing custom recovery (TWRP or CWM) via Odin. If this works and you are able to get into recovery mode, you may then try doing a hard wipe/reset via recovery. You may also try flashing the other (rooted) 4.1.1 file via Odin. At this stage, you really have nothing to lose in trying all options. I guess if you can get into recovery mode, the problem is almost solved as this leaves plenty of options.
A jig wouldn't help as that only gets you to download mode which, for now, you don't have a problem with. JTag should always be a last resort option only. Let me know how far it goes and good luck!
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
audit13 said:
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
Click to expand...
Click to collapse
This damn phone is starting to annoy me. I can still get into download mode but my phone gets usb device not recognized now. I have access to another I747 phone so my question is if I have access to the pit file from that phone can anything be done with the Debrick utility and a SD card with only download mode access? Thanks in advance.
Go into download and let us know what is shown on the screen.
audit13 said:
Go into download and let us know what is shown on the screen.
Click to expand...
Click to collapse
Odin Mode
Product Name: SGH-I747
Custom Binary Downloads: Yes (6 Counts)
Current Binary: Samsung Official
System Status: Official
Qualcomm Secure Boot: Enable
Green Android Icon Downloading...
Do not turn off target!!!
OK I plugged the USB in and out a few times and it allows to write every few tries. Back to my question can I do something in download mode if I have another i747 that I can copy stuff from? I also tried the suggestion to uncheck auto-reset pull the usb cable then the battery and try to go to recovery but it doesn't.Any suggestions are welcomed.
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
audit13 said:
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
Click to expand...
Click to collapse
I will try it again I think I already did but when I put the battery back and click the Vol+ Home Power I get the blue writing and then black screen. Should I wait like 10 min on the black screen or it should be quick. Thanks
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
audit13 said:
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
Click to expand...
Click to collapse
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
If u can get it into download mode u are never ever hard bricked my friend...take it from a guy who had to dust off his old galaxy sll last weekend & still can't get into d/l mode on my s3 after a week & even with a jig lol
Sent from my SGH-T989 using xda app-developers app
gica69 said:
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
Click to expand...
Click to collapse
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Larry2999 said:
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Click to expand...
Click to collapse
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
gica69 said:
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
Click to expand...
Click to collapse
I couldn't find one either although you may be able to create yours using the command line posted in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
You may also try using a jig to get back into download mode. Have you, however, considered exercising any buyer protection options you have on the phone since, it would appear, the guy sold you a lemon?
I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.
asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
After flashing, did you boot to recovery and wipe data and cache?
audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk
asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.
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.
Hello Everyone.
Please, I need some help. I was trying to downgrade an ATT Samsung Galaxy S3 from 5.0 to 4.1.1 and try to unlock it.
First, Try to flash with Odin 3.04, Odin 3.07 and Odin 3.09 with the firmware 4.1.1 from Samsung. It always failes.
So I rooted it , installed a team Win Recovery Project 2.6.3.1 and flashed a custom rom based on Android
4.1.2 thinking it will break the bootloader. Nothing.
I tried Emergency Recovery with Kies did not work.
In odin mode:
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcom Scoreboot: Enable
Warranty Bit:1
Bootloader AP SWREV:3
I spent hours on it. I don't know what to do.
Anyone has a idea to help me please?
Thanks you very much in advance.
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
audit13 said:
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
Click to expand...
Click to collapse
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
MEEEEEEEE said:
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
Click to expand...
Click to collapse
If you're on Philz touch, download AROMA file manager and store it on your external SD. You can get it here.
Boot into recovery and flash the file manager like you would install a ROM and it will open the file manager. Once you're up in the AROMA file manager, one of the menu options is to open a console. Once you're up in the console window the following command will tell you what bootloader you have loaded:
Code:
getprop ro.bootloader
That command will work from ADB shell in custom recovery too, if you happen to have ADB and all the drivers set up right on your computer.
What error did you get when flashing with Philz? Was it error 7?
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
MEEEEEEEE said:
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
Click to expand...
Click to collapse
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
You may have to try a de-brick image. Status 7 usually occurs when the recovery is out of date.
jason2678 said:
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
Click to expand...
Click to collapse
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
MEEEEEEEE said:
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
Click to expand...
Click to collapse
You did put the battery back in after pulling it for a couple of minutes, right? Looking back at my previous post it was poorly worded.
The fact that you went from working recovery and download to not working on a status 7 is curious. Usually status 7 errors are the developers trying to protect us from ourselves; your recovery is out of date, you are trying to flash a rom that isn't for your phone or doesn't like your bootloader, something like that. When you get a status 7, usually the recovery didn't actually do anything. It failed a safety check and quit. That's what made me wonder if maybe your battery just died.
So you flashed CM11 for the d2lte using the latest version of Philz? Did you flash anything else?
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
MEEEEEEEE said:
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
Click to expand...
Click to collapse
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Yes. The red led is showing when I plugged the device without the battery.
mrrocketdog said:
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
MEEEEEEEE said:
Yes. The red led is showing when I plugged the device without the battery.
Click to expand...
Click to collapse
pretty positive sign of a brick if thats all you can get. check the link for the "de-brick" thread that i posted. remember that sometimes it takes more than one try , and while one sdcard will work for one phone , it may or may not work for another. just keep trying. good luck.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Do I need to get a jig to un-bricked it?
MEEEEEEEE said:
Do I need to get a jig to un-bricked it?
Click to expand...
Click to collapse
nope. read the thread. a de-brick image and sdcard should do it.
"all i can really do , is stay out of my own way and let the will of heaven be done"
A jig would be helpful if the phone boots but you can't get into download mode.