[TUT] unlock bootloader, TWRP, root xperia m4 aqua [complete step]
check first by this code use phone dialler
*#*#7378423#*#* , if bootloader unlocked = yes , so you can root it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
must download it first
1. flashtool -0.9.18.4-windows > https://mega.nz/#!ThcRmQwD!x_X-U6g8bsucC5d6O5z0U7KK2W69LzrkVbBqfIubhdI
2. adb > https://mega.nz/#!ywUwFLpK!LmlAnwl8AS27wJzNjqBF7vpfvJHSz5pGer-XHOIVF6o
3. twrp > https://mega.nz/#!r8EWGQDD!nYOAC4HuQbYPx1SVl5J7pQnch_h8clEKaCP4uHuAXVg
4. supersu > https://mega.nz/#!C89nzC4L!F6yFyCqexTmi_EWQv9mTB-C1Mz_aKIS4-sBdULURJ7g
1. go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
2. chose type "M" and finish this until get key
3. save key code in file "txt" and rename it "ulcode.txt"
4. install flashtool -0.9.18.4-windows
5. activation USB debug in mobile first
6. connect mobile to PC via USB (DON'T UNPLUG te USB before DONE)
7. run flashtool wait until finish, chose option on top "devices>check drivers"
copy the devices code , my code is "YT911335HE"
INSTALLING TWRP
1. go to C:/flashtool/custom/mydevices/(here), create a new folder and rename with your device code
2. copy ulcode.txt and paste in your device code folder
3. close flashtool
4. create a new folder in C:/(here) rename it "adb" then extract file "adb tool fastboot xperia m4 aqua.zip" and copy file "recovery.img" in C:/adb/(here)
5. run flashtool and chose flash icon, click "fastbood mode" > OK , click "mode>reboot into flashtool mode (via ADB)".wait until finish
6. chose BLU icon wait until finish, unplug the mobile usb from PC and plug with hold Vol- , now chose unlock
7. go to folder "adb", typed cmd at addres bar (to open CMD)
8. paste this code "fastboot flash recovery recovery.img" in CMD, and ENTER, wait until finish
(unplug mobile and plug again with hold vol+ button if ADB tell waiting device)
This if finish intalling TWRP
DONE, TWRP installed but not ROOTED
ROOT
1. run TWRP by press " power and Vol- ", after you see logo sony, release "power" and press " vol- " twice, wait until finish
2. in TWRP mode connect it via USB to PC and send file "UPDATE-SuperSU-v2.46.zip"
3. install "UPDATE-SuperSU-v2.46.zip" by TWRP, wait until finish
DONE, TWRP installed and ROOTed
enjoy it
original source
http://forum.xda-developers.com/m4-aqua/general/guide-t3130092
http://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-sony-m4-t3229873
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
*UPDATE*
This tutorial works just needed some help with the Bootlocker.
Primal09 said:
trying this now. Will update with outcome.
Click to expand...
Click to collapse
good luck
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
same error here. any solution?
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
i think your internal not enough
check the update , i am sory to lte give manual step image :good:
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
CoreyHUN said:
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
Click to expand...
Click to collapse
ah ya,you right ?
CoreyHUN said:
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
Click to expand...
Click to collapse
It says that it is unlocked though.
Primal09 said:
It says that it is unlocked though.
Click to expand...
Click to collapse
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
agree with you ?
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
in me it's work, follow the step carefully
Primal09 said:
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
Click to expand...
Click to collapse
this tutorial i made becouse i never done to root, i try the other tutorial and error
.
so i try with my own metode (this tutorial) and yoi xan see the TWRP in my mobile phone. it's work
Primal09 said:
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
Click to expand...
Click to collapse
ok, u've checked ur BL status before the procedure, but its more important whats the status after the unlock procedure - did u recheck it afterwards? Does it now show that it is unlocked?
silencar said:
ok, u've checked ur BL status before the procedure, but its more important whats the status after the unlock procedure - did u recheck it afterwards? Does it now show that it is unlocked?
Click to expand...
Click to collapse
This is what I get when I check the status.
It did not have Rooting Status the last time if I remember correctly.
Primal09 said:
This is what I get when I check the status.
Click to expand...
Click to collapse
"unavailable" doesn't sound that good
and I have to correct myself - there are 4 kinds of Status:
...
4. UNAVAILABLE
sth went wrong with the unlocking .. for now u have to get the BL status to 'unlocked' (I dont know how)
when this is done, the rooting procedure has to be redone and should work then.
--- Update: ---
what I have found, somebody with the same problem in this thread http://forum.xda-developers.com/m4-aqua/general/guide-t3130092/post63328460
xperia m4 aqua said:
Hi XDA...
Another note, remember to remove the 0x on the bootloader code when creating ulcode file, I proceeded with it in place and it gave me "Rooting Status: Unavailable"
It has been pointed out on this thread how to recover, but if someone runs into this problem: you have plug in the phone again in flash mode (vol down then plug in), click BLU, when relock wizard appears, go back to ulcode file and edit the 0x out, then relock, then unlock again (hope this helps someone new to xperia world like me )
Click to expand...
Click to collapse
It may help u .. or u will find the solution in the mentioned thread
so there is still hope for u
thanks a lot for this tutorial ! work great for me..
what for xposed ? the phone is able to receive it ?
amaeli said:
thanks a lot for this tutorial ! work great for me..
what for xposed ? the phone is able to receive it ?
Click to expand...
Click to collapse
can you send screen shoot? . just make sure if this metode work great ?
ianthok said:
can you send screen shoot? . just make sure if this metode work great
Click to expand...
Click to collapse
I'm not allowed to post screenshot on thread, sended to you at Private message
amaeli said:
I'm not allowed to post screenshot on thread, sended to you at Private message
Click to expand...
Click to collapse
well done ?
Related
This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
One more for future use
XsMagical said:
One more for future use
Click to expand...
Click to collapse
Appreciate your contrbution
Do this only if you want to change the partition 19 cid. We do not know why HTC has a cid there and we do not know why getprop ro cid shows it.
Right now there is no reason for it.
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Worked perfect! Thank you sir. So I can go over to the Sprint forums and grab ViperRom per se and flash it to my AT&T version no problem?
Sent from my HTC One using xda app-developers app
Do we reckon this will work on HTC sensation xe??
Sent from my HTC Sensation Z715e using xda app-developers app
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
hyelton said:
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Click to expand...
Click to collapse
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
clsA said:
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
Click to expand...
Click to collapse
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
this is what I used - I'm at&t
http://forum.xda-developers.com/showthread.php?t=2314582
I have already returned my CID to AT&T stock as I have no intentions of flashing a RUU anytime soon ..just waiting on ARHD 10.2 now
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
barondebxl said:
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
Click to expand...
Click to collapse
Thats what I have been trying for the past HOUR!!!!
It fails everytime!
C:\sdk>adb push revone /data/local/tm
3413 KB/s (646704 bytes in 0.185s)
C:\sdk>cd /data/local/tmp
The system cannot find the path speci
C:\sdk>adb shell
[email protected]:/ # su
su
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod
chmod 755 revone
[email protected]:/data/local/tmp # ./revo
./revone -P
Failed (please reboot and try again!)
revone failed (error code = -6
250|[email protected]:/data/local/tmp #
hyelton said:
Thats what I have been trying for the past HOUR!!!!
I cant get past step 1... I can do ADB shell, Then ADB devices to make sure the device is there and it SHOWS UP, Then I do adb push revone /data/local/tmp/ and BAM no devices found...
SO now what??
Click to expand...
Click to collapse
Here is a video tutorial. Its not the best video around as the guy was trying to do it for the first time as well but it will help you. Make sure you make the youtube video 720p or 1080p full screen otherwise you wont see sh*t. Do the same hing as he does and pause the video when you need to. If you have more question you can pm me.
http://www.youtube.com/watch?v=YYb_Cz5rPIU
hyelton said:
Thats what I have been trying for the past HOUR!!!!
Click to expand...
Click to collapse
are you on a stock kernel ? you can also do it from the device itself
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
error -6 means your not on stock kernel ?
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
Keep trying, the tutorial says if it doesn't go through reboot and keep trying. Worked for the 1st attempt for me but others had to try several times.
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Are you SuperCID ?
did you use this script or the fastboot commands ?
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Congrats! Now get Super CID.
WARNING : I have no time to translate to English so i use google to translate please translate it if you can !
Hello,
Today I would like to introduce to you a set of tools dedicated to Sony Xperia SP. Many of these features are essential to optimize your loved cricket, and hopefully this time I will be back with sony many contributions to her son: D
1. Version:
+ V1.0: The trial version first.
2. The function:
+ Root
+ Unlock BL
+ Backup TA (very important before Unlock BL)
+ Install CWM
3. Instructions to use:
- Download and install PC Companion: http://www.sonymobile.com/vn/tools/pc-companion/
- Connect your phone to the computer.
- Open PC Companion and click on the Start button to load the driver as the adb for the SP!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Disconnect the phone cable from the computer.
- Download and install FlashTool:
http://d-h.st/Kb8
Click to expand...
Click to collapse
- Download and extract tool Xperia SP Tool Kit:
http://www.mediafire.com/?h3cixdcihd2hy37
Click to expand...
Click to collapse
- Run the file disable_driver_signing.bat to disable security when installing drivers on Windows 8, Windows 7 does not need offline. Your PC will restart.
- Go to the directory you installed earlier FlashTool (usually C: \ FlashTool \ drivers) run Flashtool-drivers.exe and select flashmode and Drivers Fastboot Drivers to install!
- Run FlashTool up and thunder click> choose to flashmode and click OK> Click the button ... select the path to the folder Xperia_Tool_Kit> Firmware you will see the same two lines appear, choose which is Version is 12.0.A.1.257 and press Flash button.
- Turn the phone off, hold volume - and plug the cable into the computer. FlashTool to flash the kernel to the machine!
- Run as Administrator XperiaSP_ToolKit.exe up, by right clicking on the tool select Run as Administrator (if using Windows 7/8)
Enable USB debugging on your device in Developer options!
On Unknow sources of Security on the phone!
Click to expand...
Click to collapse
- Tool will automatically identify your computer and is up 5 choices.
- Select the number 1 is the Root to Root machine. If rooting fail please run it again !
- After rooting complete continue flash use flashtool as above but choose the kernel is Version is 12.0.A.2.245.
- Turn on your phone.
Next is the most important part is the Backup TA. Before you unlock your phone, you are advised to take back up later TA warranty or goes back to relock without losing DRM keys
Click to expand...
Click to collapse
- Select option 2 to backup or restore the TA. When backup or restore your noticed the phone screen will light up your screen and click unlock agree when asked root.
- Choose the third option to Unlock Bootloader. You will be prompted for the unlock sequence was taken from Sony. The phone will automatically into fastboot and do things: D
- Select option 4 to install CWM (install new bootloader unlock type). The phone will automatically into fastboot and do things: D
*PS: Guide to root plant is due to its complex root guide for computers running the latest firmware 12.0.A.2.245. The older firmware, you can skip two steps before and after flash kernel root!
** Tool have used a combination of tools such as Root and Backup TA DoomLord of DevShaft
================================================== =====
Link download the latest firmware Stock Xperia SP:
https://docs.google.com/uc?id=0BwIPr1kDYTctakx1RmNxVDBVd3M&export=download
Click to expand...
Click to collapse
Over 120 views but no one comment ?
Hi, thanks you for this tool kit.
It works fine for the moment for me, I try a backup TA and it works
I'll try the others options later. Good job :good:
Anyone can help me translate all #1 in english please ? i use google so may be not correct in here !
The English is fine.
Sent from my C5303 using xda app-developers app
haha good job ^^ do you try it ?
link is dead for flash tool
Done link fixed !
I successfully completed most steps until:
"Choose the third option to Unlock Bootloader. You will be prompted for the unlock sequence was taken from Sony. The phone will automatically into fastboot and do things"
On Toolkit I get:
Please enter an unlock code: (I press enter)
Rebooting to fastboot
Unlocking... (phone reboots)
< waiting for device >
and nothing... My laptop detects the phone as normal, but Toolkit does nothing, just says < waiting for device >
Also, even though it said rooting was successful, the root checker apps say my phone is not rooted...
Ypnos said:
I successfully completed most steps until:
"Choose the third option to Unlock Bootloader. You will be prompted for the unlock sequence was taken from Sony. The phone will automatically into fastboot and do things"
On Toolkit I get:
Please enter an unlock code: (I press enter)
Rebooting to fastboot
Unlocking... (phone reboots)
< waiting for device >
and nothing... My laptop detects the phone as normal, but Toolkit does nothing, just says < waiting for device >
Click to expand...
Click to collapse
What's is your unlock code ? you have to enter your unlock code here to unlock your phone ! Not enter without any code !
If you root fail after flash kernel 1.257 please root it again it's work
quangnhut123 said:
What's is your unlock code ? you have to enter your unlock code here to unlock your phone ! Not enter without any code !
If you root fail after flash kernel 1.257 please root it again it's work
Click to expand...
Click to collapse
I don't have an unlock code...
Just go to sony website to got an unlock code !
Does unlocking bootloader erase the internal memory?
Sent from my C5303 using xda app-developers app
Yes it's does so you have to backup internal storage first !
quangnhut123 said:
Just go to sony website to got an unlock code !
Click to expand...
Click to collapse
A google search doesn't give any hits for unlock codes on the official sony website...
Ypnos said:
A google search doesn't give any hits for unlock codes on the official sony website...
Click to expand...
Click to collapse
http://unlockbootloader.sonymobile.com/instructions
how to backup TA on 2.254 kernel
Hi, Thanks you again for this tool.
I successfully backup TA and unlock my bootloader easily with your tool
Good Job :good:
thanks for this handy tool. it helped alot in installing CWM for unlocked bootloaders.
edit: cwm has some problems mounting sd card when doing a backup to external sd card. anyone facing this issue ?
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
EDIT - I sort of solved it myself in post #7
sminki said:
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
Click to expand...
Click to collapse
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
piskr said:
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
Click to expand...
Click to collapse
Not on these. That the first thing I tried. That gives
Code:
FAILED (remote: Command not allowed)
Which is essentially "command not found", as you can pass it any garbage and that's what it gives back.
As I see it, you can't install updates with an unlocked bootloader (unless I'm wrong, or there is something desperately wrong with my phone). With no custom roms (at the moment) this is all we have
EDIT:
Looks like I was wrong about updates on unlocked bootloader. I went back to B100 (UK) then back up to B121
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
t-ph said:
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
Click to expand...
Click to collapse
I haven't retried yet. I was still in my 14 day return period and was undecided if I was going to keep the phone
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried it on B100?
Have you tried it on B140?
Have you tried "oem lock" instead of "oem relock"?
Note: Always mention your model number in your thread title and description. Not all different models behave the same and not all updates give the same error message.
Thank you for opening this thread. We hope to read your answers on the above questions to help you.
kenshiwara said:
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried "oem lock" instead of "oem relock"?
Click to expand...
Click to collapse
I have the EU Version PLK-L01 16GB
..and yes I had, see my second post - lock doesn't seem to be a valid Huawei boot-loader command.
I've had a busy and incredibly boring time trying to sort this out.. Somehow, I re-locked :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately from the point of view of returning the device to Huawei, Re-locked is not the same as Locked, but it's all I have found.
After TWRP format:
Code:
sudo fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: images signature check fail)[/COLOR][/B]
finished. total time: 1.048s
After B100 Downgrade:
Code:
fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: root type is risk)[/COLOR][/B]
finished. total time: 0.970s
I re-flashed the UserData image from B100, after booting up I got this:
After UserDate Wipe:
Code:
fastboot oem relock 1111111111111111
...
OKAY [ 1.985s]
finished. total time: 1.985s
fastboot oem get-bootinfo
...
(bootloader) [COLOR="Green"]relocked[/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
So basically, I re-locked with a completely fresh, untouched system and a "factory" wiped data partition.
Obviously I have unlocked again and gone back to B140. If someone else want to experiment, feel free to post your results. I'm done with this :silly:
Re-lock your bootloader successfully
Re-lock your Honor 7(PLK-L01)'s bootloader successfully
No matter on which version you are and on which recovery, follow the steps:
1. Extract the B100 "UPDATE.APP" using this tool. Credit goes to its maker. If you wanna make flashable zip from "UPDATE.APP" then use the attached "Profiles.xml" file for HuaweiUpdate Extractor, me and @kenshiwara has added Honor 7 in the list.
2. Now flash "boot.img", "recovery.img", "cache.img", "cust.img", "system.img", "userdata.img" from the extracted B100 "UPDATE.APP" by executing following commands in "Command Prompt"
Make sure you are in the same folder where all these files are then "Right click" inside the folder by holding down "Shift", then select "Open command window here".
For "boot.img"
Code:
fastboot flash boot boot.img
For "recovery.img"
Code:
fastboot flash recovery recovery.img
For "system.img"
Code:
fastboot flash system system.img
For "cache.img"
Code:
fastboot flash cache cache.img
For "cust.img"
Code:
fastboot flash cust cust.img
For "userdata.img"
Code:
fastboot flash userdata userdata.img
Now reboot your device by executing this command
Code:
fastboot reboot
3. Setup your device, then place B100's "UPDATE.APP" in your external SDCARD in "/dload" folder.
4. Now, switch off your device and press the three button combo to flash the B100 "UPDATE.APP", the three button combo is "Vol. Up", "Vol. Down" and "Power Button" press these three simultaneously to flash the B100 "UPDATE.APP".
5. After your device reboots and after you are done setting it up, go to "Settings > Backup & Reset", then select "Factory data reset", tick "Internal Storage" and press "Reset Phone".
6. Again after rebooting, switch off your device then by pressing "Vol. Down" button connect your device with PC.
7. Now, you'll be in "Fastboot&RescueMode" and your device status will be "Phone Unlocked".
8. Execute the following command to relock your device.
Code:
fastboot oem relock *16 digit unlock code*
9. Now, you'll see that your device status is changed to "Phone relocked".
So, you just relocked your Honor 7.
So basically what I said then
sminki said:
So basically what I said then
Click to expand...
Click to collapse
I think you just flashed "userdata.img" of B100 which is not good as it broke your "/userdata" partition, but yea basically that
DigiGoon said:
8. Execute the following command to relock your device.
Code:
fastboot relock *16 digit unlock code*
Click to expand...
Click to collapse
are you sure? i thaught it was
Code:
fastboot [B]oem[/B] relock *16 digit unlock code*
non-toxic said:
are you sure? i thaught it was
Code:
fastboot relock [B]oem[/B] *16 digit unlock code*
Click to expand...
Click to collapse
Thank you for pointing that out.
speaking as the man who has, you're both incorrect
Code:
fastboot oem relock *16 digit unlock code*
sminki said:
speaking as the man who has, you're both incorrect [emoji14]
Code:
fastboot oem relock *16 digit unlock code*
Click to expand...
Click to collapse
You should've checked my answer before stating that I'm incorrect too. And yeah check its last edit too, its not edited after your reply.
Sent from my PLK-L01 using Tapatalk
i'm not well
my humble apologies @DigiGoon
I have try "fastboot oem relock *my code*" and it works. But i had changed nothing on my phone. it was just unlocked.
no root; no TWRP; no other updates
maybe this was the reason why.
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Hello,
i can`t relocked my phone.
FAILED (remote: root type is risk).
My Honor 7 has the Firmware B330.
I think i tried everything but i always have the same error.
What can is the newest solution?
what's the point of relocking the bootloader?
hachuwaka said:
what's the point of relocking the bootloader?
Click to expand...
Click to collapse
I want to know too. Is there any risk to keep unlocked the bootloader on non rooted device?? Except guarantee
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Sandnes74 said:
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Click to expand...
Click to collapse
You will receive updates but do not install them!!!! If you don't listen to me your device will be caught in bootloop
Sent from my PLK-L01 using XDA-Developers mobile app
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Nice find!
No DRM crap or anything that would cause some features to be lost (stopped working) after unlocking bootloader?
I'm Sony user btw and had already lost DRM and some of its features, including camera that didn't work on older ROM version XD
Thanks, I just ordered the phone because of this post.... Though I should probably have waited for the U20
Still, ive been jonesing for an HTC fix . I need this.
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Doesn't work for me... (Solution)
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Know it's working!
Don't use fastmode/Fastmoded Mode, it has to be done with CMD and bootloader startet!
Hello, friends on the fifth floor
Before using FastBoot flash unlock, you need to open OEM lock in developer mode now. You can try my way and give me a reply on how to unlock normally. I am looking forward to your reply
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
wpride77 said:
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
i have one and im thinking of unlocking it
C:\Users\mypc>fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
Getting this error on my Itel A48 (L6006) running on android Q.......fastboot and adb drivers are installed and fastboot recognize my device
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader can now be easily unlocked.Older get_identifier_token command is no more needed.
Instructions
Download HTC_Driver_v4.17.0.001 and install the package.
Download Google USB Driver. ( For installation information, read Install a USB Driver) .
To install the Android USB driver on Windows 10/11 for the first time, do the following:
Connect your Android device to your computer's USB port.
From Windows Explorer ( Search ), open Computer Management.
In the Computer Management left pane, select Device Manager.
In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
Right-click the name of the device you connected, and then select Update Driver Software.
In the Hardware Update wizard, select Browse my computer for driver software and click Next.
Click Browse and then locate the Google USB driver folder.
Click to expand...
Click to collapse
Connect your device to your computer and Backup device
( Get a complete backup of your contacts, messages, apps, and internal storage. Now usually, Enabling OEM unlock won’t erase the data on the device. But obviously, the eventual step after OEM unlock is bootloader unlocking, and that will wipe away everything on your device )
Download ADB. ( How to Install ADB on Windows, macOS, and Linux )
Enable OEM Unlocking
Open the settings on your phone.
Find the section that says “Developer options” and tap on it.
Scroll down till you find the option “OEM unlock”
Tap on it to turn the toggle on, and you are done.
Then simply run below command.
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
elimiriel said:
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
Click to expand...
Click to collapse
Yes you have problems with fastboot on your PC.
Btw OEM unlock wiped my data just to heads up.
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Thanks mate!
I can confirm same strategy for the new Desire 21 pro 5G.
ToM
how unlock bootloader spd 9863a Android ver.11 realme c11
Hello, I need HELP! When I get to the "Google USB Driver" section I cannot proceed any further. When I open the update hardware wizard, I choose the folder that the Google drivers are in, and sadly, the drivers do not get installed to the device. The error reads "The best drivers for your device are already installed", preventing it from getting installed. I am using a Samsung Galaxy S21 that has an IMEI of a bunch of zeros (0).
Hi,
Yesterday while I was browsing normally, the phone suddenly froze and I couldn't do anything, not even turn off the screen. Then after like 3 mins the screen went blank. (it was turned on, but blank)
Some background,
this problem with the screen happened a few times before, at first it would happen randomly when trying to turn on the screen, it would turn on, be blank, flash a few times and turn off again, but a reboot would fix it. This happened like once a month.
Then it stopped happening when trying to turn on the screen, instead it started happening everytime I try to reboot. The Huawei logo and animation would show, but instead of showing the lockscreen it would again be blank, flash and turn off. It would be back to normal after a few hrs and/or after a reboot or two.
THEN the only thing that changed is that it would be blank even when booting up. The Huawei logo wouldn't show up.
However, the phone worked, sometimes the screen, instead of flashing, would stay turned on then dim down and turn off like it would normally do on the lockscreen. The touchscreen also worked because I managed one time to shut the phone down. I would also hear that startup sound after rebooting. At this point I thought it's a hardware issue, something with the display.
Now back to what happened yesterday, I think I rebooted the phone some time after it went blank, but now I couldn't hear the startup sound anymore, and I still couldn't turn off the screen.
I left it like that until the battery died, then when I plugged the charger the red led turned on, I waited for it to charge a bit, then when I tried to turn it on the red led started flashing. And maybe I'm paranoid but the flashing was a bit off, it wasn't the normal flashing you get when you have a notification for example.
I was tired so I went to sleep and left it like that overnight.
In the morning the screen was still blank, the red led was still flashing, and after I rebooted the screen went back to normal and I finally saw that the phone is stuck on this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(image taken from a yt video)
I tried Power + Volume Up to try to go into recovery, it didn't work. It just reboots and stays stuck on that screen. Actually the only thing that worked was going into fastboot. (with Power + Volume Down)
The bootloader and FRP are both locked.
Some info from fastboot:
Code:
Z:\adb\platform-tools>fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.401(C432E13R1P7)
OKAY [ 0.006s]
Finished. Total time: 0.007s
Z:\adb\platform-tools>fastboot oem get-product-model
(bootloader) ANE-LX1
OKAY [ 0.007s]
Finished. Total time: 0.008s
Z:\adb\platform-tools>fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.006s
Z:\adb\platform-tools>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX1-CUST 9.1.0.13(C432)
OKAY [ 0.006s]
Finished. Total time: 0.007s
I was thinking maybe I can unlock the bootloader using the hardware testpoint method, with PotatoNV, then install TWRP and try to backup the data at least. (I never used TWRP, I just saw there's a Backup button, idk how/if it works)
But since it can't go into recovery, I wonder if I would be stuck on some screen again.
What should I do?
jdxgfty said:
I was thinking maybe I can unlock the bootloader using the hardware testpoint method, with PotatoNV, then install TWRP and try to backup the data at least. (I never used TWRP, I just saw there's a Backup button, idk how/if it works)
Click to expand...
Click to collapse
Yes, it's possible, using build-in File manager (Advanced > File manager > sdcard ) .
jdxgfty said:
But since it can't go into recovery, I wonder if I would be stuck on some screen again.
Click to expand...
Click to collapse
Good question...
Have you made any software modifications? (build.prop editing etc.)
Edit.:I mean, wrongly editing build.prop or systemUI can also cause similar screen issues.
-Alf- said:
Have you made any software modifications?
Click to expand...
Click to collapse
No, I don't think so.
I forgot to mention, I tried this command at one point: fastboot getvar rescue_enter_recovery
And it gave me this error: FAILED (remote: 'FAIL:need all image flashed!')
Does this help with anything?
Edit: Also when I held the Power + Volume Up buttons, the logo would take slightly longer to appear. Not a big difference, but it seemed like it was longer compared to just holding the power button.
jdxgfty said:
fastboot getvar rescue_enter_recovery
And it gave me this error: FAILED (remote: 'FAIL:need all image flashed!')
Click to expand...
Click to collapse
It is normal, it's not related to your problem.
If you want to try to save data from the phone, in your case you have only one chance - the mentioned method with TWRP.
Any method of restoring the software in your case means the loss of your data.
Personally, I would try replacing the battery first. If nothing else, you will have your phone ready for the test point .
-Alf- said:
I would try replacing the battery first
Click to expand...
Click to collapse
Why's that?
I have some questions about the testpoint method..
How do I glue the back cover after taking it off?
And on PotatoNV's readme it says I need some conductive tweezers, but I don't think I have any. Can I use something else?
Edit: To be more clear. Do you think the battery might've caused the issue? Recently I started seeing this type of notification, which I didn't see before:
Edit2: Ok, I'm sorry but I keep having questions..
I saw that fastboot has an option to boot from an image file, do I have more chances with this if flashing doesn't work?
And what if do the other way around, try the TWRP method first then replace the battery if that doesn't work?
jdxgfty said:
And what if do the other way around, try the TWRP method first then replace the battery if that doesn't work?
Click to expand...
Click to collapse
Well, I don't know, but logic tells me that if there is a problem with the battery, it is not certain that the TWRP method will work. Or other processes.
The battery thing is just a theory, you can ignore it. I'm not a specialist, I'm just a hobbyist.
jdxgfty said:
I saw that fastboot has an option to boot from an image file,
Click to expand...
Click to collapse
What exactly do you mean by that?
-Alf- said:
What exactly do you mean by that?
Click to expand...
Click to collapse
I saw this command somewhere: fastboot boot recovery twrp.img (or without the recovery)
jdxgfty said:
I saw this command somewhere: fastboot boot recovery twrp.img (or without the recovery)
Click to expand...
Click to collapse
that command doesn't work on Kirin devices.
Your priority is to save data, right? The methods of reviving the phone will come later.
For example this one
(of course, assuming TWRP is successfully installed and if there really is a software problem).
Hi @-Alf-
I unlocked the bootloader, but FRP is still locked. FB lock is disabled.
Code:
Z:\adb\platform-tools>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.000s]
Finished. Total time: 0.001s
Z:\adb\platform-tools>fastboot oem lock-state info
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.002s]
Finished. Total time: 0.003s
Flashing TWRP fails:
Code:
Z:\adb\platform-tools>fastboot flash recovery_ramdisk Z:\TWRP-9.1.img
Warning: skip copying recovery_ramdisk image avb footer (recovery_ramdisk partition size: 0, recovery_ramdisk image size: 31006720).
Sending 'recovery_ramdisk' (30280 KB) OKAY [ 0.812s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Is it because of the FRP lock? What should I do from here?
On this video, the pinned comment says:
if you want to unlock the bootloader without wiping data, just check the "DISABLE FBLOCK (not recommended)" option, then no command needs to be used "fastboot oem unlock".
Click to expand...
Click to collapse
I don't understand if I'm supposed to not use any command (I didn't) or if I'm supposed to use fastboot oem unlock without the unlock code.
Also wanna note that now the "You device has been unlocked and can't be trusted" screen shows up and it's stuck on "Your device is booting now..."
jdxgfty said:
Is it because of the FRP lock?
Click to expand...
Click to collapse
In fastboot mode PHONE Unlocked and FRP Unlock?
(both red?)
-Alf- said:
In fastboot mode PHONE Unlocked and FRP Unlock?
(both red?)
Click to expand...
Click to collapse
No, FRP is locked, in green. Phone is unlocked, in red.
That's why I asked about the commands, I didn't wanna use any and mess up something.
jdxgfty said:
No, FRP is locked, in green. Phone is unlocked, in red.
That's why I asked about the commands, I didn't wanna use any and mess up something.
Click to expand...
Click to collapse
As far as I know, there are two types of bootloader blocking:
User lock:
This lock is managed using the "fastboot oem unlock <bootloader code>" command.
With such an unlock, it becomes possible to flash part of the partitions from fastboot. But not all. And of course, this procedure automatically triggers a factory reset on A7 and above.
FB Lock:
This lock is controlled using the "fastboot oem hwdog certify set <0 or 1>" command . For this command to work, FB Lock must already be disabled. In fastboot, which is launched through a testpoint!
With this unlock, it becomes possible to flash almost all partitions from fastboot, without wiping data.
When FB Lock is unlocked, the User Lock state is ignored. The phone behaves like it is completely unlocked.
As for this problem:
Warning: skip copying recovery_ramdisk image avb footer (recovery_ramdisk partition size: 0
- I saw the same one on another forum with the Honor 9lite, there was the cause locked BL, I don't know how it turned out in the end...
I personally have no experience with potatonv. And I don't want to give you any advice that would cause data loss.
jdxgfty said:
Is it because of the FRP lock?
Click to expand...
Click to collapse
If that were the cause, you would get the "command not allowed" error, imo.