After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.
Related
Hello, my dumb ass decided to root using CFRoot, then it said it failed so I tried to flash the CFAutoRoot in Odin. Well, I tried booting my phone, after saying f*** it, and now I'm greeted with 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.' what can I do? I just bought this phone, so if I screwed it up, I'm in trouble.
What phone and what rom is it running?
audit13 said:
What phone and what rom is it running?
Click to expand...
Click to collapse
SGH-I747(AT&T Samsung Galaxy 3), and the stock 4.3 rom
Unfortunately, there is no way to flash a stock AT&T 4.3 ROM to this phone as AT&T never released a full ROM, only an update.
Did you try reconnecting it to Kies to try and re-flash?
audit13 said:
What phone and what rom is it running?
Click to expand...
Click to collapse
audit13 said:
Unfortunately, there is no way to flash a stock AT&T 4.3 ROM to this phone as AT&T never released a full ROM, only an update.
Did you try reconnecting it to Kies to try and re-flash?
Click to expand...
Click to collapse
I'm on 4.3 update I meant, and how can I reflash? I'm in Kies now.
Wesley. said:
I'm on 4.3 update I meant, and how can I reflash? I'm in Kies now.
Click to expand...
Click to collapse
Does Kies detect your phone at all? Is there a recover option? Sorry, I haven't used Kies for a long time so I don't remember what options are available.
Maybe this will help: http://www.samsung.com/us/support/faq/FAQ00052703/61329
audit13 said:
Does Kies detect your phone at all? Is there a recover option? Sorry, I haven't used Kies for a long time so I don't remember what options are available.
Click to expand...
Click to collapse
I went to tools -> Firmware upgrade and initialization, entered my model # & S/N, and it's 'Downloading file for firmware emergency recovery of 'GALAXY S III '(SGH-I747)' from the server...' so it says, which I got to from Kies. Should I let it run its course?
Wesley. said:
I went to tools -> Firmware upgrade and initialization, entered my model # & S/N, and it's 'Downloading file for firmware emergency recovery of 'GALAXY S III '(SGH-I747)' from the server...' so it says, which I got to from Kies. Should I let it run its course?
Click to expand...
Click to collapse
I'm not sure as I have never used this Kies option. I have always re-flashed via Odin. Your case is different because there is no full 4.3 AT&T Rom that can be flashed via Odin.
Is there any warranty on your phone?
audit13 said:
I'm not sure as I have never used this Kies option. I have always re-flashed via Odin. Your case is different because there is no full 4.3 AT&T Rom that can be flashed via Odin.
Is there any warranty on your phone?
Click to expand...
Click to collapse
It says Warranty Bit: 1 on Download mode
Wesley. said:
It says Warranty Bit: 1
Click to expand...
Click to collapse
Looks like you tripped the Knox counter when you tried to root the phone. Did you get it from AT&T? Maybe you could take it back and get it exchanged for another one since it got pooched while running Kies?
audit13 said:
Looks like you tripped the Knox counter when you tried to root the phone. Did you get it from AT&T? Maybe you could take it back and get it exchanged for another one since it got pooched while running Kies?
Click to expand...
Click to collapse
I got it from Walmart because AT&T was going to take two hours, lol. And, how would I go about doing that? I'm not a good liar, and I don't know how I pooched it lol
Wesley. said:
I got it from Walmart because AT&T was going to take two hours, lol. And, how would I go about doing that? I'm not a good liar, and I don't know how I pooched it lol
Click to expand...
Click to collapse
Well, if you take it to an AT&T or Walmart store, they may not care that you tripped the counter. If they send it in to Samsung for repair, they may not care either. However, there's always the chance that AT&T/Walmart/Samsung would allow repairing the phone at no charge.
audit13 said:
Well, if you take it to an AT&T or Walmart store, they may not care that you tripped the counter. If they send it in to Samsung for repair, they may not care either. However, there's always the chance that AT&T/Walmart/Samsung would allow repairing the phone at no charge.
Click to expand...
Click to collapse
Is there any way I could try flashing a rom?
Wesley. said:
Is there any way I could try flashing a rom?
Click to expand...
Click to collapse
You would need to install a custom recovery in order to flash a custom ROM. A custom recovery can be installed via Odin if you find the right file.
Do not flash any stock Samsung 4.3 ROM or a custom rom unless Knox has been removed.
audit13 said:
You would need to install a custom recovery in order to flash a custom ROM. A custom recovery can be installed via Odin if you find the right file.
Do not flash any stock Samsung 4.3 ROM or a custom rom unless Knox has been removed.
Click to expand...
Click to collapse
I have CWM Recovery, what can I do now? I am rooted, however Knox isn't disabled. Any way I can disable it? I'm unable to boot my phone up, when I try it says 'Firmware upgrade encountered an issue. Please select blah blah..', and I'm in the Download mode now.
Wesley. said:
I have CWM Recovery, what can I do now? I am rooted, however Knox isn't disabled. Any way I can disable it? I'm unable to boot my phone up, when I try it says 'Firmware upgrade encountered an issue. Please select blah blah..', and I'm in the Download mode now.
Click to expand...
Click to collapse
Are you running the latest version of CWM? If you can't boot into your OS, how do you know you are rooted?
Flashing another ROM will remove knox.
Copy a custom rom to a microSD card (do not unzip the ROM which is a single zip file), boot into recovery mode, wipe cache, wipe data, wipe Dalvik, and install the ROM from SDcard1.
I have the latest experimental Cyanfox on my i747m from here: http://cyanfox-rom.com/downloads/?folder=d2att/
audit13 said:
Are you running the latest version of CWM? If you can't boot into your OS, how do you know you are rooted?
Flashing another ROM will remove knox.
Copy a custom rom to a microSD card (do not unzip the ROM which is a single zip file), boot into recovery mode, wipe cache, wipe data, wipe Dalvik, and install the ROM from SDcard1.
I have the latest experimental Cyanfox on my i747m from here: http://cyanfox-rom.com/downloads/?folder=d2att/
Click to expand...
Click to collapse
I was able to before, however in Odin I was trying to flash something(a root file), and it said failed, so i rebooted and now i'm stuck. D:
Wesley. said:
I was able to before, however in Odin I was trying to flash something(a root file), and it said failed, so i rebooted and now i'm stuck. D:
Click to expand...
Click to collapse
When did you flash CWM? Is it 6.0.4.5? How did you flash it? Via Odin?
I can't boot into recovery, I get the firmware upgrade thing again. i have no idea what version it is, and yes via odin
Wesley. said:
I can't boot into recovery, I get the firmware upgrade thing again. i have no idea what version it is, and yes via odin
Click to expand...
Click to collapse
For recovery, are you holding the home button, volume up, and then pressing and holding power? You need to hold all 3 until you see some blue text appear on the screen, then let go of the power button.
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
ghjsdf9 said:
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
Click to expand...
Click to collapse
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Larry2999 said:
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Click to expand...
Click to collapse
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
ghjsdf9 said:
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
Click to expand...
Click to collapse
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Larry2999 said:
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Click to expand...
Click to collapse
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
ghjsdf9 said:
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
Click to expand...
Click to collapse
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Larry2999 said:
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Click to expand...
Click to collapse
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
ghjsdf9 said:
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
Click to expand...
Click to collapse
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Larry2999 said:
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Click to expand...
Click to collapse
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
ghjsdf9 said:
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
Click to expand...
Click to collapse
I've seen this particular problem reported several times and it's always been a problem with the pit file. Flashing a complete stock system should fix all partition problems though. If the stock file you are using is an Odin flashable file, you may try using Odin 3.09. Otherwise, I'd suggest you find a recovery flashable image and flash via (custom) recovery.
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FRP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
EDIT: Good news! Flashing the stock 5.1.1 odin image worked . (link: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841)
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working.
whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
SmartSwitch disaster recovery mode.
whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.
PanchoPlanet said:
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.
Click to expand...
Click to collapse
I was running the G925T (edge) leaked 5.1.1 rom ([5.1.1][ROM][TW][OE6] Blck/TW), which worked well for the month that I used it. I had TWRP from that thread installed as well (I think it was 2.8.6.x). Everything was good at this point.
Where I am now:
When I power the device on, it says:
KERNEL IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
When I try to enter Recovery, it says:
RECOVERY IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
What I did to get here:
SHORT VERSION - flashed latest modem and bootloader for G925T (edge) via Odin.
LONG VERSION
Last night I attempted to flash (via ODIN) the G925T bootloader, modem, and TWRP for this ROM: http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
G92xF(D)/T Galaxy S6 Universal Odexed Pure edition ROM
Based on the latest Samsung Stock G925F XXU2BOFJ Lollipop 5.1.1 firmware (Base build date: 20-JUN-2015)
NOTE: I didn't ever get to flash the ROM because the trouble started when trying to flash the bootloader/modem via ODIN.
- Odexed Pure Edition: Odexed & 100% original/Stock files!
Steps followed:
Do exactly step-by-step the following things:
- Unplug your Phone (IMPORTANT!)
- Turn your Phone completely off (This is IMPORTANT)
- Start your Phone in download mode on this way: Press Vol down + Home + Power buttons till the screen turns on, press Vol Up to continue (Only enter download mode on this way, otherwise it won't work!!)[/B]
- Open Odin 3.10.6 on your PC (Make sure you're using this version of Odin, other versions won't work correctly maybe!)
- Click on the 'BL' button, and load in your BOOTLOADER tar.md5 file for your model
- Click on the 'CP' button, and load in your MODEM tar.md5 file for your model
- DON'T TOUCH ANYTHING ELSE (you can brick your phone if you choose other settings in Odin)
- Now Connect your phone to your computer (DO NOT connect your phone before this step, otherwise it won't work!)
- Click on the Start button
- Wait till it finish flashing.
- Your phone reboots automatically after flashing. <--- device never rebooted because ODIN said Failed instead of Successful.
I then tried to flash TWRP 2.8.7.1 (link below) since maybe that had to be flashed before the bootloader/modem, but it failed too.
Links:
Odin 3.10.6
DOWNLOAD - https://www.androidfilehost.com/?fid=95916177934555153
[G925T] Odin Bootloader/Modem Packages:
5.1.1 Bootloader: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766210
5.1.1 Modem: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766211
You also have to update your TWRP to the latest version (2.8.7.1 or newer) when flashing this.
DOWNLOAD - http://build.twrp.me/twrp/twrp-2.8.7.1-zeroflte.img.tar
Is there a file I can Odin flash to disable FRP Lock? I can't boot up to turn it off.
If not, what are my options from here? Any way to preserve SDCARD or even /Data?
If all else fails, what Odin file should I flash to get back to stock?
EDIT: Regardless of what I try to flash in Odin (recovery, kernel, TWRP, modem), it begins the process but then fails because the phone states "_______ is not SEANDROID enforcing" and states FRP lock is on.
NexVision said:
SmartSwitch disaster recovery mode.
Click to expand...
Click to collapse
SmartSwitch isn't detecting my phone (although Odin does). What mode should it be in? I can get into Download Mode, but that's about it!
Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.
PanchoPlanet said:
Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.
Click to expand...
Click to collapse
Guys at the store couldn't do anything unfortunately. I guess it's just a brick now?
EDIT: The leaked 5.1.1 didn't have that option in dev options either. I guess running the leaked 5.1.1 is where I screwed up, even though it worked great while actually using it. I didn't have root, but I had TWRP recovery.
Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.
whittikins said:
Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.
Click to expand...
Click to collapse
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.
Screenshot showing option for bootloader unlock.
Pp.
PanchoPlanet said:
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.
Click to expand...
Click to collapse
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!
whittikins said:
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!
Click to expand...
Click to collapse
Glad to hear, don't forget about the oem unlocking in developer options.
Read carefully before you flash, and setup smartswitch on your pc, do a backup just in case.
Pp.
I had the same issue. I try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.
drakegao said:
I bricked my phone as well, same situation, I headed to that page try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.
Click to expand...
Click to collapse
Try a different pc, check your WiFi connection, or maybe Starbucks.
Pp.
Just checked link works and download works.
Pp.
PanchoPlanet said:
Just checked link works and download works.
Pp.
Click to expand...
Click to collapse
Thanks for replying, by the way. I got locked when i am still on 5.0.2 and i flash the bootloader and the modem. It was the modem of 5.1.1 didn't go through.
Will it be flashed through the 5.1.1 firmware, if not, any other options can solve the frp locked? Thanks
You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.
PanchoPlanet said:
You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.
Click to expand...
Click to collapse
tried, still failed in odin. I think is may be because my bootloader is actually 5.1.1's.
However, I saw above said flash 5.1.1 odin image ? what is that? Thanks.
solve it by flash 5.1.1 tar via odin as above said. thanks.
I have a Samsung Galaxy J2 (SM-J200M) Region: TTT stuck on a bootloop.
I believe it's soft bricked, but can access Download Mode, but not Recovery mode.
In Download Mode, it shows SM-J200M; Custom Binary: Samsung Official, System Status: Custom, FRP Lock: On; Secure Download: Enabled, and Knox Warantee Void: 0 (0x0000).
I cannot get into recovery mode to wipe data/factory reset. I have flashed different firmwares of SM-J200M. Some failed, some passed, but ultimately, I flashed the original stock firmware of the phone still with no luck. I'm beginning to think it's the System Status that has something to do with it. I know that when I flash the wrong firmware, it will show custom. But it shows System Status as Custom even with stock firmware. Please help.
Note: I have tried Emergency Recovery with Samsung Kies with no luck. I've unlocked bootloader using ADB Enabler to try to flash TWRP and try to have a recovery option, I've tried to take out the battery for 5min. and then reflash the stock firmware and still have no luck. Just the boot up screen with only Download Mode available when holding down combination buttons. Fastboot won't recognize the phone.
Out of 54 views, I have no response. I would just like to know if there's any hope for this device to be used or not. Thanks guys.
Hello there.
You might be able to unbrick using ODIN and flash the stock firmware.
Stock firmware is here: "https://boycracked.com/2016/04/01/official-samsung-galaxy-j2-sm-j200m-stock-rom-firmware/"
Look for your phones region and then click the DOWNLOAD button
To get ODIN, well, you just google ODIN
Once you have got the stock firmware(should be a .md5 file)
Boot your device in DOWNLOAD MODE
Plug the device into your PC
Then... Open ODIN, click on the big button that says AP, and locate your stock firmware
Click on start!
Hope I helped :good:
Naton670 said:
I have a Samsung Galaxy J2 (SM-J200M) Region: TTT stuck on a bootloop.
I believe it's soft bricked, but can access Download Mode, but not Recovery mode.
In Download Mode, it shows SM-J200M; Custom Binary: Samsung Official, System Status: Custom, FRP Lock: On; Secure Download: Enabled, and Knox Warantee Void: 0 (0x0000).
I cannot get into recovery mode to wipe data/factory reset. I have flashed different firmwares of SM-J200M. Some failed, some passed, but ultimately, I flashed the original stock firmware of the phone still with no luck. I'm beginning to think it's the System Status that has something to do with it. I know that when I flash the wrong firmware, it will show custom. But it shows System Status as Custom even with stock firmware. Please help.
Note: I have tried Emergency Recovery with Samsung Kies with no luck. I've unlocked bootloader using ADB Enabler to try to flash TWRP and try to have a recovery option, I've tried to take out the battery for 5min. and then reflash the stock firmware and still have no luck. Just the boot up screen with only Download Mode available when holding down combination buttons. Fastboot won't recognize the phone.
Click to expand...
Click to collapse
Suggest you look for the correct firmware on updato: Link
Try to also flash TWRP see if you can manage to boot into recovery by some miracle and wipe everything
ShaDisNX255 said:
Suggest you look for the correct firmware on updato: Link
Try to also flash TWRP see if you can manage to boot into recovery by some miracle and wipe everything
Click to expand...
Click to collapse
I have flashed the correct firmware from the exact region by using kies firmware upgrade and seeing what the region is cause it teeells you what firmware it downloads based on the serial # then i downloaded it manually and flashed via Odin. I also flashed twrp for j200m latest i believe is 3.0.0.1 or someting or 3.1.1 I forget but they failed. I can't figure out the issue here. All I know is the system status is custom even after flashing original stock firmware when it should say offical and still stuck on the J2 logo. Any idea why that is.?
Naton670 said:
I have flashed the correct firmware from the exact region by using kies firmware upgrade and seeing what the region is cause it teeells you what firmware it downloads based on the serial # then i downloaded it manually and flashed via Odin. I also flashed twrp for j200m latest i believe is 3.0.0.1 or someting or 3.1.1 I forget but they failed. I can't figure out the issue here. All I know is the system status is custom even after flashing original stock firmware when it should say offical and still stuck on the J2 logo. Any idea why that is.?
Click to expand...
Click to collapse
According to your post FRP Lock is ON. Your system status is custom. This is what's causing the bootloop.
It's unlikely you are flashing the correct firmware if the system status is still custom. Yes this can happen even with official Samsung firmware if it isn't 100% correct.
How did you actually end up in this predicament?
I would also ask you post your exact model details and a link to the firmware you have attempted to flash and if possible a screenshot or post the output of the flash with ODIN.
OK I have officially screwed up...
So it was all going smoothly flashing a tweaked custom rom and twrp successfully and then I decided to back to stock...
I accidentally (ok maybe not so accidentally) flipped the OEM unlock switch and now I am locked out of my phone since I still had the custom binary on the phone.
I tried to flash the latest stock firmware for the s9 BTU found from samfirm but odin seemed to have not liked the firmware or something and it gave me an a red message on the odin mode screen.
When I try to flash everything at once I get "REV Failed Check (Bootloader)"
When I try to flash just AP I get "REV Failed Check (Kernel)"
At the moment when I boot up I get the message telling me to use emergency software recovery but Smart Switch does not seem to recognise the device either in the emergency recovery page however it does try to connect on the home page.
I'm not too sure what to do, any help would be nice?
Thank you
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
*Detection* said:
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
Click to expand...
Click to collapse
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Delks123 said:
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Click to expand...
Click to collapse
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Delks123 said:
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Click to expand...
Click to collapse
Yea you'll either have to do something like that, or wait for your region firmware to have it's BL updated
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Delks123 said:
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Click to expand...
Click to collapse
You might need to check "Repartition" in ODIN only, flash all 4 parts at the same time, use CSC and not HOME_CSC
Make sure you are using ODIN 3.13.1
Oh yea forgot the update...
I got it working, I think I unchecked repartition and auto reboot whilst flashing all of them together to get it working
So yea this is now solved