Database Info

update broke up>!

HELP.!!
i bought a W200A version, AW was 1.5 and android version was 6
so i tried system update to AW 2.0 , but after it showed me the update message and i accepted it my watch went to fastboot menu and don't even enter recovery mode.!!! it always restart on fastboot menu.!!
and i can't enable secure boot so that i could make a sideloading update
CAN ANYONE HELP ME IN THAT IN STEPS PLEASE?
{
"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"
}

etch_sam_etch said:
HELP.!!
i bought a W200A version, AW was 1.5 and android version was 6
so i tried system update to AW 2.0 , but after it showed me the update message and i accepted it my watch went to fastboot menu and don't even enter recovery mode.!!! it always restart on fastboot menu.!!
and i can't enable secure boot so that i could make a sideloading update
CAN ANYONE HELP ME IN THAT IN STEPS PLEASE?
Click to expand...
Click to collapse
Just flash the full image through the bootloader.

g33k3r said:
Just flash the full image through the bootloader.
Click to expand...
Click to collapse
nothing happened... it keep showing fastboot menu
it show me this message while flashing
--------------------------------------------
Bootloader Version...: NEMOZ20m
Baseband Version.....: M8926-4.0.06.0.10
Serial Number........: 0a9260f3fecbb88d
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'NEMOZ20m'.
Update requires 'NEMOZ20c'.
finished. total time: 0.036s
Press any key to exit...

have you installed ADB? have you correct drivers?

Mate 8 Oreo Can't unlock bootloader

Hello xda,
{
"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"
}
and when i try to unlock in fastboot
...
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
finished. total time: 0.013s
if you have any idea of what cause it
Rogafe

rogaf said:
Hello xda,
and when i try to unlock in fastboot
...
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
finished. total time: 0.013s
if you have any idea of what cause it
Rogafe
Click to expand...
Click to collapse
Hmm I can't even see that option anymore on my phone, updated to Oreo a couple of days ago
Sent from my HUAWEI NXT-DL00 using Tapatalk

rogaf said:
Hello xda,
and when i try to unlock in fastboot
...
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
finished. total time: 0.013s
if you have any idea of what cause it
Rogafe
Click to expand...
Click to collapse
i think i 'm stuck like you
availables solutions are :
1- get the FRP key and unlock it via fastboot then unlock bootloader.
2- flash the correct firmware with tool that use Dload mode (dc-phoanix.....)

So I have roll back to emui 5 (with dc phoenix and hcu thanks to them) and I will wait that I have more time to understand how to go to oreo thanks for all your answer

twrp installation doesn't work

Hello.
I have a Moto G of 1st generation (falcon) with lollipop and I need to upgrade Android and install root.
I can't proceed because I am unable to install twrp.
This is the commands and responses that I get on PC.
Code:
# fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.011s]
finished. total time: 0.011s
# fastboot flash recovery twrp-3.3.1-0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9612 KB)...
OKAY [ 0.325s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.337s
# fastboot boot twrp-3.3.1-0-falcon.img
downloading 'boot.img'...
OKAY [ 0.331s]
booting...
FAILED (remote failure)
finished. total time: 0.333s
This is what appears on the cell phone:
{
"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"
}

Zegame said:
Hello.
I have a Moto G of 1st generation (falcon) with lollipop and I need to upgrade Android and install root.
I can't proceed because I am unable to install twrp.
This is the commands and responses that I get on PC.
This is what appears on the cell phone:
Click to expand...
Click to collapse
Bootloader must be unlocked.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs

Thanks, it is working.

ADB does not recognize my device

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"
}

Question About the Bootloader Lock

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"
}