Time to Updat QLM - GSM-Forum

unlock in nepal · 09-07-2018, 11:45

Updat MI Phone MI Account relock Salutaion & support New phone

MI Note 5 Pro Connacting Error

Wait for phone...
Device Found!
Initialize ...
Handshake passed!
ID_BLOCK_I : FFA648A5
ID_BLOCK_S : F7B7DD2A
ID_BLOCK_L : D4C0C8563DDAF04974BA909221DB0F21
ID_BLOCK_L : 8D1EA52823490854FF27F6C25C1F3B74
Use CM2 Internal Loader

ERROR : Prepare target failed! Unsupported yet CPU!
INFO : Send log and report.log to support! Include device info also!

Reconnect Power/Cable!

PASSIONATE_BOYS · 09-07-2018, 15:05

Hello,
About update work is in progress. When update will be ready team will release it.
Regarding Note 5 pro, Y2, A3S etc latest models they all need authentication from manufacturer server which needs legit login, so until other way is found it's not possible.

Br.
Infinity Box Team.

rebainoor · 09-08-2018, 23:15

these phones have new authentication system (done by Xiaomi)
i call it SIG, because them added new command to his Firehose programmer's.

Things to need to know:
1. QC was always implemented SW_VERSION (RollBack) tag in his certificate
validation schema, but nobody was used it before (Except Samsung and LG)
2. After FireHose is Validated, OEM manufacturer is free to add his own
secondary authentication (First was introduced in old SE phones which was need
SE validation card, now old golden idea was taken by Xiaomi and auth protocol
moved to server)

So what in fact we can do:
1. Need to Have FireHose Programmer signed to current eFuse Value
with sme HW_ID and Higher or Same SW_ID (Included RollBack Version)
tags without a SIG authentication extension.
Here is importan RollBack Version, is activated then tag value is > 0

How we can recognize it:
Unfortunatelly Sahara Protocol, not let us to read SW_ID tag and
choose right RollBack Satisfied Firehose Automatically
Fast boot "getvar:all" will show "RollBack Version" or "Anti" Variable
who reflects RollBack (SW_VERSION) value

How to check is FireHose Ready to do jobs:
Jus Open it wih notepad and look for "SW_ID"
Here You will see Hex Value string: 0000000200000003 SW_ID
Here You see RollBack (SW Version) = 2
So with this FireHose can serve : RB: 0, 1, 2 and cannot work with 3, 4, ...

How to see is FireHose Need Xiaomi Authentication or not
is same open with note pad and search for this string: "sig "
(white space is important here)
if not found "sig " - you are lucky: this FireHose not need it.

And for sure do not forget that Root CA HASH must be same as is in eFuse (QFPROM)

09-07-2018, 11:45	#1 (permalink)
unlock in nepal No Life Poster Join Date: Nov 2011 Location: Student Posts: 1,225 Member: 1686564 Status: Offline Sonork: PM me Thanks Meter: 157	Time to Updat QLM Updat MI Phone MI Account relock Salutaion & support New phone MI Note 5 Pro Connacting Error Wait for phone... Device Found! Initialize ... Handshake passed! ID_BLOCK_I : FFA648A5 ID_BLOCK_S : F7B7DD2A ID_BLOCK_L : D4C0C8563DDAF04974BA909221DB0F21 ID_BLOCK_L : 8D1EA52823490854FF27F6C25C1F3B74 Use CM2 Internal Loader ERROR : Prepare target failed! Unsupported yet CPU! INFO : Send log and report.log to support! Include device info also! Reconnect Power/Cable!

09-07-2018, 15:05	#2 (permalink)
PASSIONATE_BOYS No Life Poster Join Date: Jul 2007 Location: Infinity-Box Support- Posts: 9,321 Member: 541591 Status: Offline Sonork: 100.1611509 Thanks Meter: 7,361	Hello, About update work is in progress. When update will be ready team will release it. Regarding Note 5 pro, Y2, A3S etc latest models they all need authentication from manufacturer server which needs legit login, so until other way is found it's not possible. Br. Infinity Box Team.

09-08-2018, 23:15	#3 (permalink)
rebainoor No Life Poster Join Date: Feb 2006 Location: In my LAB Posts: 3,163 Member: 231728 Status: Offline Thanks Meter: 2,103	these phones have new authentication system (done by Xiaomi) i call it SIG, because them added new command to his Firehose programmer's. Things to need to know: 1. QC was always implemented SW_VERSION (RollBack) tag in his certificate validation schema, but nobody was used it before (Except Samsung and LG) 2. After FireHose is Validated, OEM manufacturer is free to add his own secondary authentication (First was introduced in old SE phones which was need SE validation card, now old golden idea was taken by Xiaomi and auth protocol moved to server) So what in fact we can do: 1. Need to Have FireHose Programmer signed to current eFuse Value with sme HW_ID and Higher or Same SW_ID (Included RollBack Version) tags without a SIG authentication extension. Here is importan RollBack Version, is activated then tag value is > 0 How we can recognize it: Unfortunatelly Sahara Protocol, not let us to read SW_ID tag and choose right RollBack Satisfied Firehose Automatically Fast boot "getvar:all" will show "RollBack Version" or "Anti" Variable who reflects RollBack (SW_VERSION) value How to check is FireHose Ready to do jobs: Jus Open it wih notepad and look for "SW_ID" Here You will see Hex Value string: 0000000200000003 SW_ID Here You see RollBack (SW Version) = 2 So with this FireHose can serve : RB: 0, 1, 2 and cannot work with 3, 4, ... How to see is FireHose Need Xiaomi Authentication or not is same open with note pad and search for this string: "sig " (white space is important here) if not found "sig " - you are lucky: this FireHose not need it. And for sure do not forget that Root CA HASH must be same as is in eFuse (QFPROM)