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

pls z3x team i av samsung g925t it av v5.1.1 cant root to unlocked and av dwld firmware from support trying to flash so it can downgrade but i got error
here is the logs

Operation: Flash
Selected model: SM-G925T
Software version: 21.5

File analysis... OK
Total file size: 0xDB8E1740 (3512 Mb)
Searching USB Flash Interface... detected COM196
Setup connection... OK
Reading PIT from phone... OK
Sending boot.img... error timeout

Done with Samsung Tool PRO v.21.5

On phone it said

KEANEL REV. CHECK FAIL. DEVICE:2, BINARY:1

Phone hang now

What root is failing? Have you tried CF autoroot for the G920T? (I know you have the G925T)

Yes pls av try it i got error on phone RECOVERY IS NOT SEANDROID ENFORCING
it cant boot now only with logo

Seems like new update (5.1.1) is killing repaired phones.
I have 2 with the same problem.
Both were repaired (IMEI and Unlocked) and now are stuck on SAMSUNG logo after updating to 5.1.1

Any solution to this problem?

You need to flash this original firmware and make phone alive again
G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar
https://www.unlockbase.com/download/...e-firmware.zip

Then root it with Tennis root when phone is alive :D:D:D:D


then unlock it if you wish


Also there is no downgrade or upgrade for this phone at all, doesn't exist at any place for the moment any other firmware except the one above posted which can be found also on Z3X support site

i av dwld this firmware and the one on support site too but still getting error
KEANEL REV. CHECK FAIL. DEVICE:2, BINARY:1 on the phone and cant boot hang on logo

You might of done something wrong ... make sure you write the Original Firmware for the device ... and should be working back again ..

hello friend I have the same problem gave the update to 5.1.1 and now hangs in the logo and leaves install 5.0.2 if you find a solution let me know

makes perfect sense if you say that after repair imei 5.1.1 install stayed locked in the logo if so tmobile did a good job security but a headache for us ....

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).

I was thinking about that. Also it may be a possible cause that those who flashed a "efs" are now having this issue?

I know someone who tried twrp/cwm recoveries....it ticks the recovery with red letters on the upper left hand side...doesn't allow boot to recovery.

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.

So its blocking custom recoveries...why not just use a locked bootloader at that point? *shrug*

Right! Reminds me of Verizon and AT&T. Which is very strange, T-Mobile hasn't done that, this is bad...