Hello, I upgraded my girlfriend's phone up to Alpine ROM for SGH-T989D Telus model.
I recently got her a new phone and I wanted to sell this device off and tried to get it to stock firmware.
I was using Odin 3.09 and since it's been a while I accidentally put the md5 file in the BL section and started.
I realized when after a reset my phone was stuck on the boot logo that I must've made a mistake.
I downloaded the telus stock firmware from sam mobile again and flashed it using the PDA box this time. Yet, I still have no luck.
The phone is stuck on the Galaxy SII boot logo and just flashes the big S logo for hours.
Does anyone know how to get this phone up and running. Did I screw up the BL? Where could I download the original BL if I did.
Odin even says PASS! after everything has flashed and the phone reboots but still just stuck on boot logo.
Related
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
try a factory reset in recovery after flashing rom
PhoneTamer said:
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
Click to expand...
Click to collapse
I Odin'd to stock a couple days ago and was at the Samsung Logo for a WHILE (over and hour). It did just go eventually.
Not sure what did it... Got a PIT file, and then did the NAND Erase All bit again when i installed the stock ROM again. Wiped data as soon as install finished, and it booted right up. I'm happy again
Now if i can just figure out the LTE glitch...
It had clockwork mod on it, so I downloaded TWRP from their site and flashed it via clockwork mod and now the boot image get's all crazy and flickers and then black screens. I can still get into download mode so I guess it's odin for me. It's the GT-N7100 model. What version of Odin and which image do I use? I'm in the USA using T-Mobile. Thanks.
Use the right one for your phone, N7100. Try flash it with odin. If it still in bootloop, flash cf-auto root through odin, usually it will boot after auto root process done. Hope this help...
stonedead said:
Use the right one for your phone, N7100. Try flash it with odin. If it still in bootloop, flash cf-auto root through odin, usually it will boot after auto root process done. Hope this help...
Click to expand...
Click to collapse
I meant what country's firmware, mostly, since I didn't see anything for the U.S and I don't have any info about this phone other than that it's the gt-n7100. Anyway, I got past that bootloop, I used some UK firmware, kinda bootlooping between some o2 splash screen and a samsung logo now. I can get into recovery though.
Ok, I'm not boot looping anymore, just did a factory reset in the stock recovery and it worked.
Now I have another issue - I put my sim in, and it starts up and I have HSPA+. Then it drops to 3g after like 30 seconds, and in the initial setup I can't connect to any services to set up my accounts - it just flat out doesnt work. Then I get into the system after skipping all that and I have no data at all, and when I make phone calls it just hangs at dialing. What do I do? Thanks.
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 am happy to be a brand new member of XDA
I am also a noob:/ I have been on this website for a while now and have found nothing for my problem with my SGH-I317 Galaxy Note 2...
My Problem- I installed CWM custom recovery it wokred fine I installed CM 10 (that was a week ago). yestarday I went to turn on my phone when i woke up. It showed the "Samsung Galaxy Note II" and then went CRAZY the logo spazzed and then just turned black. I immediatly went into odin and flashed my only stock rom the SGH-I317 android 4.1.1 because I could only access the download mode. I went to go and do an OTA update to 4.3 (I think I messed up right here). It went fine up until it restarted and and froze on the Galaxy Note 2 logo. I can still access Download mode but I cant get into either stock recovery or the custom recovery mode. I have tried flashing three different stock roms and Odin says it passed but it just reboots and stays on that logo. Please help I am not in the position to buy or replace a new phone (I'm only 14).
ZLederman said:
I am happy to be a brand new member of XDA
I am also a noob:/ I have been on this website for a while now and have found nothing for my problem with my SGH-I317 Galaxy Note 2...
My Problem- I installed CWM custom recovery it wokred fine I installed CM 10 (that was a week ago). yestarday I went to turn on my phone when i woke up. It showed the "Samsung Galaxy Note II" and then went CRAZY the logo spazzed and then just turned black. I immediatly went into odin and flashed my only stock rom the SGH-I317 android 4.1.1 because I could only access the download mode. I went to go and do an OTA update to 4.3 (I think I messed up right here). It went fine up until it restarted and and froze on the Galaxy Note 2 logo. I can still access Download mode but I cant get into either stock recovery or the custom recovery mode. I have tried flashing three different stock roms and Odin says it passed but it just reboots and stays on that logo. Please help I am not in the position to buy or replace a new phone (I'm only 14).
Click to expand...
Click to collapse
Fixed It
Good to hear that it's fixed.
Always tell us how you fixed it - might be of interest for others having the same problems
ZLederman said:
Fixed It
Click to expand...
Click to collapse
how to ???
hackerse7en said:
how to ???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2589891
this forum will help go down and install the att odexed odin rom and flash that via odin
if that doesnt help than install "if ou are running official MK6 bootloader" llink
I had TWRP 2870
i was running cm 11 cough made
everything was fine for a few days then realized that i could only receive text messages and my lte was always dropping out. So I verified my APN setting with my wife's i317 and made all adjustments as needed but no help. so i just got fed up with it all and reinstalled from a backup that i made of stock 4.4.2 everything worked then last night my phone received an OTA from AT&T but because I had TWRP it would not install. I am assuming that it was the stage freight update so (all the trouble began) I used a back to stock recovery using a back to stock sticky that i found and it worked it took me all the way back to stock recovery and 4.1.2 I think and then after installing all necessary updates I went to about device and check for updates and it downloaded a update I don't remember the file size but under 500 megs. then it restarted and installed it then rebooted and it would not go past the samsung logo I have tried everything but a pit file or something like that the only thing i have access to is download mode. when I tried going back to stock 4.4.2 using odin3 v.1.85 and flashed I317-UCUCNE5-Stock.tar odin says all is good and I get very happy but the stupid phone wont boot it gets stuck at the same samgung logo for 30mins. help me. please! Im stuck using the captivate untill i get this fixed.
And you cannot boot into recovery using the 3 button combo ??
If yes ....wipe data...factory reset the device...and wipe the cache as well...g
Edit:
The Update will put the device to UCUCNJ1 official and will lock you into the Knox bootloader as well.
The only 4.1.2 reverts from this point forward cannot contain the bootloader image or softbrick will occur....g