Xiaomi Redmi 3s, Redmi 3s Prime launched

I'll definitely post a solution if i find it.

I've started a thread in the complaints section. Mod asked me to donload a dev rom. 1.4 friggin gb later, no luck.

looks like whenever the xiaomi servers update the info, could be days/weeks/months, then it'll work. till then, tough luck.

stupid POS company.
 
Charun said:
It seems there is no end to these errors, i tried almost all the methods out there to solve the "couldnt verify device" error which comes at 50%

In case u find a solution let me know
The only method i havent tried it the hard reset method, search for it and post here if it works
Click to expand...
Wait for couple days and try it again, It's a known error also I has nothing to do with Dev or stable rom works on stable have personally unlocked 2 phones on stable.
 
So when you go to the miui forum, it shows your miui version under your profile, both next to your posts and in your settings. Mine is still showing 8.0.3.0 (stable) even after changing to dev version 6.10.13. I guess whenever the server sees that change, then the unlock might work.
 
Charun said:
It seems there is no end to these errors, i tried almost all the methods out there to solve the "couldnt verify device" error which comes at 50%

In case u find a solution let me know
The only method i havent tried it the hard reset method, search for it and post here if it works
Click to expand...

Can you check something? go to your MiFlashUnlock_1.1.0317.1_en folder and delete the logs in the in the log subfolder. Then first connect the phone in fastboot mode to USB, and run the unlock tool. Don't enter your username or login. Go to the log folder and open the log file. Scroll through all the stuff till you reach the first DEBUG line. These are the lines from mine:

Code: 
DEBUG  <08:33:52.015,T:1612> : Initializing native downloader...
INFO   <08:33:52.015,T:1612> : init resource C:\MiFlashUnlock_1.1.0317.1_en\res\ language:en region:
ERROR  <08:33:52.218,T:3936> : Can't identify device in fastboot mode.(num=0)
INFO   <08:34:04.671,T:5092> : to login by name:XXX pwd:XXX sid:XXX verify:EMPTY sec_token:EMPTY
INFO   <08:34:04.687,T:5092> : LoginStep1
DEBUG  <08:34:06.078,T:5092> : OnAccountLoggedIn
DEBUG  <08:34:07.437,T:5092> : OnNewServiceCookies
DEBUG  <08:34:07.437,T:5092> : Login success and get user detail
INFO   <08:34:10.328,T:6084> : status result: {   "applyStatus" : 2,   "code" : 0,   "description" : null,   "shouldApply" : true,   "uid" : 1606076227}
DEBUG  <08:34:10.328,T:6084> : unlock status: 2
DEBUG  <08:34:10.328,T:6084> : should apply:true
INFO   <08:34:13.062,T:1612> : land connected
DEBUG  <08:34:15.656,T:0156> : VerifyDeviceInfo
DEBUG  <08:34:15.703,T:0156> : to sign token with key for device:
DEBUG  <08:34:40.078,T:0156> : sign result:{   "code" : 20031,   "description" : "账号与设备没有绑定关系",   "uid" : 1606076227}
ERROR  <08:34:40.078,T:0156> : unlock signature request fail:20031 reason:账号与设备没有绑定关系
DEBUG  <08:34:40.078,T:0156> : unlock return:20031 msg:账号与设备没有绑定关系
INFO   <08:34:42.859,T:1612> : UIWindow::OnWindowProc: received CWM_GLOBAL_PROCESS_CLOSE message.

My guess is the ERROR line means the unlock tool is unable to properly identify the connected device, and it's nothing to do with a different account on the server. As long as the device can't be identified, it probably will never authenticate it because it can't read the signature.

I'm going to try flashing a china dev rom via miflash to check. So far i've been trying using the upgrade rom option inside miui itself.[DOUBLEPOST=1476977304][/DOUBLEPOST]Great, now it's worse. Not only was the dev rom suggestion by that mod useless, but now i can't even rollback to miui7, because dev --> stable is a no no. And can't flash a fastboot rom either because even edl mode seems to be blocked. Xiaomi's really locked down this one. All those with older 3s batch phones should be very careful not to update and first unlock their bootloaders if possible.
 
Last edited by a moderator:
Nope, mine says made in AP.

Quality is not the issue here. It's Xiaomi's retarded and poorly implemented (though well-intentioned) bootloader unlocking policy.

My guess now is that the unlock tool from march simply doesn't recognize the 3sP signature as a valid device.[DOUBLEPOST=1476997794][/DOUBLEPOST]Successfully managed to revert back to 7.5.9.0 stable by modding a 'deep flash' usb cable so i could enter edl mode and flash the rom. Still no luck with the unlock though.
 
Last edited by a moderator:
By cannot i meant, i don't want to, and never login to google on any new android phone without first disabling the hangouts app. Once hangouts is logged in, it's very hard to log out of it completely. There was a very complicated process to do so and i don't want to go through that again. Even when logged out it shows you as available.

In miui7 you can sucessfully disable some system apps, the problem is certain ones, i think google app and TTS if disabled, cause a bootloop. This is probably why miui8 doesn't allow you to disable ANY system apps.

I don't understand why these apps are in /system anyway. The are all frequently updated and the updates all go into /data, making the original version apk in system redundant and a waste of space.[DOUBLEPOST=1477094267][/DOUBLEPOST]
Update on the unlock:

I did some more digging and I think the current mi unlock tool simply does not recognize or support the redmi 3s.

See my thread here for more details.[DOUBLEPOST=1477142086][/DOUBLEPOST]So people replied saying that even though the unlock tool shows that error, and even though the 3sP is not in the device info file, it still can be unlocked. Just takes time. So waiting game it is...
 
Last edited by a moderator:
Can someone with a rooted redmi 3s help me? I need a qcn file extracted.
 
Last edited by a moderator:
Back
Top