Database Develop

Remake the phone warranty valid?

Hello guys,
Today when I tried to plug my headphones to listen to music, I noticed that the pone hardly recognises them. First I thought it was problem of the headphones but I tried to plug another and I almost must keep my finger pressing the cable where is plugged
So I think is problem of the headphone jack.
I have the bootloader unlocked so the warranty is void. I want to know if there is any method to lock it again to re valid the warranty
Sent from my XT890 using xda premium

Aljecama12 said:
Hello guys,
Today when I tried to plug my headphones to listen to music, I noticed that the pone hardly recognises them. First I thought it was problem of the headphones but I tried to plug another and I almost must keep my finger pressing the cable where is plugged
So I think is problem of the headphone jack.
I have the bootloader unlocked so the warranty is void. I want to know if there is any method to lock it again to re valid the warranty
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
It´s hard because when you did the Bootloader Unlock procedure on Motorola website you gave to them your IMEI, so theorically if you send the phone to repair it will be rejected.
But I don´t. Here on Brazil a lot of users had general problems with Razr i, sended the phone with BL unlocked to the technical support and got a new one... So I don´t know, it deppends of how stuff works with Motorola in your country..
The command "fastboot oem lock", or something else, doesn´t work as other phones. So the bootloader is not lockable again via PC...

WendelSchelhan said:
It´s hard because when you did the Bootloader Unlock procedure on Motorola website you gave to them your IMEI, so theorically if you send the phone to repair it will be rejected.
But I don´t. Here on Brazil a lot of users had general problems with Razr i, sended the phone with BL unlocked to the technical support and got a new one... So I don´t know, it deppends of how stuff works with Motorola in your country..
The command "fastboot oem lock", or something else, doesn´t work as other phones. So the bootloader is not lockable again via PC...
Click to expand...
Click to collapse
the command fastboot oem lock works, but two things:
The warranty is still void, because you require the code in the motorola website
The BL still show the "WARNING BOOTLOADER UNLOCKED" message
So if you want to lock the bootloader and don't want the "WARNING BOOTLOADER (...)" message follow this commands, This will delete your /data & /cache partition, and you need flash motorola signed files (firmware):
cd (firmware folder)
fastboot oem lock begin
fastboot flash boot boot_signed
fastboot flash bos bos_signed
fastboot flash cdrom cdrom_signed
fastboot flash gpt gpt_signed
fastboot flash motoboot motoboot
fastboot flash radio radio_signed
fastboot flash recovery recovery_signed
fastboot flash system system_signed
fastboot flash ulogo ulogo_signed
fastboot erase userdata
fastboot erase cache
fastboot oem lock
the first command will start the lock and wait for signed partitions, all the fastboot flash (...) commands will flash ALL the partitions signed's; the fastboot flash ulogo_logo will remove the "WARNING BOOTLOADER UNLOCKED" message; "fastboot erase (...)" will wipe the data partitions (required); Fastboot oem lock finalizes the bootloader lock process

Boss442 said:
the command fastboot oem lock works, but two things:
The warranty is still void, because you require the code in the motorola website
The BL still show the "WARNING BOOTLOADER UNLOCKED" message
So if you want to lock the bootloader and don't want the "WARNING BOOTLOADER (...)" message follow this commands, This will delete your /data & /cache partition, and you need flash motorola signed files (firmware):
cd (firmware folder)
fastboot oem lock begin
fastboot flash boot boot_signed
fastboot flash bos bos_signed
fastboot flash cdrom cdrom_signed
fastboot flash gpt gpt_signed
fastboot flash motoboot motoboot
fastboot flash radio radio_signed
fastboot flash recovery recovery_signed
fastboot flash system system_signed
fastboot flash ulogo ulogo_signed
fastboot erase userdata
fastboot erase cache
fastboot oem lock
the first command will start the lock and wait for signed partitions, all the fastboot flash (...) commands will flash ALL the partitions signed's; the fastboot flash ulogo_logo will remove the "WARNING BOOTLOADER UNLOCKED" message; "fastboot erase (...)" will wipe the data partitions (required); Fastboot oem lock finalizes the bootloader lock process
Click to expand...
Click to collapse
I didn´t knew about this. Stills impossible to remove WARNING BOOTLOADER UNLOCKED message on unlocked devices using this "fastboot flash ulogo ulogo_signed" command?

WendelSchelhan said:
I didn´t knew about this. Stills impossible to remove WARNING BOOTLOADER UNLOCKED message on unlocked devices using this "fastboot flash ulogo ulogo_signed" command?
Click to expand...
Click to collapse
No, Only fastboot flash ulogo logo_signed.
If you flash ulogo file still show warning bl unlocked, but if you do in fastboot "fastboot oem lock" they said: [FAIL] Already locked :silly: maybe motorola don't want the users relock the bootloader

Is our phone water resistant? Not submersions Because I had a problem when it was raining is that the problem? Does Motorola warranty covers this?
Sent from my XT890 using xda premium

Would do the same procedure on the Motorola Razr HD? In firmware does not have the files "bos_signed, gpt_signed, motoboot and radio_signed" if any can help, I really need. Grateful.

Flashing bootloader unlock image gets stuck on waiting for device.

My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.

SachK2 said:
My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.
Click to expand...
Click to collapse
I had a similar thing happen to me when I did my unlocking, fastboot doesn't recognise your phone, what happens if you send "fastboot -i 0x2b4c devices"?
Eventually I did figure it out but I can't remember the solution, but one thing that did work all the time was mauronofrio's multi-tool. https://forum.xda-developers.com/zu...ol-tool-one-driversunlocktwrpfactory-t3432782
Have a go, see if that works.

SachK2 said:
My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.
Click to expand...
Click to collapse
Hi, SachK2.
When I faced the same issue, installing the custom USB drivers that are usually attached to the bootloader unlock topic did the trick to me.

I tried the multi-tool but it gets stuck and crashes on the command window. I cant find the custom drivers download.

SachK2 said:
I tried the multi-tool but it gets stuck and crashes on the command window. I cant find the custom drivers download.
Click to expand...
Click to collapse
posting the links to another forum is disallowed here, though if I were in your shoes, I'd go on 4pda, search there zuk z2 pro topic and download the drivers there - wasn't able to find those drivers within xda yet
I'll also PM you the direct link so that you can check [the registration might be needed to be able to view and download the files]

fastboot getvar stuck

So I unlocked the bootloader for my Mi8, and now I'm trying to flash MIUI Global visa fastboot.
I'm running Linux and using USB2.0 with original cable and fastboot version 9.0.0_r30
When I type
Code:
fastboot devices
I can see that the phone is connected.
But when I try
Code:
fastboot getvar all
or any parameter for getvar , it just get stuck. By that I mean, the fastboot process hangs in there for a while and cannot be stopped with Crtl+C.
Also note that
Code:
fastboot oem device-info
works fine.
Another thing I noticed, when I repeate multiple instances of fastboot devices or oem device-info I get the 'press any key to shutdown'.
I'm not sure what is the problem. Any thoughts? I tried rebooting and changing USB ports but didn't help.

Bump

Unlock OEM via ADB

Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks

_08_ said:
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
Click to expand...
Click to collapse
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.

shihabrumel said:
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
Click to expand...
Click to collapse
It won't let me. It says:
my command: fastboot oem unlock System: FAILED (remote "flashing unlock is not allowed")
Fastboot: error: command failed.
Same with the critical. I also had an error trying another command, it said, not allowed in lock mode.
Actually, I'm trying other commands and it's the same error with all comands.

My Mi A2 was not booting
My mi a2 last updated to 19/04/05 pie version, then i install the Google camera using below steps..
1. Turn on debugging mode/oem & turn off the phone
2. Then power button+vol dwn Fastboot mode & connect to pc (Pc already have the adb)
3. In pc>adb>folder>Cmd> type "fastboot oem unlock"
4. Then factory reset the phone and reboot again to fastboot mode
5. Then boot the patched image for phone
6. Then install the magisk and gcam work perfectly.
Simply i used these methods
the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
But then I tried to relock the bootloader, using below commands on cmd
1. "adb reboot-bootloader"
2."fastboot oem lock"
I tried these 2 commands 4 or 5 times
But phone is not power on with locked bootloader. Then I unlock again oem and try again,, But not working,
Then i unlock bootloader again and try these commands to lock it again,
1. "adb reboot-bootloader"
2."fastboot flashing lock"
3. "fastboot oem lock"
Unfortunately it is not work, also i can't give command "fastboot oem unlock", also i can't turn on my phone, Please help me... I want to restore my phone to working mode... Please help me, Quick, urgent :crying::crying::crying::crying:

Question How to UNLOCK BOOTLOADER UNOFFICIALLY ?

Greetings!
As far as I know ASUS does not have a physical bootloader unlock counter like Samsung smartphones with their KNOX. This means that ASUS gets information about the unlocked bootloader via the internet when using their official unlock bootloader app. That is, ASUS gets the IMEI or S/N of the smartphone and puts it on their blacklist.
Is there any way to unlock the bootloader unofficially?
I really want to be able to get the bootloader back to its locked state and start getting and installing updates from my smartphone without using a PC as it was before the bootloader manipulation.

I tried these adb commands, but they don't work.
fastboot oem unlock
fastboot oem unlock confirm
fastboot oem asus-go
fastboot oem asus-go confirm
fastboot oem get_unlock_key
fastboot flashing unlock

fastboot oem asus-unlock working but i got error Verify unlock token fail.