Related
Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked
Dear all
Huami has started locking their bootloaders (see the other thread) and, so far, has not offered any official way of unlocking the bootloaders to allow custom ROM flashing.
Due to the great work of our distinguished XDA developer Olivier (@kasakdor) :good: we have reverse engineered the unlock mechanism of the bootloader and can now offer to send you unlock codes for opening your bootloader again and flashing other software.
Please read and understand the following terms and conditions:
You unlock your bootloader on your own risk. Nobody else takes any responsibility on your actions and any possible consequences.
We are therefore NOT responsible for any bricked devices, invalid warranty claims, heart attacks or world wars.
Huami / Xiaomi will consider your warranty void. Do not contact Huami / Xiaomi or your dealer if anything goes wrong after you have unlocked your watch. Only YOU are responsible for the outcome of any modification you do.
This service is for personal usage only. Any identified commercial activities will be blocked.
A maximum of three unlock codes can be requested by each individual.
This service is provided free of charge. You accept that you cannot claim any charges towards us, if you are unhappy with the service or if the service does not work for you.
If ever Huami offers an official unlock service, we will stop our service. The goal is not to be in competition with Huami here, but only to provide something as long as they are not able to.
INSTRUCTIONS
You need to have fastboot installed and working correctly on your PC. You need to enter fastboot mode and get some information from your watch. Then go to the website https://unlockamazfit.com and enter your information. We will check your data and send you the unlock code. This can take 1-2 days typically.
We need to do the manual checking as we do NOT want to support any abuse (e.g. pirate companies reflashing watches).
If you have questions or feedback, please feel free to post here. Please also report briefly back, if the unlocking was successful.
Enjoy custom ROMs!
Before continue, please read the following:
[*] The approval process is manual, and it might take more than stated, have patience. If no unlock received within a week, contact by PM.
[*] Please keep track of the email used for the request, check in your trash and in your spam folder!
[*] DO NOT HAMMER THE SERVICE - if a request is made more than 3 times, it goes into a more detailed inspection and it takes more time for you to approve. No need in requesting 7 times.
[*] In case of an error during the filling of the form, stop and contact by PM - more retries will lock your SN/email.
[*] Once you've UNLOCKED YOUR SERIAL NUMBER - there is no need in unlocking it again after an update. if the watch gets locked, use the same unlock key.
[*] If additional help needed, do not hesitate in contacting in ENGLISH with all relevant information only: name, SN, email used.
[*] 2nd hand watches - unlock will be provided according to the original owner of the unit, make sure to have the details of the person you bought the watch from.
A detailed How to - please read before attempting, and then perform the steps.This process is not intended for the week of heart, so embrace yourself, winter is coming, and its going to unlock your bootloader! (excited kitten noises)
prerequisites:
1. ADB/fastboot knowledge, we're assuming that you do know how to enter your watch into fastboot, and how to obtain all the relevant information needed for a successful unlock.
2. Installed and functional Google ADB drivers - can be obtained from here - https://forum.xda-developers.com/showthread.php?t=2588979 , do not forget to install them as Administrator.
3. Additional microUSB cable - as seen, sometimes the original cable provided by Huami is not co-operative, so prepare another one.
4. Make sure that your watch has at least 60% of juice.
use this tool - https://toolaio.tk/
is has instant unlock built in.
Now ... for the fun part.
1. Reboot your watch into fastboot mode by
Code:
adb shell reboot bootloader
Make sure that you can see your watch in the Device Manager and it has its drivers installed!
2. while your watch is in the fastboot mode, type
Code:
fastboot getvar all
this will provide you with the following information
Code:
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version-bootloader: [B][COLOR="red"]U-Boot 2013.07-00096-gf3b140c[/COLOR][/B]
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: [B][COLOR="Red"]0123456789abcdef[/COLOR][/B]
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.280s
Besides the marked in bold, you will need the watch OS version, can be obtained from the settings in the watch -> tick the cog and go to the about section.
It is advised to double check the serial number provided by the fastboot with the one imprinted on the back of the watch, to make sure that its the correct one.
US/Global watches - 1612/1619/1811- the serial must be provided in a continuous format: 12345123456789
CN watches - 1602/1609/1801 - the serial must be provided in a divided with a / format: 12345/12345678
Very good!
I'll try tonight!
C:\adb>fastboot getvar all
< waiting for device >
Nothing more, any idead how to solve problem ?
Gruchi said:
C:\adb>fastboot getvar all
< waiting for device >
Nothing more, any idead how to solve problem ?
Click to expand...
Click to collapse
your watch needs to be in fastboot.
please read the description again.
Code:
adb shell reboot bootloader
Click to expand...
Click to collapse
it is in fastboot mode
C:\Users\Gruchi\Desktop>cd adb
C:\Users\Gruchi\Desktop\adb>adb shell reboot bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\Users\Gruchi\Desktop\adb>fastboot getvar all
< waiting for any device >
please post a screenshot of your device manager.
Try to use different cable, sometimes it should be problem.
Or other ADB drivers version...
Gruchi said:
it is in fastboot mode
C:\Users\Gruchi\Desktop>cd adb
C:\Users\Gruchi\Desktop\adb>adb shell reboot bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\Users\Gruchi\Desktop\adb>fastboot getvar all
< waiting for any device >
Click to expand...
Click to collapse
I got the code but I unlocked the smartwatch ... ... I tried several times but after entering the string by unlocking it tells me failed
Worked perfect!
MarcolinoV112 said:
I got the code but I unlocked the smartwatch ... ... I tried several times but after entering the string by unlocking it tells me failed
Click to expand...
Click to collapse
Send me a PM with a screenshot of fastboot and the command that failed.
Also for me error:
FAILED (remote: ED)
finished. total time: 0.078s
Worked just like the tutorial says. Many thanks !!!!
OS ver: 1.3.3a
US version
fastboot getvar unlocked
unlocked: yes
finished. total time: 0.033s
im geting always invalid serial number... and is the same on watch..
superino said:
Also for me error:
FAILED (remote: ED)
finished. total time: 0.078s
Click to expand...
Click to collapse
Hmm, I see that you and MarcolinoV112 both have OS 1.2.29i. Maybe Huami changed the mechanism already in that OS version.
jardaz said:
im geting always invalid serial number... and is the same on watch..
Click to expand...
Click to collapse
My bad i forget the / waiting for the email
Bootloader unlocked successfully! Many thanks!
(1.3.3a US)
Work many thanks 1.3.3a
FAILED (remote: ED)
finished. total time: 0.068s
With 1.3.3a :'(
Waiting for the unlock code in my email.
Hi everyone !
I'm a little stuck now, so i really need your help !
I want to install LineageOS on my Xiaomi redmi note 4. So i followed the installation instructions on official Lineage website.
At the step "Install TWRP recovery" i'm stuck.
Here are the logs :
Code:
> $ fastboot flash recovery twrp-3.1.0-0-mido.img
target reported max download size of 134217728 bytes
sending 'recovery' (26840 KB)...
OKAY [ 1.328s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.331s
So after searching on the web I tried splitting img into chunks with the following command :
Code:
> $ fastboot flash -S 20M recovery twrp-3.1.0-0-mido.img
Invalid sparse file format at header magi
sending sparse 'recovery' (20476 KB)...
OKAY [ 1.015s]
writing 'recovery'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 1.019s
I choosed 20M for my chunks randomly (inferior to recovery image of 26840KB).
Other informations :
I can't boot to origin system
I can access to fastboot
I can use adb but my device is in sideload mode
Please feel free to answer if you have any idea.
You're great! Thanks.
Did you already unlock the bootloader? It seems not yet..
crok.bic said:
Did you already unlock the bootloader? It seems not yet..
Click to expand...
Click to collapse
Yes I did !
Code:
> $ fastboot getvar all
...
(bootloader) unlocked: yes
...
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
crok.bic said:
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
Click to expand...
Click to collapse
I'm not sure if it's Mido or Nikel.
Do you have a link for Nikel ? Because it doesn't appear in twrp list :\
For adb i've downloaded with
Code:
sudo apt-get install android-tools-adb
I've tried with 3.1.1-0-mido and same error than 3.1.0 :\
@crok you really rock !
I've tried with this link of Nikel : https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/
And I'm having the recovery mode!
I continue the tutorial !
Great news. Please mark the thread [solved] just to help people who has the same trouble and seeking for info/solution.
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
ChaseRxx said:
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
Click to expand...
Click to collapse
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
ikolbyi said:
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
Click to expand...
Click to collapse
GL!
Enviado de meu BLA-L29 usando o Tapatalk
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
LLoTE said:
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
Click to expand...
Click to collapse
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
LLoTE said:
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
Click to expand...
Click to collapse
okay - steps?
ikolbyi said:
okay - steps?
Click to expand...
Click to collapse
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
LLoTE said:
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
Click to expand...
Click to collapse
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
LLoTE said:
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
Click to expand...
Click to collapse
Thank you. I'm new at this and learning.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
look at this one
Toggling OEM unlocking in developer options is not enough, as that simply enables the ability to unlock your bootloader within fastboot. You need to retrieve a bootloader unlock code either directly from Huawei or a third party. I believe there is a guide for it in the guides sub-forum.
LLoTE said:
look at this one
Click to expand...
Click to collapse
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
ikolbyi said:
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
Click to expand...
Click to collapse
And how will you edit it? You'll root the phone or?
LLoTE said:
And how will you edit it? You'll root the phone or?
Click to expand...
Click to collapse
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
ikolbyi said:
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
Click to expand...
Click to collapse
No problem man
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i_plevra said:
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Click to expand...
Click to collapse
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
alonsoj636 said:
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
Click to expand...
Click to collapse
This smartphone is a Japan-only model for a company called au, but probably a global version is available. The size is a little different but the base is redmi note 10 5g I just checked and it seems to be 5g I'm not confident I'll use miflash. It's a hassle to borrow a phone from a family member, stick a sim in it and have to receive an authentication SMS.
pihpih95 said:
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
Click to expand...
Click to collapse
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
now I can't use Windows for some reasons so am using m1 mac, this pc can't use the miflash so am trying GSI boot in a while
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
big problem...
your device is locked which means that flashing anything (vbmeta , recovery) or use MiFlash Tool will not be possible because unlocked bootloader is compulsory
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
do you still have mi recovery, or only have fastboot?
LR7875 said:
do you still have mi recovery, or only have fastboot?
Click to expand...
Click to collapse
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
i_plevra said:
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
Click to expand...
Click to collapse
and does fastboot oem unlock or fastboot oem unlock_critical work
LR7875 said:
and does fastboot oem unlock or fastboot oem unlock_critical work
Click to expand...
Click to collapse
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
have u apply to unlock bootloader through official method ?
i_plevra said:
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...oken-verify-failed-reboot-the-device.4300755/ this is for redmi note 10 pro but is worth to read. maybe it can help