Samsung 6 edge G925T v5.1.1 root failed downgrade to v5.0.1

[APUAK47]

Originally Posted by ecs87

So...has anyone tried twrp/cwm? Afaik, custom recoveries normally work in the event that direct kernel roots and cf roots dont work. (Please dont ask where to get a custom recovery or how to use it...these things are easily searchable and will result in a lmgtfy response from me).

if you already deal with TWRP and does not work in Odin she gives me pass but says recovery is not seandroid enforcing seems to have locked bootloader.

[F_X]

Originally Posted by meraz9000

IMEI repaired S6 edge..for testing purposes updated to 5.1.1 . Phone will not boot. I flashed stock original EFS and phone came back on just fine..also you cannot downgrade due to new boot loader.

Hmm. Did you flash another efs (to unlock)? Or just IMEI repair?

[xk3r]

Originally Posted by F_X

Hmm. Did you flash another efs (to unlock)? Or just IMEI repair?

seems like if you play with efs then update the phone get bricked.
They blocked the boot loader and also implement that security for modified EFS and phone stuck on samsung logo forever, Hope that some one find a solution for that.

[meraz9000]

Originally Posted by F_X

Hmm. Did you flash another efs (to unlock)? Or just IMEI repair?

just repair via usb. no rooting.so gonna have to get unblacklisted via imei.

[F_X]

Originally Posted by xk3r

seems like if you play with efs then update the phone get bricked.
They blocked the boot loader and also implement that security for modified EFS and phone stuck on samsung logo forever, Hope that some one find a solution for that.

According to our analysis it appears to be so. In that case phone must be AS IS in order for the update to work. If that's the case, then everyone who unlocked the phones via efs is now going to get customers screaming at them.

Originally Posted by meraz9000

just repair via usb. no rooting.so gonna have to get unblacklisted via imei.

Strange, in that case you wiped the imei via download mode?

[xk3r]

Originally Posted by F_X

According to our analysis it appears to be so. In that case phone must be AS IS in order for the update to work. If that's the case, then everyone who unlocked the phones via efs is now going to get customers screaming at them.



Strange, in that case you wiped the imei via download mode?

I got customers with that problem already, Seems like SAMSUNG is trying to get out of the Repair Business.

[meraz9000]

Originally Posted by F_X

According to our analysis it appears to be so. In that case phone must be AS IS in order for the update to work. If that's the case, then everyone who unlocked the phones via efs is now going to get customers screaming at them.



Strange, in that case you wiped the imei via download mode?

Ran two tests..one wiped efs using download mode = brick

Using Z3x aka ADB DD = brick

Luckily for all my customers i have their original efs backups and i will pass the blame to samsung if they scream at me.

[APUAK47]

Originally Posted by meraz9000

Ran two tests..one wiped efs using download mode = brick

Using Z3x aka ADB DD = brick

Luckily for all my customers i have their original efs backups and i will pass the blame to samsung if they scream at me.

I mean you say that if I restore the original copy EFS does not stay in the logo?

[F_X]

Originally Posted by xk3r

I got customers with that problem already, Seems like SAMSUNG is trying to get out of the Repair Business.

Looks like they've finally found a way to block out that field of business...or at least for now

Originally Posted by meraz9000

Ran two tests..one wiped efs using download mode = brick

Using Z3x aka ADB DD = brick

Luckily for all my customers i have their original efs backups and i will pass the blame to samsung if they scream at me.

Haha sounds "reasonable"

I meant as in when you repaired the imei, did you wipe via download mode?

[Ahmad-Hzzory]

any one have arabic flash

[F_X]

Originally Posted by APUAK47

I mean you say that if I restore the original copy EFS does not stay in the logo?

Nope, looks like stock EFS is the only way to fix this issue. Somehow their security doesn't allow any tampered efs to be carried onto the update, some update huh?

[meraz9000]

Originally Posted by F_X

Looks like they've finally found a way to block out that field of business...or at least for now



Haha sounds "reasonable"

I meant as in when you repaired the imei, did you wipe via download mode?

yeah both download mode and nother using z3x

[F_X]

Originally Posted by meraz9000

yeah both download mode and nother using z3x

Alright just making sure, thanks bro! I want to see if this is also going on to those who unlocked the G925T using that file..it shouldn't since it carries the original imei, then we'll know a bit more in depth of what the issue may be.

[meraz9000]

Originally Posted by F_X

Alright just making sure, thanks bro! I want to see if this is also going on to those who unlocked the G925T using that file..it shouldn't since it carries the original imei, then we'll know a bit more in depth of what the issue may be.

I read some reports in XDA from ppl that got unlocked via cable remotely and they phone is bricked too.

[F_X]

Originally Posted by meraz9000

I read some reports in XDA from ppl that got unlocked via cable remotely and they phone is bricked too.

I understand, well now that means that it definitely has to do with the sda3 & probably the sda8 efs partitions.