Database Develop

Tried to root 5.0.2 with 5.1.1 guide - softbricked it [SOLVED]

Hello!
Ok, I'll admit I didn't read closely enough in my haste to root my new phone, and now it's softbricked. My phone was brand new and still on the 5.0.2 firmware, and I tried to follow the guide at link here on XDA before updating to 5.1.1. After flashing the sboot.bin, it rebooted, but stuck at the Samsung logo screen with some green text at the top of the screen:
ASV TBL VER = 15
ASV TBL VER2 = 1285
ASV big:10 LITTLE:10 630:11 MIF:10 INT:10 CAM_DISP:10 (I think that's right, it's very tiny!)
I've been stuck there ever since! I can get into download mode, but that's it.
I'm not sure what to do now. I've tried reflashing the sboot.bin file, and I've tried flashing the 5.1.1 stock (COF8) ROM (which fails!)
Am I correct in thinking that the sboot.bin file will only boot 5.1.1 roms? If so, how do I get the ROM flashed if ODIN won't do it?
Any help will be greatly appreciated!

I've been thinking about this problem, and I've come up with two options. Either flash back to the original boot loader, kernel, etc. Or somehow get a stock 5.1 ROM to flash.
Any thoughts?
Sent from my (old) SGH-M919 using XDA Free mobile app

More info...
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.

SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
.
Click to expand...
Click to collapse
You are a lifesaver. More specifically a $579 saver.

Lovetoflyguy said:
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
Click to expand...
Click to collapse
Scratch that. I used PeaZip instead of WinRar or 7Zip. I didn't name it tar.md5, flashed and it's booting up now. We'll see if it works.
How did you get the new tarball file you made to pass the MD5 check? I can't get past that check when I make a new .tar file or tar.md5.

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Click to expand...
Click to collapse
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode

vegeta_badman said:
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
Click to expand...
Click to collapse
Always!!!! flash Odin files in Download mode.

i did everything as u said it...But i can not flash the STOCK (COF6) in odin it fails..plz help:crying:

Lovetoflyguy said:
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
Click to expand...
Click to collapse
how did you flash the firmware back to stock because i cant enter download mode:crying:

Bricked :(

I can't boot my phone, it says Custom binary blocked by FRP
I can't flash twrp, and whenever I try to flash a stock md5, odin fails
What do I do?

Update- I tried to flash a stock rom from http://forum.xda-developers.com/not...ware-firmware-kernel-modem-recovery-t2902574/
Results were
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk

Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.

nano303 said:
Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I booted it into recovery and got the Custom Binary Blocked message when I try to boot
glm0025 said:
Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.
Click to expand...
Click to collapse
I would, but I can't boot into recovery mode

Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working

aaronfrickinaustin said:
Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working
Click to expand...
Click to collapse
Which one worked?? Please tell me! Stuck in the same situation

This error is due to the Samsung Activation Lock being on before flashing a custom rom, be sure to turn this off in the future before installing another rom. If by chance you forget and get the error just try flashing back the stock version of the rom you currently have and it should come up.

System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )

Galaxy s6 System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 , 3.11 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )
(whitch version i should use to flash 920F or V or A ? )

[ROOT][ANDROID11][OFFICIAL][MAGİSK] Magisk 22.0 patched boot.img M51

Magisk 22.0 Patched Boot Image
I'm not responsible for any bricked device.
Installation
1- Just flash it via odin.
2- After 1-3 loops it will boot into recovery. Don't panic just format data from there.
3- Install Magisk-v22.0.apk
4- Open it and click "Okay"
5- Enjoy it.
I'll release in three days twrp and ofox for Android 11. Use this rooted boot image for now.​

Great Work.
Looking forward to your Android 11 TWRP soon.
any progress updates for us, maybe?

Thanks man, awesome work! Looking forward to try your twrp version!

Thanks for the patched image. Root was one of the primary things keeping me on Android 10. Good to know now there's root for Android 11 as well. Will definitely be using this when I upgrade.

Hi everybody. In this moment, I have root for Android 10 version. Does it possible to get smartphone updates (Android 11 included) and keep the current root without problems? Or Should I unroot the device and after that, update in Android 11 version? Thank you.

does this root option breaks the fuse? after which samsung in the event of a guarantee knows that something was done? knox flag?

odin error
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 64 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

userprince said:
odin error
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 64 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Enable developer options and make sure that oem unlock is on

userprince said:
developer option no longer has oem unlock option.
Click to expand...
Click to collapse
you have to either turn on the access to the net or wait a few hours, I had it in samsung and it appeared after a while

"I'll release in three days twrp and ofox for Android 11. Use this rooted boot image for now." - please do

Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.

M H N said:
Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.
Click to expand...
Click to collapse
Do step 1 and 3. But use beta twrp 3.5 beta 2

LahKeda said:
Do step 1 and 3. But use beta twrp 3.5 beta 2
Click to expand...
Click to collapse
Can you give me the link please

M H N said:
Can you give me the link please
Click to expand...
Click to collapse
Check twrp thread and download the latest build provided in the thread

Is there any bugs ?? Can I uninstall system apps ?

Do we need to unlock bootloader first?

aze89 said:
Great Work.
Looking forward to your Android 11 TWRP soon.
any progress updates for us, maybe?
Click to expand...
Click to collapse
i need to wait for the twrp manifests for a stable build but i can port an unstable beta for you users if you want.

anggabastian said:
Do we need to unlock bootloader first?
Click to expand...
Click to collapse
Yeah

abhi_ki said:
Is there any bugs ?? Can I uninstall system apps ?
Click to expand...
Click to collapse
No its stable u can uninstall system apps but be careful.

M H N said:
Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.
Click to expand...
Click to collapse
yeah its a part of android 11 you can use it