Develop Bugs

[Q] bricked -i747.

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.

[Q] need help urgently please :'(

i don't know how i did that stupid thing ! i'm using note 2 gt-n7100 ( rooted ) i tried to install a new rom that doesn't built for my phone with " mobile odin v 4.2 pro unfortunately it flashed the sumsung star dous stock rom on my mobile but it doesn't boot .. i entered the philz touch recovery menu and select clean to install a new rom and restore my old rom and the problems started to appear !
the first thing is when i press the power button to lock my note 2 and try to open it again i find no response at all and the only way is to remove the battery and re turn it on again and try not to press the lock button as if i do so my mobile gives me no response and the screen doesn't turn on !
the second matter i noticed that when the start up i found the bluetooth icon trying to turn to green like i'm turning the bluetooth on but a few seconds it didn't turn on even i try to turn it ! the bluetooth doesn't work at all !
the third thing when i recieve a call that turn on the proximty sensor automatically if i touch the sensor the screen go black but i lose the control and give me no response at all and i have to remove the battery and turn it on again !
the things i noticed when i flashed the galaxy star rom with mobile odin that it has partion called param and the note to doesn't have it with its rom but have partion called modem which i didn't found in the galaxy star rom !
i need help please how i delete things that caused that conflict .. i tried to reflash the stock rom of my note with odin on my lap top but nothig changed and it hanging and the screen freezes with no control at all and that happened when i try to use a custom rom and flash it through the recovery .. please help urgently
sorry for my bad english

Two options I see:
1. Try to restore your device using Kies3
2. Flash newest firmware (get it from sammobile) for your region using PC-Odin.

Putting "need help urgently please :'(" does not help you in any way, in fact it makes it more likely that people will simply ignore the topic. Topic titles need to be descriptive, not generic non-descriptive.
Your problem is that like many newbies you cant be bothered to do research, read and learn before messing around with your device.
You should boot into download mode and flash a stock rom. Preferably a older one that doesn't have knox. Then flash a stock rom(without knox) in recovery mode. All the info you need is here on forum.

Androidwizzard said:
Two options I see:
1. Try to restore your device using Kies3
2. Flash newest firmware (get it from sammobile) for your region using PC-Odin.
Click to expand...
Click to collapse
i forgot to tell that one of the things changed that my mobile lost the usb support in the normal mode as there is no change when i connect it to my pc except it charges only but it works in the download mode and when i reflash the stock rom v 4.3 the screen freezes after a few seconds of turning it on and i have to remove the battery .. do you think that flashing the 4.4.2 sthock rom will make a change ? as the solution of kies isn't possible due to the lack of usb support !
is there a way to format the sectors that the pation " param " which flashed by the sumsung star dous stock rom is in it and make that conflict to delete that ??

What was your last stock rom on your device before messing up?
I do absolutely not agree with those horror tales about knox, most people don't use and easily get rid of.
Do you remember your last bootloader? MK4 or above? Then don't take any risk by flashing 4.3 firmware and go straight ahead to 4.4.2.
It will be the safest way to get a working device again.

TheATHEiST said:
Putting "need help urgently please :'(" does not help you in any way, in fact it makes it more likely that people will simply ignore the topic. Topic titles need to be descriptive, not generic non-descriptive.
Your problem is that like many newbies you cant be bothered to do research, read and learn before messing around with your device.
You should boot into download mode and flash a stock rom. Preferably a older one that doesn't have knox. Then flash a stock rom(without knox) in recovery mode. All the info you need is here on forum.
Click to expand...
Click to collapse
i'm sorry for the way i show my problem as i'm a newbie already .. it that possible to downgrade my rom ? i will try install 4.1.2 rom then flasing the 4.4.2 one but when i flashed the 4.3 stock rom the screen freezes and nothing changed what do you think of that ? it there's a way to delete the " param " found in the sumsung galaxy star dous rom ? i think that made this conflict but try to explain to me why flashing an old rom then a new one without knox ? what will that do ?

Androidwizzard said:
What was your last stock rom on your device before messing up?
I do absolutely not agree with those horror tales about knox, most people don't use and easily get rid of.
Do you remember your last bootloader? MK4 or above? Then don't take any risk by flashing 4.3 firmware and go straight ahead to 4.4.2.
It will be the safest way to get a working device again.
Click to expand...
Click to collapse
i was using dn3 rom which has android version v 4.4.2 but i enter the recovery and restored the stock rom v 4.3 and it works with no problem and it was the last rom i use it when i flashed the star dous rom through the mobile odin in my mobile .. is there is a things i must do when i'm flashin the rom through the pc odin ? like check the repartion option or some thing else ?
my bootloader version is : n7100xxuena1 what that mean ?

omar youssef said:
i was using dn3 rom which has android version v 4.4.2 but i enter the recovery and restored the stock rom v 4.3 and it works with no problem and it was the last rom i use it when i flashed the star dous rom through the mobile odin in my mobile .. is there is a things i must do when i'm flashin the rom through the pc odin ? like check the repartion option or some thing else ?
my bootloader version is : n7100xxuena1 what that mean ?
Click to expand...
Click to collapse
So you can also try the NA1 firmware, but nothing beneath that. NA1 is a knox enabled BL, so whatever you flash successfully will have Knox in it.
DON'T TICK REPARTITION!

Androidwizzard said:
So you can also try the NA1 firmware, but nothing beneath that. NA1 is a knox enabled BL, so whatever you flash successfully will have Knox in it.
DON'T TICK REPARTITION!
Click to expand...
Click to collapse
what you mean of the NA1 firmware if you mean the 4.3 stock rom i flashed it with the pc odin and my mobile screen freezes as i told you and nothing changed .. give me obvious steps 1 2 3 to do it to solve this problem and if you can give me a suitable download links .. now you know all the issues with my mobile and thanks for your interst

omar youssef said:
what you mean of the NA1 firmware if you mean the 4.3 stock rom i flashed it with the pc odin and my mobile screen freezes as i told you and nothing changed .. give me obvious steps 1 2 3 to do it to solve this problem and if you can give me a suitable download links .. now you know all the issues with my mobile and thanks for your interst
Click to expand...
Click to collapse
1) Go to Sammobile
2) Find firmware for your region -> download
3) Find Odin 3.09 -> download and install
4) Start Odin 3.09
5) Plugin device -> see if Odin displays active com port
6) Go into download mode
7) Link firmware download in tab PDA/AP
8) Let Odin check md5
9) Press start button
10) Wait until display of com port in Odin turns green and says success.
All these steps could also be found with an easy Google search or in Youtube tutorials

Androidwizzard said:
1) Go to Sammobile
2) Find firmware for your region -> download
3) Find Odin 3.09 -> download and install
4) Start Odin 3.09
5) Plugin device -> see if Odin displays active com port
6) Go into download mode
7) Link firmware download in tab PDA/AP
8) Let Odin check md5
9) Press start button
10) Wait until display of com port in Odin turns green and says success.
All these steps could also be found with an easy Google search or in Youtube tutorials
Click to expand...
Click to collapse
Thanks for your work but I did all these steps but my mobile freezes and noying changed fir sorry .. I flashed the 4.4.2 kitkat stock rom which is the latest one !

omar youssef said:
Thanks for your work but I did all these steps but my mobile freezes and noying changed fir sorry .. I flashed the 4.4.2 kitkat stock rom which is the latest one !
Click to expand...
Click to collapse
OK, I see. Try a wipe from stock recovery, wipe all possible.
Another option: Kies!
I know, you said not recognized but you must get it to work. Uninstall all drivers from PC an re-install drivers until Kies can restore your device.
Very last option: Find a Samsung repair near to you.

Androidwizzard said:
OK, I see. Try a wipe from stock recovery, wipe all possible.
Another option: Kies!
I know, you said not recognized but you must get it to work. Uninstall all drivers from PC an re-install drivers until Kies can restore your device.
Very last option: Find a Samsung repair near to you.
Click to expand...
Click to collapse
Look I searched the internet find something I think it will be useful if we can use it successfully called n7100 rescue rom consists of 5 files in one zip file it is the fully original factory rom but unfortunately it's 4.1.2 jellybean so how can I flash this rom successfully ? Is it possible downgrade the bootloader first or what ?? Please help

omar youssef said:
Look I searched the internet find something I think it will be useful if we can use it successfully called n7100 rescue rom consists of 5 files in one zip file it is the fully original factory rom but unfortunately it's 4.1.2 jellybean so how can I flash this rom successfully ? Is it possible downgrade the bootloader first or what ?? Please help
Click to expand...
Click to collapse
As you mentioned you already have been on NA1 firmware and as it seems you have flashed latest 4.4.2 with "a kind of success" I find it hope- and useless to even try this rescue rom. Bootloader is the reason why you can't successfully flash. NO DOWNGRADE POSSIBLE.

Androidwizzard said:
As you mentioned you already have been on NA1 firmware and as it seems you have flashed latest 4.4.2 with "a kind of success" I find it hope- and useless to even try this rescue rom. Bootloader is the reason why you can't successfully flash. NO DOWNGRADE POSSIBLE.
Click to expand...
Click to collapse
Can you illustrate your words ? For kies it's unpossible to connect my mobile to any pc the drivers works perfectly for any similarphone the fault is in my mobile not the driver and for sumsung care it will be high cost as the warranty ended ! And I wipe every thing possible through the stock recovery but noyhing changed !

I am beginning to lose my patience cause you don't follow my advice or even don't consider that I am right.
Look into system on your PC if there is an unknown device.
Whenever hardware is connected to PC Windows starts to search for drivers.
It doesn't matter that other devices are recognized correctly.
Wipe all Samsung drivers and re-install. Even re-install Kies too.
Start Kies and try restoration, maybe it will fail, but try. AND with current drivers you are supposed to fail.
At last: Try to find a friend with knowledge who can help you at your home or his.

10.1 Note (2014 Edition - SM-P600) Continuously Reboots - Please HELP

Hello Everyone!
I'm stuck!!! If anyone can help, it is so appreciated!
I attempted to root my subject named device using ODIN following these directions:
http://forum.xda-developers.com/galaxy-note-10-2014/development/root-cf-auto-root-t2905495
Everything seems to go as planned until restart.. the tablet continuously reboots, over and over, but fails to load.
I have no clue what to do from here, so this is my only option... ask those who have much more knowledge than me!
Thanks in advance. I really appreciate your assistance.

That's called a bootloop. Something went wrong with flashing. What is a subject named device? That autoroot method only works for smp600 that is already running stock 5.1 or 4.4.2 . Boot into downloadmode using the appropriate buttons, then Download stock firmarwe from sammobile.Com and flash via Odin to get back a working device.

Which build are you on? If it is 5.1.1, that method will result in a bootloop if you try to root.
Use this instead
http://forum.xda-developers.com/showthread.php?p=63637426
Sent from my SM-N915G using Tapatalk

diabl0w said:
That's called a bootloop. Something went wrong with flashing. What is a subject named device? That autoroot method only works for smp600 that is already running stock 5.1 or 4.4.2 . Boot into downloadmode using the appropriate buttons, then Download stock firmarwe from sammobile.Com and flash via Odin to get back a working device.
Click to expand...
Click to collapse
The tablet is a Samsung Galaxy Note 10.1 (2014 Edition) Model SM-P600.

Not sure about the build.... but I will most definitely checkout the link you provided - thanks!
Question, can I flash a different rom rather than stock?
Also, I was just able to flash TWRP via ODIN and was able to get TWRP to load on the device. I'm hoping to flash a custom rom from the external SD via TWRP. I don't care which one at this point.. just need to get the tablet functional again and get a backup saved lol.

smoothbeaver said:
Not sure about the build.... but I will most definitely checkout the link you provided - thanks!
Question, can I flash a different rom rather than stock?
Also, I was just able to flash TWRP via ODIN and was able to get TWRP to load on the device. I'm hoping to flash a custom rom from the external SD via TWRP. I don't care which one at this point.. just need to get the tablet functional again and get a backup saved lol.
Click to expand...
Click to collapse
Here is "how to" instruction by me - post #225 for upgrade to the latest 5.1.1 and root your device. Once done and you want custom rom, just boot into twrp and flash any custom rom that you like. Let me know if you have issue.
http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3239971/page23

Updated Bootloader: Bootloop, cannot access recovery, can access download mode !

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.

**HELP** Bricked SM-J200M

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.