Using Flashtool to unlock the bootloading.
The volume down step is ok but the volume up step gives the error
Code:
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - ...
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: Command not allowed)
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.004s
Any advice?
Cheers
fredted40x said:
Using Flashtool to unlock the bootloading.
The volume down step is ok but the volume up step gives the error
Code:
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - ...
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: Command not allowed)
21/029/2015 16:29:00 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.004s
Any advice?
Cheers
Click to expand...
Click to collapse
You had a problem with drivers. Install these drivers, they worked with me.
Either that, or you're putting ulcode.txt into the wrong folder of flashtool. If you use the latest flashtool, make sure you put it into the appropriate subfolder of the registeredDevices subfolder of the .flashtool folder. If you don't use the latest flash tool, make sure you put it into the appropriate subfolder of the mydevices subfolder.
AforAnonymous said:
Either that, or you're putting ulcode.txt into the wrong folder of flashtool. If you use the latest flashtool, make sure you put it into the appropriate subfolder of the registeredDevices subfolder of the .flashtool folder. If you don't use the latest flash tool, make sure you put it into the appropriate subfolder of the mydevices subfolder.
Click to expand...
Click to collapse
Ty, just needed to copy the phones ulcode folder into the other folder
Related
[ICS Beta 4.0.3] fresh install + CWM + Bt-Wifi + Superuser.
Thanks to:
sonymobile.com; for releasing Ice Cream Sandwich (ICS) beta ROM for 2011 Xperia™ smartphones.
szl.kiev; for releasing ST18i-SE_Beta_StockKernel_4.1.C.0.7+CWM-boot.img for Xperia Ray.
features:
- pure stock ICS Beta kernel 4.1.C.0.7, only added CWM 5.5.0.4.
- on boot press any key once when gold/yellow LED triggered to enter CWM
soji89; for Superuser + Wifi-Bt Fix
1. Download Xperia-Ray_ICS_Beta_+_CWM.7z here;
mediafire.com/?60wkudjy32m978a
Copy/past link yourself because new users are not permitted to post outside links in their messages.
2. Download Xperia-Ray_ICS_Beta_Bt_Wifi_+_Superuser.zip here;
mediafire.com/?u29w2b93c1d11yp
Copy/past link yourself because new users are not permitted to post outside links in their messages.
3. Download Gapps-Lite_ICS_Beta_2011.12.30.zip here;
mediafire.com/?8ecf4a6si11op6l
Copy/past link yourself because new users are not permitted to post outside links in their messages.
4. Extract Xperia-Ray_ICS_Beta_+_CWM.7z to your Android Fastboot directory. For example: ..\android\fastboot.
now you have three beta ROM files.
5. Copy Xperia-Ray_ICS_Beta_Bt_Wifi_+_Superuser.zip to SD-card.
6. Copy Gapps-Lite_ICS_Beta_2011.12.30.zip to SD-card.
7. Now flash the three beta ROM files one by one using Fastboot. Using these three commands:
• fastboot flash boot boot.img
• fastboot flash userdata userdata.img
• fastboot flash system system.img
8. Once done, please reboot your phone.
9. On boot press any key once when gold/yellow LED triggered to enter CWM.
10. In CWM flash first Xperia-Ray_ICS_Beta_Bt_Wifi_+_Superuser.zip.
11. Then flash Gapps-Lite_ICS_Beta_2011.12.30.zip
12. Reboot your phone and enjoy.
are u sure this ICS never posted before???
These are stock ICS Beta files, only the boot.img file has been replaced for ST18i-SE_Beta_StockKernel_4.1.C.0.7+CWM-boot.img (by szl.kiev) so we can acces CWM.
I've got this while flashing:
09/045/2012 01:45:51 - INFO - Device Status: FASTBOOT mode
09/045/2012 01:45:58 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Soulee\Desktop\Xperia-Ray_ICS_Beta_+_CWM\system.img
09/045/2012 01:45:58 - INFO - Flashing selected kernel
09/046/2012 01:46:25 - INFO - FASTBOOT Output:
sending 'boot' (233434 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 26.193s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 26.196s
Any suggestions??
Soulee said:
I've got this while flashing:
09/045/2012 01:45:51 - INFO - Device Status: FASTBOOT mode
09/045/2012 01:45:58 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Soulee\Desktop\Xperia-Ray_ICS_Beta_+_CWM\system.img
09/045/2012 01:45:58 - INFO - Flashing selected kernel
09/046/2012 01:46:25 - INFO - FASTBOOT Output:
sending 'boot' (233434 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 26.193s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 26.196s
Any suggestions??
Click to expand...
Click to collapse
Are u serious?... You are flashing System partition image over Boot partition... Flashtool cant flash system img files.. it only flashes boot img...
Use ADB fastboot to flash system.img and userdata.img... google to know moew..
I've done it and now I have:
C:\Users\Soulee>fastboot flash boot boot.img
error: cannot load 'boot.img'
ok, I have gone back to GB. to recheck my steps in my first post,
and guess what? Everything works as it should if you follow the above steps
Hi all,
i tried several time to root my device, bot via flashtools and adb. As written in many guides here and around, I downgrade kernel, use binary method, then upgrade kernel again. When I switch on the phone, I have SU installed, and apps with su permission like Samba filesharing, work perfectly. I also have CWM recovery installed and working. But
I have problem when I want to flash a new kernel. This is the log of flashtools:
Code:
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:461) - Selected kernel (boot.img or kernel.sin): C:\Users\administración\Downloads\boot.img
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:465) - Flashing selected kernel
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (6726 KB)...
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.002s
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:467) - FASTBOOT Output:
sending 'boot' (6726 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:468) - Please check the log before rebooting into system
26/052/2013 15:52:46 - INFO - (FastBootToolboxGUI.java:231) - Finished Fastboot Toolbox
Any hint?
Sorry, I post in the wrong section. Please mod move it in General.
Thanks
R: Unable to root Xperia P
Rooted on fastboot/adb is unlocked,you have unlocked bootloader?
If no you cant flash kernel partition for now!
I'm trying to root my Xperia U, following the instructions here.
I have android 4.0.4 and build number 6.1.1.B.1.54.
I can connect to flashtool in fastboot mode without problem, but after selecting the C.10 kernel to flash I get a rather catch-22 error telling me that the device must be rooted first. USB debugging and unknown sources are on and the lock screen is off (I assume this is what 'PIN code' refers to in step 6 of the instructions). The flashtool log is below.
Am I missing something here? Any help would be appreciated.
17/005/2013 23:05:30 - INFO - Device disconnected
17/005/2013 23:05:30 - INFO - Device connected in fastboot mode
17/005/2013 23:05:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\A\Desktop\Root\New folder\kernel.sin
17/005/2013 23:05:40 - INFO - Flashing selected kernel
17/005/2013 23:05:40 - INFO - sending 'boot' (5293 KB)...
17/005/2013 23:05:40 - INFO - FAILED (remote: The Device must be rooted first)
17/005/2013 23:05:40 - INFO - finished. total time: 0.005s
17/005/2013 23:05:40 - INFO - FASTBOOT Output:
sending 'boot' (5293 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
L Asriel said:
I'm trying to root my Xperia U, following the instructions here.
I have android 4.0.4 and build number 6.1.1.B.1.54.
I can connect to flashtool in fastboot mode without problem, but after selecting the C.10 kernel to flash I get a rather catch-22 error telling me that the device must be rooted first. USB debugging and unknown sources are on and the lock screen is off (I assume this is what 'PIN code' refers to in step 6 of the instructions). The flashtool log is below.
Am I missing something here? Any help would be appreciated.
17/005/2013 23:05:30 - INFO - Device disconnected
17/005/2013 23:05:30 - INFO - Device connected in fastboot mode
17/005/2013 23:05:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\A\Desktop\Root\New folder\kernel.sin
17/005/2013 23:05:40 - INFO - Flashing selected kernel
17/005/2013 23:05:40 - INFO - sending 'boot' (5293 KB)...
17/005/2013 23:05:40 - INFO - FAILED (remote: The Device must be rooted first)
17/005/2013 23:05:40 - INFO - finished. total time: 0.005s
17/005/2013 23:05:40 - INFO - FASTBOOT Output:
sending 'boot' (5293 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
Click to expand...
Click to collapse
Interesting. You can try to run fastboot manually, it is under x10flasher_lib directory under flashtool.
Open x10flasher_lib directory and right click the content while pressing the shift key and select "Open command window here".
now type: fastboot flash boot "C:\Users\A\Desktop\Root\New folder\kernel.sin"
When you see the message "< waiting for device >", connect the phone in fastboot mode.
See if you get the same error.
if you're trying to root you need the b10 kernel not c10 and you need Flash mode, not fastboot
Sent from my AOSP 4.3 Xperia S via Tapatalk
L Asriel said:
I'm trying to root my Xperia U, following the instructions here.
I have android 4.0.4 and build number 6.1.1.B.1.54.
I can connect to flashtool in fastboot mode without problem, but after selecting the C.10 kernel to flash I get a rather catch-22 error telling me that the device must be rooted first. USB debugging and unknown sources are on and the lock screen is off (I assume this is what 'PIN code' refers to in step 6 of the instructions). The flashtool log is below.
Am I missing something here? Any help would be appreciated.
17/005/2013 23:05:30 - INFO - Device disconnected
17/005/2013 23:05:30 - INFO - Device connected in fastboot mode
17/005/2013 23:05:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\A\Desktop\Root\New folder\kernel.sin
17/005/2013 23:05:40 - INFO - Flashing selected kernel
17/005/2013 23:05:40 - INFO - sending 'boot' (5293 KB)...
17/005/2013 23:05:40 - INFO - FAILED (remote: The Device must be rooted first)
17/005/2013 23:05:40 - INFO - finished. total time: 0.005s
17/005/2013 23:05:40 - INFO - FASTBOOT Output:
sending 'boot' (5293 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
Click to expand...
Click to collapse
You need to unlock boot loader to flash custom kernel. You can root without flashing any custom kernel.
http://forum.xda-developers.com/showthread.php?t=1886460
AD9295 said:
You need to unlock boot loader to flash custom kernel. You can root without flashing any custom kernel.
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
you can flash stock kernel with flashtool. just untick everything else
Sent from my AOSP 4.3 Xperia S via Tapatalk
Thanks all, got this sorted by using flash mode and the kernels from here.
L Asriel said:
Thanks all, got this sorted by using flash mode and the kernels from here.
Click to expand...
Click to collapse
The other one was FTF too why do they tell to extract the kernel and flash in fastboot i don't know.
Here is the B.2.257 stock kernel I've extracted from the .257 firmware.
This is pure stock and I've done nothing to it.
DOWNLOADS:
SIN
https://drive.google.com/file/d/0B_rMaA9i_MUSb0tVMzR0X1pIQlU/edit?usp=sharing
ELF
https://drive.google.com/file/d/0B_rMaA9i_MUSWGN0UHVHOTNHX2s/edit?usp=sharing
Instructions:
Use flashtool to flash this kernel
Detailed Instructions:
- Use 'flashtool' - fastboot mode
- Select thunder icon
- Connent phone in fastboot mode ( volume up pressed while connecting to usb )
- Select 'fastboot' mode
- Click on 'select kernel to flash' - /Choose your .elf or .sin kernel
May I know which kernel to use for the C6833 LTE model ?
mobile88 said:
May I know which kernel to use for the C6833 LTE model ?
Click to expand...
Click to collapse
Yes both links are for the C6833. Reason is that it will work for all devices.
.sin and .elf are effectively the same. Its up to you which you want to flash.
Thank you
Sent from my C6833 using XDA Premium 4 mobile app
Great!!
This is the output I get when I flash using the provided instructions:
Code:
11/053/2013 11:53:06 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\jpruitt\Downloads\xperia\257-ftf-kernel\kernel.sin
11/053/2013 11:53:06 - INFO - Flashing selected kernel
11/053/2013 11:53:06 - INFO - sending 'boot' (8833 KB)...
11/053/2013 11:53:06 - INFO - OKAY [ 0.297s]
11/053/2013 11:53:06 - INFO - writing 'boot'...
11/053/2013 11:53:06 - INFO - FAILED (remote: image is not a boot image)
11/053/2013 11:53:06 - INFO - finished. total time: 0.300s
11/053/2013 11:53:06 - INFO - FASTBOOT Output:
sending 'boot' (8833 KB)...
OKAY [ 0.297s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.300s
11/053/2013 11:53:06 - INFO - Please check the log before rebooting into system
I tried flashing the 'elf' file too and got the same output.
Is it normal to see that error?
Am I doing something wrong?
majikfox said:
This is the output I get when I flash using the provided instructions:
Code:
11/053/2013 11:53:06 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\jpruitt\Downloads\xperia\257-ftf-kernel\kernel.sin
11/053/2013 11:53:06 - INFO - Flashing selected kernel
11/053/2013 11:53:06 - INFO - sending 'boot' (8833 KB)...
11/053/2013 11:53:06 - INFO - OKAY [ 0.297s]
11/053/2013 11:53:06 - INFO - writing 'boot'...
11/053/2013 11:53:06 - INFO - FAILED (remote: image is not a boot image)
11/053/2013 11:53:06 - INFO - finished. total time: 0.300s
11/053/2013 11:53:06 - INFO - FASTBOOT Output:
sending 'boot' (8833 KB)...
OKAY [ 0.297s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.300s
11/053/2013 11:53:06 - INFO - Please check the log before rebooting into system
I tried flashing the 'elf' file too and got the same output.
Is it normal to see that error?
Am I doing something wrong?
Click to expand...
Click to collapse
You're all set dude! Just ignore that
dyepnoodle said:
You're all set dude! Just ignore that
Click to expand...
Click to collapse
Thanks!
majikfox said:
Thanks!
Click to expand...
Click to collapse
Did u rename the file? Because when i downloaded it it says .bin at the end. Im downloading it incase i need to jump back from aosp to stock
dyepnoodle said:
Did u rename the file? Because when i downloaded it it says .bin at the end. Im downloading it incase i need to jump back from aosp to stock
Click to expand...
Click to collapse
i just downloaded both.
kernel.sin
kernel.elf
fine from my end.
dyepnoodle said:
Did u rename the file? Because when i downloaded it it says .bin at the end. Im downloading it incase i need to jump back from aosp to stock
Click to expand...
Click to collapse
If you download from chrome mobile on a Google drive account it somehow makes it a bin file. Just change to sin or elf or whatever you downloaded.
Sent from my C6833 using Tapatalk 4
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