So I tried to add a proxy on MiUnlock's fastboot.exe, here is the behavior I observed.
[MiUnlock checking the phone's lock status]
-s [serial number] oem lks
if lks = 1 // Means it's locked.
[Input]
oem get_token -s [serial number]
[Output]
(bootloader) token: VQECOgEQqNzRiT9Tkv/P1o1QGQ4fWQMIcGlzc2Fy
(bootloader) token: cm8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8Im
(bootloader) token: tOg=
Don't mind with the serial number, those parameters' will still work without it, it is for fastboot.exe targeting the phone, you will receive exactly same output without it.
My inference is that, this Base64 encoded information included Account Add Date and Phone Serial Number, for MiUnlock to check.
in the middle of data, cGlzc2Fycm (=) is Phone's Code, in Redmi 11's case, Pissarro.
We can infer that this divided the data into two parts.
VQECOgEQqNzRiT9Tkv/P1o1QGQ4fWQMI (Don't know if this "MI" at the end is for locating, haven't generate a second token(Rebind Account, which will reset your 168 hours.))
8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8ImtOg=
I haven't gained any progress on decoding them, it is highly likely that they are encoded with different Base64 rules.
I guess I'll try to remove Account Binding and bind it one more time to observe the Data alternation as for locating where is the date information encoded.
idk i don't think i can hack it anyway.
If you have any idea decoding it, welcome to share!
ok, after 4 hour I rebinding and this is new output
(bootloader) token: VQECOgEQIhLuo5o7ujbwTgaaRoFNBwMIcGlzc2Fy
(bootloader) token: cm8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8Im
(bootloader) token: tOg=
we are now completely sure that "MI" is for locating, and where does the date got encoded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I'm posting this on behalf of member zerabot.
Hi all.
Immediately apologize for my English, writing for the first time in 7 years)
If the moderators to correct mistakes, I'm not offended.
Maybe what I'll write to you is not new, but maybe useful to someone.
This is user manual for translation Android software into Your's native language.
Heare original of this instruction on russian
Download and install
Check My computer->Properties->additional->environment variables->Path
Is way to java heare? If no, add it.
this and this download and unpack to c:\windows
run console
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in command line
apktool d <way to *.apk> <way to dir>
download
http://artfulbits.com/Android/Localizer.aspx
open whith it <way to dir>
press + and add 2 letter code for you language
Translate all files from right spoiler
Delete not used files
When done in command line
apktool b <way to dir>
it create folders dist and build we need *.apk file in next steps from dist folder
in first time you need a key
to generate it in command line
keytool -genkey -alias <YourAliasName> -keyalg RSA -validity <NumberDays> -keystore <YourKeystoreFilename>
And finaly in command line
jarsigner <way to *.apk from dist filder> <YourAliasName>
Enter you password on keystore. And be happy.
This may be of some assistance to users, applies to any rom.
http://forum.xda-developers.com/showpost.php?p=8268893&postcount=3
Hi All Pros,
My phone stucks at this screen.
when power on, it stuck at this screen for long time until battery end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i know i have to look at this thread
but i not really see the steps to do it there.
Anyone please help to explain more/ guide me how to fix my phone ?
Thanks
MOD reset unlock tamper bit.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ?
tried to unlock before, but never success
2) What is the recovery already installed in your device ?
none, original cynogenmod recovery
3) What is the status of your device ? "fastboot oem device-info"
Unlock Bit - FALSE , Tamper Bit - TRUE
4) What error msg you got when tried to run command fastboot boot <custom_recovery.img>.
Failed ( remote: Device not unlocked cannot boot)
5) Steps you tried.
adb sideload CM-update file = not working.
Have a look here: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Thread closed because it looks like you are getting help here: http://forum.xda-developers.com/showthread.php?p=57701167
Please try not to ask things more than once because it becomes difficult for you and other people to keep track of the answers.
Thanks!
How unlock bootloader on alcatel v1 5001D 2019?When i use fastboot oem unlock command or fastboot flashing unlock on adb i get this error:
Rec_002
Watch "Rec_002" on Streamable.
streamable.com
Fastboot is not standardized, means Fastboot isn't equal Fastboot: how it's implemented depends on OEM/Carrier, it's not always the version as with a bootloader based off the latest AOSP code.
And most OEMs/Carriers nowadays have implemented their own version. Thus you can't expect that the Fastboot commands / options listet and described on hundreds of websites as also here on XDA are working.
Unlocking device's bootloader must be granted by OEM/carrier: have you checked this?
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Only if returned value is 1 it's supported.
BTW: Fastboot and ADB are 2 totally different things, don't confuse them.
Thats what i get when i type code.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For me it looks that ADB isn't got enabled on phone by you: Android Settings -> Developer options -> Allow USB debugging -> ON
Actually Allow Usb Debbuging and OEM Unlock are both on.
If not done yet, install the Android USB Driver provided by OEM for this Android device, too
Already done that.
I have been trying all day to access phone with adb tool tools but without any success. I have been searching and searching, but no luck. However newflasher does recognize my phone and flashtool says the device is in flash mode, but not ADB. There must be some explanation for this, Ive searched allover internet for an answer but no result. Thats why I am creating this thread and hope someone can help me with that.
I have a TAbackup, I restored it and run the command lines with success. I installed a stock rom with newflasher with success. Now I am trying relock the bootloader, but got into ADB not recognizing my device, and again newflasher does.
I get this from newflasher
Code:
Product: G8141
Version: 0.4-SONY-0.31
Bootloader version: 1306-5035_X_Boot_Sensured
Baseband version: 1306-8499_47.2.A.10.107
Serialno: Sensured
Secure: no
Loader version: XFL-Sensured-N-47
Phone ID: 0000:Sensured
Device ID: E691Sensured
Platform ID: 2005E0E1
Max download size: 104857600
Sector size: 4096
Rooting status: ROOTED
Ufs info: SAMSUNG,KLUCG4J1ED-B0C1,0200
Emmc info: FAILEmmc-info not supported
Default security: ON
Keystore counter: 1
Security state: BA1894F07A55612Sensured
Sake root: D159
S1 root: S1_Root_e69c
Root key hash: C30DEC2471CEA311E6918657367B5106Sensured
Current slot: F
When trying relock BL with flashtool I get this message
Code:
Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
ADB is not working on my PC
how to fix this ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot Control is an Android app that toggles the active boot slot.
Notes
It uses the same HIDL interface as bootctl to read the data and make the change.
Credits
@badabing2003 for the idea and for testing the many builds of both the app and bootctl
Latest Update
2023-06-22 v1.0.0-alpha02
capntrips said:
(...)
Latest Update
2023-06-22 v1.0.0-alpha02
Click to expand...
Click to collapse
BootControl-main.zip = 120 KB
BootControl-v1.0.0-alpha02.apk = 38.8 MB
Why such a drastic difference between SC and APK?
ze7zez said:
Why such a drastic difference between SC and APK?
Click to expand...
Click to collapse
The size of the source code has basically zero bearing on the size of the APK. As for why the APK is so large, I can sum that up with a link to one line in the app's build.gradle file.
The longer explanation is R8 breaks HIDL for some reason. I tried a variety of ProGuard rules with no luck. If I build it with Soong instead of Gradle it works fine, but it can't be installed on older devices. I may have been able to find a workaround for the latter issue, but it's much more convenient to build it with Gradle. Beyond that, the Soong build had issues with the Java HIDL interface, so I had to make a C++ library for HIDL and use JNI to interface with that, making the whole thing a bit more complex.
The broken minified Gradle build is ~8mb and the limited Soong build is ~14mb.
@capntrips
On p6, you need to disable verity (but not verification) in vbmeta on both slots to get Boot Control to switch slots without getting a corruption message.
Can the tool be modified to perform this task?