Is there any Mi flash tool for mac os?
If yes plz share link.....
android_smater said:
Is there any Mi flash tool for mac os?
If yes plz share link.....
Click to expand...
Click to collapse
Why do you need Mi flash tool when you can do it via terminal?
Install adb/fastboot drivers, go to launchpad-terminal, use fastboot devices to check if the device is connected.
Go the folder where you've downloaded the fastboot files and than make executable script with "chmod +x ./*.sh" and than flash the fastboot files on your phone by "./flash_all.sh".
Same script is created as an user interface if you find the above method difficult, check this
https://github.com/Somnius/MiFlash-for-Mac
I am compiled a post to do equivalent of mi flash tool from mac or linux
Unbricking Android with mac/linux
How to unbrick soft brick with mac/linux
erluxman.com
naturist said:
Why do you need Mi flash tool when you can do it via terminal?
Install adb/fastboot drivers, go to launchpad-terminal, use fastboot devices to check if the device is connected.
Go the folder where you've downloaded the fastboot files and than make executable script with "chmod +x ./*.sh" and than flash the fastboot files on your phone by "./flash_all.sh".
Same script is created as an user interface if you find the above method difficult, check this
https://github.com/Somnius/MiFlash-for-Mac
Click to expand...
Click to collapse
-imac platform-tools % chmod +x ./*.sh
-imac platform-tools % ./flash_all.sh
product: lavender
Sending 'antirbpass' (8 KB) OKAY [ 0.009s]
Writing 'antirbpass' OKAY [ 0.000s]
Finished. Total time: 0.012s
Sending 'xbl' (2510 KB) OKAY [ 0.090s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Related
Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam
webbsimax said:
Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam
Click to expand...
Click to collapse
I have the same issue. I mean I didn't tried to copy with windows because I don't have it.
I'm trying to find any usefull information how to flash recovery with fastboot to my dell streak 5 under ubuntu for 2 days but I haden't found solution.
Whenever I want to send file in fastboot mode I get:
Code:
[email protected]:~/Pobrane/DSC_flashme2$ sudo fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (15780 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
any ideas what to do?
Code:
sudo fastboot -i 0x413c reboot
works fine
I have the same issue
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86
abr4xas said:
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86
Click to expand...
Click to collapse
obviously it will fail because you are not using the one for streak 5. we have our own working recovery you know.
Had the same problem, using an other fastboot (the one found on http://forum.xda-developers.com/showthread.php?t=1067273) was the solution for me. I'm using a 64-bit Ubuntu 12.04.
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
blue9a said:
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
Click to expand...
Click to collapse
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Davey126 said:
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Click to expand...
Click to collapse
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
blue9a said:
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
Click to expand...
Click to collapse
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Davey126 said:
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Click to expand...
Click to collapse
python3 /home/jeremy/Desktop/cuberHDX.py 0x45202b1325
File "/home/jeremy/Desktop/cuberHDX.py", line 64
print 'Usage: %s [boot.img|serial]' % path.basename(argv[0])
^
SyntaxError: invalid syntax
hmm not sure if i did this right
[email protected]:~$ fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: true
OKAY [ 0.036s]
finished. total time: 0.036s
[email protected]:~$ -i 0x1949 oem unlock 0x45202b1325
-i: command not found
[email protected]:~$ /fastboot -i 0x1949 devices
bash: /fastboot: No such file or directory
[email protected]:~$ fastboot -i 0x1949 devices
D0FCA0A03523013E fastboot
[email protected]:~$ fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
error: cannot load 'unlock.signed': No such file or directory
[email protected]:~$ fastboot -i 0x1949 flash boot '/media/jeremy/MULTIBOOT/boot.img'
target reported max download size of 536870912 bytes
sending 'boot' (6884 KB)...
OKAY [ 0.290s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.341s
[email protected]:~$ fastboot -i 0x1949 flash unlock '/media/jeremy/MULTIBOOT/unlock.img'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.084s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
[email protected]:~$ python cuberHDX.py 45202b1325
python: can't open file 'cuberHDX.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py 45202b1325
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ '/media/jeremy/MULTIBOOT/cuber.py' 45202b1325
bash: /media/jeremy/MULTIBOOT/cuber.py: Permission denied
[email protected]:~$ '/home/jeremy/Desktop/cuber.py' 45202b1325
bash: /home/jeremy/Desktop/cuber.py: Permission denied
[email protected]:~$ python '/home/jeremy/Desktop/cuber.py' 45202b1325
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Your unlock code is in '45202b1325.unlock'.
[email protected]:~$ fastboot -i 0x1949 flash unlock '/home/jeremy/45202b1325.unlock'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.142s
[email protected]:~$ /cuber_unlockbl --sign ./'/home/jeremy/Desktop/unlock.img' ./ '/home/jeremy/45202b1325.unlock'
bash: /cuber_unlockbl: No such file or directory
[email protected]:~$ python ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file './cuber_unlockbl': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuberHDX.py [boot.img|serial]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cublock.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cublock.py manfid serial
[email protected]:~$
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
blue9a said:
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
Click to expand...
Click to collapse
Can't unlock bootloader versions >3.2.3.2; can't flash with a locked BL. Your device is bricked.
Here is what I did.
Phone was running with Android 6.0+EMUI4.0 beta version. I unlocked the bootloader by acquiring unlock code from Huawei website.
After unlocking bootloader, when I try to flash TWRP, it says
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kiwi_twrp_5-14_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45116 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
I tried above procedure several times but no luck. So I rebooted my devices, and then booted it again in bootloader mode and then fired command to flash recovery, but this time new error came:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kiwi_twrp_5-14_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45116 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
In both of the above cases fastboot devices working good and showing my device in the list. Please help me here :crying:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
but still on windows 10 unable to run Shift + Command Prompt on the adb folder aswell it reboots on adb but still not able to open the .img file
kartrikpal said:
but still on windows 10 unable to run Shift + Command Prompt on the adb folder aswell it reboots on adb but still not able to open the .img file
Click to expand...
Click to collapse
are you serious ? you can't right click and choose open command prompt here ?
and what .img are you trying to open ? are you trying to flash twrp ?
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\fastboot>adb devices
List of devices attached
GFMDU1********** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\kiwi_recovery.img
downloading 'boot.img'...
OKAY [ 1.433s]
booting...
OKAY [ 0.020s]
finished. total time: 1.455s
C:\fastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.002s
C:\fastboot>
clsA said:
are you serious ? you can't right click and choose open command prompt here ?
and what .img are you trying to open ? are you trying to flash twrp ?
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\fastboot>adb devices
List of devices attached
GFMDU1********** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\kiwi_recovery.img
downloading 'boot.img'...
OKAY [ 1.433s]
booting...
OKAY [ 0.020s]
finished. total time: 1.455s
C:\fastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.002s
C:\fastboot>
Click to expand...
Click to collapse
Yes, i'm unable to do that, instead just unlocked my Phone using Windows 10 and Flashed Twrp.img using Ubuntu - Using Linux its that easy but on Windows 10 it force closes ! I could not find solution .
@clsA
Anyways i'm done with Flashing but after first boot there was seemless WiFi speed seen as i have 2MbPs connection but after few hours of restoring my apps using PS it started to load slow - is there any fixes ?
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
Thank you very much...i should have come here before spending my 1 hour on trying everything else!!:good::good:
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
That is great, I'll keep it in mind always when I face issues
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