Related
So my note 2 had been working very well, but just the other night it turned off and then was stuck at the Samsung logo screen. I attempted to boot into recovery, but it would freeze at the TWRP logo screen. I decided to Odin a new recovery and put the latest version of TWRP on there. I can now boot into recovery, but it asks for a password. I assumed I had just used a bad version, so I tried several others which resulted in the same outcome. Pressing cancel lets me get into TWRP, and it seems as though I can browse files, but trying to perform any other action gives an error message saying that TWRP cannot find the partition for data, system, and a few others.
Is the phone dead? Or is there something I can do to bring it back to life?
captterrible said:
So my note 2 had been working very well, but just the other night it turned off and then was stuck at the Samsung logo screen. I attempted to boot into recovery, but it would freeze at the TWRP logo screen. I decided to Odin a new recovery and put the latest version of TWRP on there. I can now boot into recovery, but it asks for a password. I assumed I had just used a bad version, so I tried several others which resulted in the same outcome. Pressing cancel lets me get into TWRP, and it seems as though I can browse files, but trying to perform any other action gives an error message saying that TWRP cannot find the partition for data, system, and a few others.
Is the phone dead? Or is there something I can do to bring it back to life?
Click to expand...
Click to collapse
Try to flash a stock rom with Odin.
If this does not work you are facing a compareable problem to mine http://forum.xda-developers.com/showthread.php?t=2440687 .
Maybe you find a way to get it work in this link.
Sounds like SDS
Luke44 said:
Try to flash a stock rom with Odin.
If this does not work you are facing a compareable problem to mine http://forum.xda-developers.com/showthread.php?t=2440687 .
Maybe you find a way to get it work in this link.
Click to expand...
Click to collapse
I just read through that thread, I'm not sure where I could find the correct pit mapping for this phone though =/
muppetmania said:
Sounds like SDS
Click to expand...
Click to collapse
I really hope it isn't SDS. I can odin a recovery onto the phone, but so far other odin-able images just fail. I'm downloading a pure factory image currently and will check to see how that works,
I'll try and give as much info as possible so that hopefully this is easy to figure out.
My phone is a Samsung Galaxy s3 sch-r530u the US Cellular version. I didn't see a US Cellular forum and read someplace that it's the same as the at&t one so that's why I'm posting in here.
About a month or so ago I rooted and installed cyanogenmod with the installer and it installed I believe 11.1 maybe 11.2. The Android version my phone said it was I'm pretty sure was 4.4.2. Today in about phone in the settings I got a new version available message so I tried to do an update, which I was understanding that it was a cyanogenmod update and not a stock update but maybe I was wrong.
Right after the update my phone would boot to the boot screen with the blue robot guy on it and freeze basically. I was able to get into CWM and also into download mode. I did a little looking around and went into CWM and did the factory reset/wipe and cleared the cache and dalvik and that changed nothing.
Then I tried to flash the cyanogenmod 10.2 from inside CWM because I read someplace that it fixed the problem for someone else and it just failed when I tried. I also tried to fix via Kies and it isn't accepting my serial number for some reason. Then I found the teamuscellular website and grabbed both roms that say are stock roms and tried to flash both of those (not at the same time) via Odin and when I did the first one I got the something happened during firmware upgrade error.
I eventually fixed that by flashing the pit file with Odin and now I'm back to being stuck on the blue robot boot screen. When I try to flash either stock rom from teamuscellular in Odin they fail at some point and then I have to reflash the pit file again.
Somewhere along the line I couldn't get into CWM anymore and had to reflash that and I now have the philz touch 6.09.2 version of that.
I currently can get into both CWM and Download mode but for the life of me nothing I try works. When I go into Download mode what reads in the top left corner is this
odin mode, in red letters
Product name: SCH-R530U, in white letters
Custom binary download: Yes (4 counts), in white letters
Current Binary: Custom, in white letters
System Status: Custom, in white letters
Qualcomm Secureboot: Enable, in grey letters
Waranty bit: 1, in red letters
Bootloader Ap Swrev: 1, in grey letters
When I try and flash a rom and it fails I get some other line of text in red but I forget what it says
Any help is greatly appreciated
Thanks in advance
EDIT - Also a number of places directed me to samsungs updates websites to get the stock mod for my phone but there isn't one there for the SCH-R530U.
Also I'm looking at the how to guide for unbricking and I see something there about the status 7 error, which I do believe I got when I tried to flash the 2 teamuscellular stock mods but I don't remember for certain. I know one thing I didn't try was updating my bootloader.
I've also tried fixing with the simple upgrade tool and it fails also.
OK so I went ahead and tried the simple upgrade tool again to see the errors it gave me and in the bottom left corner of the program it had gone through a few things and failed when it said ABOOT.
And also at that same time on the download mode screen it added this line in red text at the bottom of the list in the top left corner on my phone screen
SW REV CHECKFAIL: FUSED1>Binary0
Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.
audit13 said:
Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.
Click to expand...
Click to collapse
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.
Thequass said:
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.
Click to expand...
Click to collapse
You can try and fix your phone by updating your recovery to the latest version of CWM for your phone. Then, download an install a custom ROM for your phone.
If you are not sure of what or how to do upgrade your recovery, don't do it until you have done some research and really understand the process.
As with any software change, there is no guarantee you won't brick your phone in the process.
Yeah I understand, I just wanted to make sure you meant CWM. So you think I should try reflashing a 4.3 custom rom over a 4.4? It was running 4.4.2 totally fine for a month ish.
If you want to install another ROM, I recommend doing a full wipe, including the system, cache, Davik, and data, before installing the new ROM.
I have switched between older and newer ROMs without a problem on my i747m.
Ok. I'll definitely wipe everything as I did in the past maybe there's one that I'm missing somehow. I wipe everything and somehow the blue robot boot screen is still there.
Thanks for all of your help. Your suggestions definitely led me in the right direction. I ended up finding a modified stock 4.3 with the bootloader file removed and since it seemed like my issues were related to that I figured what the hell I'll try it, I was almost at the point of going and getting a new phone anyhow. Because it wasn't completely bricked I wanted to try everything I could though and this worked!!!
Thanks again!!
Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop
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.
So I attempted to flash the renegade rom...do not think this has anything to do with that in particular, but now I'm stuck on the screen that says the software was not installed correctly. Holding down the power, volume up and home buttons will get me back to odin but when I try to flash anything in Odin (3.10.6), it gets about 20% done and fails. I can't get into the stock recovery again. Before this happened, I was on stock OI1 and had developer options up and bootloader option on , I tried to flash TWRP but kept getting an error, then I had flashed the unikernel (V6 I believe). The phone booted correctly, but the touch screen didn't work. I rebooted several time and tried again, still screen problem. I went into the stock recovery and did a factory reset, booted, screen still didn't work. I went back to odin tried to flash the G920PVPU3BOI1_G920PSPT3BOI1_G920PVPU3BOI1_HOME.tar, but it halted with the fail message at about 20%. Tried again, failed at same time point. Very frustrating because I've successfully rooted and installed multiple roms on my S4 and Evo prior.
At this point I am stuck in the blue screen that says you need to do smart switch to do an emergency recovery, I can get this over to odin, but not recovery. I tried both smart switch and Kies, and both say the phone isn't supported by the software(s). Yes, the drivers were installed prior to. I've tried waiting for the battery to discharge as well, nothing.
I'm at a loss of what to do now. Phone is inoperable and I can't even get into a screen that tells me anything about versions of hardware or software. The barcode is still intact and I can still get into Odin, but nothing more than that. Stock kernel to flash? Why won't odin finish the upgrades? Anything?
The phone is about to go in the trash...Help!
sfinkedbeef said:
So I attempted to flash the renegade rom...do not think this has anything to do with that in particular, but now I'm stuck on the screen that says the software was not installed correctly. Holding down the power, volume up and home buttons will get me back to odin but when I try to flash anything in Odin (3.10.6), it gets about 20% done and fails. I can't get into the stock recovery again. Before this happened, I was on stock OI1 and had developer options up and bootloader option on , I tried to flash TWRP but kept getting an error, then I had flashed the unikernel (V6 I believe). The phone booted correctly, but the touch screen didn't work. I rebooted several time and tried again, still screen problem. I went into the stock recovery and did a factory reset, booted, screen still didn't work. I went back to odin tried to flash the G920PVPU3BOI1_G920PSPT3BOI1_G920PVPU3BOI1_HOME.tar, but it halted with the fail message at about 20%. Tried again, failed at same time point. Very frustrating because I've successfully rooted and installed multiple roms on my S4 and Evo prior.
At this point I am stuck in the blue screen that says you need to do smart switch to do an emergency recovery, I can get this over to odin, but not recovery. I tried both smart switch and Kies, and both say the phone isn't supported by the software(s). Yes, the drivers were installed prior to. I've tried waiting for the battery to discharge as well, nothing.
I'm at a loss of what to do now. Phone is inoperable and I can't even get into a screen that tells me anything about versions of hardware or software. The barcode is still intact and I can still get into Odin, but nothing more than that. Stock kernel to flash? Why won't odin finish the upgrades? Anything?
Odin Screen Reads:
ODIN MODE (red)
PRODUCT NAME: SM-G920P (white)
CURRENT BINARY: Samsung Official (white)
SYSTEM STATUS: Custom (White)
FRP LOCK: OFF (white)
Secure Download: Enabled (blue)
KNOW WARRANRY VOID: 1 (0x0384) (gray)
AP SWREV: B:3 K:2 S:2 (gray)
The phone is about to go in the trash...Help!
Click to expand...
Click to collapse
What I would recommend doing is to try using Kies 3 its pretty much Samsung's take on iTunes. It maybe able to help you. Otherwise, try redownloading the latest tar avabile which is: OJ7 also, try Odin v3.10.7
1619415 said:
What I would recommend doing is to try using Kies 3 its pretty much Samsung's take on iTunes. It maybe able to help you. Otherwise, try redownloading the latest tar avabile which is: OJ7 also, try Odin v3.10.7
Click to expand...
Click to collapse
Thanks for replying.
I tried Kies and Smart Switch, but both did not recognize phone. I did manage to find out that TWRP has a sprint variant and that it seems to be incorrectly labeled in many posts. The sprint variant is 2.8.7.0 NOT 2.8.7.1. I managed to flash it in ODIN and now it boots into Recovery, which is a start. I tried applying the renegade rom, but it wouldn't finish and I'm left with a 'no OS detected, do you want to reboot?' from TWRP.
TWRP website isn't much help (but I love that product). At this point, still cannot tell what firmware is on device and where to go from here. I think I may need a recovery of some sort, but don't have. Tried flashing OJ7 tar as recommeded but it continues to fail when it hits the 'system' part of the download.
Still need advice/help....etc.
Since you are now in recovery, wipe everything!
Cache, System, Data, Internal Data and Dalvik Cache. After that, reboot into Odin and try restoring once more in odin. If that does not work, then wipe everything again and try installing Renegade once more.
1619415 said:
Since you are now in recovery, wipe everything!
Cache, System, Data, Internal Data and Dalvik Cache. After that, reboot into Odin and try restoring once more in odin. If that does not work, then wipe everything again and try installing Renegade once more.
Click to expand...
Click to collapse
Thank for the reply. I did just that and after installing Renegade with kernel version 8, three times, the phone is up and running. Really appreciate the help.
sfinkedbeef said:
Thank for the reply. I did just that and after installing Renegade with kernel version 8, three times, the phone is up and running. Really appreciate the help.
Click to expand...
Click to collapse
, NP glad I could help.
no roms install on my s6 edge after forget to copy rooms file into TWRP
1619415 said:
, NP glad I could help.
Click to expand...
Click to collapse
now my phone in download " blue screen " mode
please someone help me :crying:
billyfatra said:
now my phone in download " blue screen " mode
please someone help me :crying:
Click to expand...
Click to collapse
You should be able to use odin on your PC tp send an image to your phone.
Lookup, for example, how to root your phone in these threads.
Sent from my SM-G920P using Tapatalk