Database Info

[Q] Tried to root Korean SM-P900; now stuck in reboot loop

Hi,
I have a Korean SM-P900 that I tried to root with CF AutoRoot using Heimdall. I identified the recovery and cache partitions using print-pit, then flashed the recovery.img and cache.img to their respective partitions. After that it started booting, and was stuck at the Samsung screen for several minutes.
I then rebooted it by holding down the power button. When it was booting back up, it showed a message in Korean and with a counter that counted up to 79, then showed a similar message counting up to another number. It kept doing that no matter what, never booting up, even if I rebooted it again.
After that I tried flashing it again the same way. Now it shows the same message as earlier, but actually boots into the Samsung initial setup screen. However, I can't get past it, because a message showing "MyScript ResourceManager", followed by some Korean text, blocks me from doing anything, and if I hit okay it just reappears.
Any ideas on how to unbrick it?

Try going into recovery and do a Full reset. If that doesn't work, download the Korean firmware (or whichever version you want, as long as it is SM-P900) and flash back to stock using Odin. Messing with partitions using Heimdall can be tricky and dangerous if you don't have a PIT file for your device. Hope this works for you.
Sent from my SM-P900 using Tapatalk

dodo99x said:
Try going into recovery and do a Full reset. If that doesn't work, download the Korean firmware (or whichever version you want, as long as it is SM-P900) and flash back to stock using Odin. Messing with partitions using Heimdall can be tricky and dangerous if you don't have a PIT file for your device. Hope this works for you.
Click to expand...
Click to collapse
Going into recovery and doing a reset fixed the problem. Thank you very much!
The reason I didn't flash back to stock earlier was because I couldn't find the Korean stock firmware anywhere, and I was unsure if I could flash another country's firmware to it without breaking something. Nice to know that I can.
Now that it's functional again, will it be okay to try to root it again, this time using Odin?

sm-p900user said:
Going into recovery and doing a reset fixed the problem. Thank you very much!
The reason I didn't flash back to stock earlier was because I couldn't find the Korean stock firmware anywhere, and I was unsure if I could flash another country's firmware to it without breaking something. Nice to know that I can.
Now that it's functional again, will it be okay to try to root it again, this time using Odin?
Click to expand...
Click to collapse
Yes, flashing another region is ok, but you may have issues with keyboard languages and wifi channels being different. Yeah just use Odin for CF-Autoroot. You can download a recovery image to flash if it gets stuck on cache.img. It's in the cf-autoroot thread for the 12.2. Best to read the entire thread before you start. Good luck.
Sent from my SM-P900 using Tapatalk

dodo99x said:
Yes, flashing another region is ok, but you may have issues with keyboard languages and wifi channels being different. Yeah just use Odin for CF-Autoroot. You can download a recovery image to flash if it gets stuck on cache.img. It's in the cf-autoroot thread for the 12.2. Best to read the entire thread before you start. Good luck.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I have now rooted my tablet, and it's working great. Thank you very much for your help!

sm-p900user said:
I have now rooted my tablet, and it's working great. Thank you very much for your help!
Click to expand...
Click to collapse
so towelroot doesnt work for this device?

torreon901 said:
so towelroot doesnt work for this device?
Click to expand...
Click to collapse
Towelroot is only for Qualcomm based devices. SM-P900 uses an Exynos SOC.
Sent from my SM-P900 using Tapatalk

Help with bricked device

Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?

mpalomba3 said:
Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?
Click to expand...
Click to collapse
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.

http://forum.xda-developers.com/showthread.php?t=1734949

dawgdoc said:
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.
Click to expand...
Click to collapse
landshark68 said:
http://forum.xda-developers.com/showthread.php?t=1734949
Click to expand...
Click to collapse
Thanks, I managed to figure out the problem. I thought I was flashing 4.4.2 images but I was actually flashing 4.3 images. I downloaded the latest image and managed to flash it in Odin without a problem.
Thanks again for responding

Custom binary blocked by FRP lock.

Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.

chewtoy0 said:
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
Click to expand...
Click to collapse
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck

mrd0pe said:
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
Click to expand...
Click to collapse
Can't get into Recovery no. Which file of the lot has the stock recovery in it?

chewtoy0 said:
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
Click to expand...
Click to collapse
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho

Your S/N is on the rear of the phone it can be a pain to see but it is there. Use smart switch to restore the firmware. Just click emergency firmware restore.

It is? The IMEI is there but I didn't see the SN. Also my phone is black so that doesn't help.
I will have another look.

mrd0pe said:
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Click to expand...
Click to collapse
I did that. No dice.

I had the same issue as you. Used the same rom and disabled developer options. I downloaded stock firmware.. flashed it with odin. It actually took 2 tries. The first time I could see only 1/4 of the screen. The second time i flashed stock firmware from another country and it worked. You might actually have to do a hard factory reset if you cant unlock your phone.. for some reason. Then I let kies do its magic because I could then see my S/N. Right now I still feel my phone slightly different. Messenger is unstable for some reason also.

Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".

chewtoy0 said:
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
Click to expand...
Click to collapse
Try to flash Nougat firmware, as that was what your custom rom was on right? I dont think it really matters though as I downgraded from stock 7.0 to stock 6.0.1 via odin without errors... But you can try
As an absolute last resort I would try to check the "re-partition"-tab and provide odin with a .pit file, then load everything (BL, AP, CP...) with stock firmware <<<< do this at your own risk, if you are not careful, your phone will be bricked

I am trying to flash MM back to it .
I'm not sure I want to mess with the re partition table...But it's already soft bricked.

Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.

Matty39856 said:
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Click to expand...
Click to collapse
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.

chewtoy0 said:
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
Click to expand...
Click to collapse
I'm not sure then. Have you tried flashing the latest unlocked version for your region? I remember on my s6 I had a similar problem that was caused because I was trying to flash a lower version of Android than what I previously had. So ended up flashing the latest unlocked version BTU for my region and it worked. Sorry I can't be of more help. It looks like the latest firmware is still 6.0.1 that's why it's blocking it from downgrading.

Was sent a PM by a person. Was skeptical at first, but in 10 minutes using TeamViewer, they fixed the issue by reflashing the device (as well as repartitioning it properly). I can't thank them enough.
This is the person on Facebook...
Unlock Network FRP Lock Remote Service

Help with rooting Galaxy S7

Hey all,
I tried rooting my Galaxy S7 today with Odin 3.11.1 and I thought it all went fine, it said it passed and that it was successful. However when it starts to boot it gets no further than the boot screen which says "Samsung Galaxy S7" and then "Powered by Android" at the bottom. There isn't an unlocked padlock on the screen either which I thought there was meant to be. Any help would be much appreciated and at this point I am more than happy to just go back to stock firmware and forget rooting even exists.
SM-G930F
G930FXXU1DQD7

You can flash stock from updato.com and ODIN 3.12.3 or newer

*Detection* said:
You can flash stock from updato.com and ODIN 3.12.3 or newer
Click to expand...
Click to collapse
Is that guaranteed to fix my problem then and bring it back to stock?

Lethal_Trousers said:
Is that guaranteed to fix my problem then and bring it back to stock?
Click to expand...
Click to collapse
Nothing is a guarantee when you flash devices with custom stuff and break them
But flashing stock is guaranteed to take you back to stock obviously, so long as it flashes successfully (It will not reverse KNOX 0x1 though, good chance you've tripped KNOX already)
Seems you have reservations about flashing stock, but quite happy to try rooting the phone using an outdated ODIN?

Try downloading a stock firmware from sammobile (make sure to find the right model and android version), extract it and then flash it with odin (assuming that you can still enter download mode). File is quite large to download, but Internet Download Manager (IDM) could speed up the process by 4-5 times. As for rooting, I have an S7 myself and I managed to successfully root it using Odin and chainfire's auto root file. However, I was also stuck in your situation the first time I tried and had to factory reset before trying again. Can't remember the cause though.

The easiest way is using samsung smart-switch.
There is a menue "emergency-recovery" or similar.
Follow the instructions and it will automatically download the actual firmware and flash it.
Good luck

Bricked Samsung S7

Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.

Andre369 said:
Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.

spawnlives said:
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.
Click to expand...
Click to collapse
Thank you for the response I managed to get it fixed. I used odin 3.14 instead and I wiped it with the NAND option and started from scratch. I used the pit file and flushed the bootloader first with repartition, then did the AP separete, and thats how I went on. After all, I'm back again. Thank you for trying, much appreciated.