[SOLVED-ish] Bootloader Relock FAILED - Honor 7 Q&A, Help & Troubleshooting

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

Related

[MOD][S-OFF] SuperCID Your Amaze!

Hello!
So since I had a sensation before the Amaze, I remembered that once we got S-Off, a next step was to obtain SuperCID on the phone. Basically, having SuperCID allows you to flash any ROM, regardless of which carrier it is for. Pretty handy if you have your phone SIM unlocked and wanted to use your Amaze on Wind Mobile or something. Anyway, the steps are from this thread (http://forum.xda-developers.com/showthread.php?t=1192300) and original credit goes to "xl VipeR lx" for the Sensation write up.
The usual warning goes here. I'm not responsible for what you do, use this at your own risk!
Required - You MUST have your phone S-Off from Juopunutbear's method first! Go here for that: http://forum.xda-developers.com/showthread.php?t=1611977
Also, if you've upgraded to ICS, the 1.93.0002 SHP Hboot is required to SuperCID!
--------------------------------------
ATTENTION:
It appears that the ICS update changes the firmware of the phone a bit. This means that using any bootloader other than SHP 1.93.0002 will remove your ability to write SuperCID to your device. This includes the ENG bootloader. It makes no different if you're locked/unlocked and S-OFF, the command doesn't work without being on the proper HBoot. Unfortunately, being on 1.93.0002 also removes your ability to flash partitions directly in Fastboot (ie. fastboot flash recovery, fastboot flash radio, etc) and you must revert to ENG 1.90.2005 in order to use fastboot flash commands.
--------------------------------------
The process is very simple and exactly the same as the Sensation and most S-Off HTC devices:
1. Command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
2. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings)
3. Enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. Enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
IF it doesn't you can Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
5. Enter the command "fastboot oem writecid 11111111"
6. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. Enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. Enter the command "fastboot reboot"
9. You can now flash any ROM you like.
{
"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"
}
To remove SuperCID and return to stock CID:
1. Follow steps 1-4 for SuperCID
2. Enter the command "fastboot oem writecid __________" <--- Here you will put either T-MOB010 (T-Mobile), TELUS001 (Telus), GLOBA001 (Wind Mobile Canada)
3. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
4. Enter the command "fastboot getvar cid" [it should confirm your CID has changed]
5. Enter the command "fastboot reboot"
6. You are now back on stock CID (for your carrier)
****If you like the automated route, benjamminzIs has provided two batch files, one for SuperCID (for all devices) and one for reverting to stock (T-Mobile only). Place them in your SDK/tools folder and run them!****
I'll write two .bat scripts for you soon
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
I'll write two .bat scripts for you soon
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
hhilton said:
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
Click to expand...
Click to collapse
Thanks, updated. If anyone has a Wind device and knows what the CID is, I'll add it for reference.
benjamminzIS said:
done...
here: DOWNLOAD
place these in SDK/tools folder and run them...
Click to expand...
Click to collapse
Thanks, attached to main post with credit
Here are my scripts. No need to put it in the SDK folder. Just extract and run it!
electronicrice said:
Thanks, attached to main post with credit
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
Basically the same. You just push the .CID rather than writing them.
hasoon2000 said:
Basically the same. You just push the .CID rather than writing them.
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
electronicrice said:
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
Click to expand...
Click to collapse
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
benjamminzIS said:
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
Click to expand...
Click to collapse
no not at all. everything's great here. we have s-off. mood couldn't be better. =]
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Thanks, for reference
Code:
cid: TELUS001
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Worked like a charm Thanks
Opentang said:
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Click to expand...
Click to collapse
Yeah it's in the OP but basically it allows you to flash to any carrier's official ROM for the Amaze. So if you have a T-Mobile Amaze and you wanted to flash the RUU for Telus or Wind, you can with SuperCID.
In the past, the RUU has to be hacked to allow a flash on a non-carrier specific device, and this allows you to bypass that entirely.
MentalDeath said:
Thanks, for reference
Code:
cid: TELUS001
Click to expand...
Click to collapse
idaggerpwn said:
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Click to expand...
Click to collapse
Great, thanks guys, updated the OP
updated the DnD_SuperCID here: DOWNLOAD. (PLEASE DON'T QUOTE THIS POST!!!)

[TUT] BLU, TWRP , ROOT Xperia M4 Aqua [complete step]

[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 ?

[GUIDE] How to unlock bootloader

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).

YT-X705F - Rooting Guide (Android 10.0)

Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"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"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?

P20 Lite bricked, no eRecovery

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.

Categories

Resources