Related
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.
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
leatherneck6017 said:
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
Click to expand...
Click to collapse
Thanks for the suggestion, but I've tried flashing TWRP in Odin and it fails and says "Custom Binary (Recovery) blocked from FRP lock".
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
leatherneck6017 said:
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
Click to expand...
Click to collapse
Sure am, I just hope that flashing the firmware download will work when it's available. Otherwise I guess I'm screwed
How about Kies? Long shot I know...
leatherneck6017 said:
How about Kies? Long shot I know...
Click to expand...
Click to collapse
Just tried Kies and still nothing, this sucks I hate how I can't leave my phones stock
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
bhavstech said:
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
Click to expand...
Click to collapse
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
bbacon said:
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Click to expand...
Click to collapse
bbacon said:
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
Click to expand...
Click to collapse
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Mig1234 said:
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Click to expand...
Click to collapse
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
bbacon said:
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
Click to expand...
Click to collapse
sorry for the bother but am a bit new to all this. am faced with exactly the same problem. What TAT file are u guys talking about and where can i download it.
Saafir said:
They mean TAR and you can find it here as well as various other threads here on sammobile.com
Click to expand...
Click to collapse
Thanks for the clarification
i have the same problem too, frp lock. i cant do anything, stuck in logo
butterfan214 said:
i have the same problem too, frp lock. i cant do anything, stuck in logo
Click to expand...
Click to collapse
Which version were u on, 5.1 or 5.0
My sm-920T t-mobile Galaxy s6 is now stuck in a boot loop on splash screen
I flashed the new note 5 kernel and firmware that just came out to it and everything was working fine until I restarted my phone and now I'm stuck in just the Samsung Galaxy s6 boot screen can't access anything but download mode do any of you have any useful info or files I may be able to flash through odin to get through this because my phone is now essentially now a locked down brick that was working awesome right before I restarted it for the first time I forget the devs. name who put out the kernel and firmware for the note 5 to work on the s6 but this damned frp block/lock has made my fully paid for s6 I just got a doorstop now and I'm so frustrated anything I'm trying to flash on odin AP. is failing and I'm just so angry. Can someone please swoop in and give me some possibly useful advice so I can get my phone to boot because it was fine..... Till the restart because just one program was f/c but I would've eventually restarted anyway so I guess once I flashed it I was doomed. DEVS PLEASE. I know someone in here has to have had the same problem and conquered it. I've tried everything in my limited repertoire. Thanks alot for any responses. I was on normal 5.1.1 s6 firmware previous was just rooted with custom recovery
Getting the same frp error. Everthing I flash through ODIN fails. Even flashing stock 5.1.1 OF7 fails. I believe it's because I was on OGA so I have to wait until the tarball for that comes out I guess. Unless anyone else has some ideas?
Try using ODIN to reload the bootloader. Google the how, there are many posts.
Hope it helps. That's what I did to get mine to work.
same-ish stuffs
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
tupac unincorn said:
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
Click to expand...
Click to collapse
can you tell me which stock rom did you use please.
I recently rooted my galaxy s6 edge g925t and was successful, but i couldn't stop there, i wanted to upgrade to android 6.0. i spent hours searching for a custom ROM/firmware and found one that i thought would work. I installed that custom OS through TWRP installer. After i finished the installation i tried to restart the phone but it just stayed at the "Samsung Galaxy S6 EDGE" boot logo and didn't play the boot animation. I searched online for ways of unbricking the phone and i eventually got to the recovery mode and tried to wipe the internal storage. then i restarted the phone and was back to the same Samsung logo. I again tried to get back to the recovery mode, but this time i did an advanced wipe and i ended up deleting the OS. if tried installing the stock ROM/firmware via Odin but can't get it to work. Is there anything i can still do? Can anyone please help me?
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
M9x3mos said:
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
Click to expand...
Click to collapse
The phone doesn't accept that either.
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Also, what is happening when you do that. I gathered out didn't work, but what error comes up?
zabrador said:
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Click to expand...
Click to collapse
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
micahtjosaas said:
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
Click to expand...
Click to collapse
Yeah, I don't think TyrannusRom is runnable on a G925T :/
Flashing stock with ODIN should do the trick. It's hard to tell where that stock file is from, so I would try to download the latest directly from SamMobile here (this is specifically for the G925T). If it's still not working, copy/paste the error ODIN is giving you here if you can.
Also, this thread seems to suggest you might be able to just re-flash the bootloader.
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
micahtjosaas said:
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
Click to expand...
Click to collapse
No problem! Glad you're back up and running
im so sorry for anytime this may take up..but i am desperate for help.my previous account was username doomtree i think
i had lost it when i messed up my phone.anyhow my phone is a VERIZON NOTE 4 SM 910V
i was trying out some new roms.i had flashed a ported edge rom to my device it was working but showed as T-MOBIL
i tryed a verison modem and brickked...i couldnt access twrp recovery..i did odin restore..my understanding was use a full firmware image
flash with odin.after many attemps i can now get it to flash and pass but i cant seem to flash any custom recovery
and i cant get it to boot up to a functioning system..if left to boot after a odin pass i get through boot to system but nothing showes
...stays blank throwing sytem ui error
simple search reveals...
https://forum.xda-developers.com/search/forum/3676?query=bricked
basically, you need to download samsung kies3 and let it return to stock firmware.
make sure you have a working usb cable as I had given up on un bricking my note 4 but it worked with a new cable.
Doomunit said:
im so sorry for anytime this may take up..but i am desperate for help.my previous account was username doomtree i think
i had lost it when i messed up my phone.anyhow my phone is a VERIZON NOTE 4 SM 910V
i was trying out some new roms.i had flashed a ported edge rom to my device it was working but showed as T-MOBIL
i tryed a verison modem and brickked...i couldnt access twrp recovery..i did odin restore..my understanding was use a full firmware image
flash with odin.after many attemps i can now get it to flash and pass but i cant seem to flash any custom recovery
and i cant get it to boot up to a functioning system..if left to boot after a odin pass i get through boot to system but nothing showes
...stays blank throwing sytem ui error
Click to expand...
Click to collapse