I have a XT1941-4 that is stuck in the Bootloader. Whenever I press 'START' it says that the device can't be verified and will boot in 5 seconds, but it never actually boots. Is there anything I can do as a noob to get this phone to work again?
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
applesucksLmao said:
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
Click to expand...
Click to collapse
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
ogruendel said:
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
Click to expand...
Click to collapse
Failed after 6 minutes at ~70%
send pictures of the "fail" and the phone 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"
}
applesucksLmao said:
send pictures of the "fail" and the phone screen
Click to expand...
Click to collapse
Just added them to the thread
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
applesucksLmao said:
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
Click to expand...
Click to collapse
Deleted the first image. I don't know how to manually flash an image or where to get this image to begin with. I am also not using the cable that came with the phone. I will try to find it and see if that works
Edit: Come to think of it I believe this cable broke a while ago
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
applesucksLmao said:
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
Click to expand...
Click to collapse
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
ogruendel said:
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
Click to expand...
Click to collapse
how did you try to unroot it?
applesucksLmao said:
how did you try to unroot it?
Click to expand...
Click to collapse
That was a year ago. I can't remember a lot.
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
I am able to boot into TWRP. When I'm in TWRP only adb works, when I'm not in TWRP only fastboot works
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
so you tried to unroot it a year ago and it just happened or its dead for 1 year?
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Hucin44 said:
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Click to expand...
Click to collapse
When running fastboot erase userdata I get (bootloader) Permission denied
ogruendel said:
When running fastboot erase userdata I get (bootloader) Permission denied
Click to expand...
Click to collapse
go to twrp and format data from the wipe section
applesucksLmao said:
go to twrp and format data from the wipe section
Click to expand...
Click to collapse
i mean the slider
applesucksLmao said:
i mean the slider
Click to expand...
Click to collapse
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Related
Hey guys,
I have an HTC One running Android Revolution HD and while upgrading to version 30 I chose full wipe. AROMA installer ran and everything went fine with the installation... Or so it seemed.
After AROMA was done, I was in CWM and rebooted the device and it went into a bootloop. It automatically tried going into recovery (CWM) but that didn't work.
I finally got into HBoot and tried using fastboot from my windows 8 PC but for some reason Command Prompt couldn't detect my phone using fastboot or ADB! So now I have a bootlooped HTC One which isn't being detected while running fastboot and cannot open recovery either.
Anyone know what to do?
ShanayAbbas said:
Hey guys,
I have an HTC One running Android Revolution HD and while upgrading to version 30 I chose full wipe. AROMA installer ran and everything went fine with the installation... Or so it seemed.
After AROMA was done, I was in CWM and rebooted the device and it went into a bootloop. It automatically tried going into recovery (CWM) but that didn't work.
I finally got into HBoot and tried using fastboot from my windows 8 PC but for some reason Command Prompt couldn't detect my phone using fastboot or ADB! So now I have a bootlooped HTC One which isn't being detected while running fastboot and cannot open recovery either.
Anyone know what to do?
Click to expand...
Click to collapse
I don't know how to delete this thread but I've resolved the problem. I finally managed to access fastboot (windows 8 seems to have a problem with fastboot) and flashed TWRP... Then I flashed my old ROM and everything's okay.
I'm having a similar issue! Except I was able to get into fastboot and flash a new recovery but it's still looping.
Fixed it, had to clear the cache using "fastboot clear cache" but now I'm having trouble accessing the sd card in recovery. It says "Can't mount/ sdcard"
Same problem here
BerryCrunch said:
I'm having a similar issue! Except I was able to get into fastboot and flash a new recovery but it's still looping.
Fixed it, had to clear the cache using "fastboot clear cache" but now I'm having trouble accessing the sd card in recovery. It says "Can't mount/ sdcard"
Click to expand...
Click to collapse
Have you resolved this issue? I'm having the same problem with my phone.
BerryCrunch said:
I'm having a similar issue! Except I was able to get into fastboot and flash a new recovery but it's still looping.
Fixed it, had to clear the cache using "fastboot clear cache" but now I'm having trouble accessing the sd card in recovery. It says "Can't mount/ sdcard"
Click to expand...
Click to collapse
How do you "Fastboot Clear Cache"?
racosta201045 said:
How do you "Fastboot Clear Cache"?
Click to expand...
Click to collapse
the correct command is
fastboot erase cache
it's always done after flashing recovery
Hi guys,
Need ur help..i have got my device relocked from revo hd rom..now i cannot go into recovery and stuck in bootloader
Pls help
This is what i get and im.not sure how to.move forward coz this phone was just given to me and i need to flash to stock to claim warranty for the purple tint issue
{
"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"
}
cynd_05 said:
Hi guys,
Need ur help..i have got my device relocked from revo hd rom..now i cannot go into recovery and stuck in bootloader
Pls help
This is what i get and im.not sure how to.move forward coz this phone was just given to me and i need to flash to stock to claim warranty for the purple tint issue
Click to expand...
Click to collapse
whats with the OS version ? 2.x.707.x
is it an AT&T phone ?
clsA said:
whats with the OS version ? 2.x.707.x
is it an AT&T phone ?
Click to expand...
Click to collapse
Nope it's an asia unit, from singtel. I need help on how I can boot up normally so I can get the purple tint issue repaired under warranty. I might have messed up everything after trying to restore to stock
Hello, I need help.
I have had my nexus 9 bricked for like 6 months or more..
I tried to upgrade to Android 6 developer preview 3..
It doesn't boot.. I see the alert that the device may be corrupt and that things..
I tried to find a OTA but there isn't one for
6.0/MPA44I/2172151 to ->???
After it didn't worked I *as stup*id* did:
fastboot erase system
fastboot oem lock
I think my system partition is corrupt and my bootloader is locked.
I can't do anything, I tried to sideload android N from developer. android. com /intl/es/preview/download-ota.html
BUt nope..
Please help..
I replied to you on the other threads but you have supplied more information here.
"fastboot erase system" probably didn't do anything as your bootloader is locked.
Last thing to try, if you haven't done so already is to try sideloading
volantis MPA44I from MPZ79M
That link gotten from here.
If that doesn't work. You don't have a soft brick but an expensive paperweight!
corkiejp said:
I replied to you on the other threads but you have supplied more information here.
"fastboot erase system" probably didn't do anything as your bootloader is locked.
Last thing to try, if you haven't done so already is to try sideloading
volantis MPA44I from MPZ79M
That link gotten from here.
If that doesn't work. You don't have a soft brick but an expensive paperweight!
Click to expand...
Click to collapse
Hey, I will try.
I did fastboot erase system before lock
At least I can say that I've tried ?
{
"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"
}
ignaciouy said:
Hey, I will try.
I did fastboot erase system before lock
Click to expand...
Click to collapse
I read that as "fastboot oem unlock", did the update process brick your tablet.
Are did you issue the commands 6 months ago and that is why your device is bricked?
corkiejp said:
I read that as "fastboot oem unlock", did the update process brick your tablet.
Are did you issue the commands 6 months ago and that is why your device is bricked?
Click to expand...
Click to collapse
Kinda, I'm 100% sure that it's because I removed the system partition. and then oem lock
r ur bootloader soff and unlocked?
lusamuerstan said:
r ur bootloader soff and unlocked?
Click to expand...
Click to collapse
My bootloader is locked.
I can't boot in Android (probably there's nothing on system partition.) and I wasn't able to install Android N because my recovery is too old
ignaciouy said:
My bootloader is locked.
I can't boot in Android (probably there's nothing on system partition.) and I wasn't able to install Android N because my recovery is too old
Click to expand...
Click to collapse
what recocery u have.
Sent from my Nexus 9 using Tapatalk
How to see that?
I have the Android M developer preview 3
Still think you have an expensive paperweight.
Have you tried the command "fastboot oem unlock" since you locked the device?
Can you boot a newer stock recovery.img or TWRP.img with
"fastboot boot <name of recovery.img>"
On the odd chance that actually boots, try sideloading Android N OTA again.
Even if it boots, your corrupted system.img might prevent the OTA from been applied.
Note: Try the above commands with your device in bootloader mode.
corkiejp said:
Have you tried the command "fastboot oem unlock" since you locked the device?
Can you boot a newer stock recovery.img or TWRP.img with
"fastboot boot <name of recovery.img>"
On the odd chance that actually boots, try sideloading Android N OTA again.
Even if it boots, your corrupted system.img might prevent the OTA from been applied.
Note: Try the above commands with your device in bootloader mode.
Click to expand...
Click to collapse
That doesn't work, I already tried...
If I replace the motherboard the tablet should work, no?
I think its better to buy a motherboard Instead of getting a new one
ignaciouy said:
That doesn't work, I already tried...
If I replace the motherboard the tablet should work, no?
I think its better to buy a motherboard Instead of getting a new one
Click to expand...
Click to collapse
I wouldn't waste money on a new motherboard as you storage is corrupted, so you would still be faced with trying to get a working system on it.
Write it off as a lesson learned!
corkiejp said:
I wouldn't waste money on a new motherboard as you storage is corrupted, so you would still be faced with trying to get a working system on it.
Write it off as a lesson learned!
Click to expand...
Click to collapse
Mhm, isn't the storage on the motherboard?
https://es.ifixit.com/Guide/Nexus+9+Motherboard+Replacement/43015
can you flash latest marshmallow factory image?..or it stuck during flash the img
Sent from my Nexus 9 using Tapatalk
Can you unlock the bootloader again? Chances are "OEM unlocking" option is still toggled and open.
No, I can't unlock my bootloader.
I tried sideloading Android N, and it doesnt work.
Probably because my keys are dev-key? I have no idea.
Rip nexus ((
I tried to rebrand my Honor 9 model STF-AL10 to European model. It successfully flashed new oeminfo but now won't boot because it shows that message.
{
"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"
}
Also if I boot to fastboot and rescue mode I can't flash anything because now it shows that message.
What can be done ? I'm also willing to pay to repair my phone...
I think your phone is bricked now, Only Huawei can help you now buddy. FRP and Bootloader should be unlocked
Rommco05 said:
Before u start rebrand phone was phone and FRP unlocked?
Click to expand...
Click to collapse
Phone was unlocked but Chinese models don't have FRP Lock so I couldn't turn it off. The FRP lock appeared when the Chinese oeminfo was replaced with the European one and suddenly also the bootloader was locked again.
But I have a feeling that I forgot to turn on USB debugging when flashing using that guide on forum...
Anyway maybe DC Phoenix is my last option before sending it to Huawei to reflash OS. Apparently that tool can flash over locked bootloader and FRP.
Does anybody know how it works and if there is a free alternative?
gljiva123 said:
Phone was unlocked but Chinese models don't have FRP Lock so I couldn't turn it off. The FRP lock appeared when the Chinese oeminfo was replaced with the European one and suddenly also the bootloader was locked again.
But I have a feeling that I forgot to turn on USB debugging when flashing using that guide on forum...
Anyway maybe DC Phoenix is my last option before sending it to Huawei to reflash OS. Apparently that tool can flash over locked bootloader and FRP.
Does anybody know how it works and if there is a free alternative?
Click to expand...
Click to collapse
Did you select the correct oeminfo for your firmware? STF-L09C10 is the Russian one and STF-L09C432 is the European one.
Also, did you remember to boot into recovery (volume up + power button) and select the option to clear your data after the rebrand?
You might still be able to boot into recovery and try a reset, but I'm not sure if that will help.
Ring0h said:
Did you select the correct oeminfo for your firmware? STF-L09C10 is the Russian one and STF-L09C432 is the European one.
Also, did you remember to boot into recovery (volume up + power button) and select the option to clear your data after the rebrand?
You might still be able to boot into recovery and try a reset, but I'm not sure if that will help.
Click to expand...
Click to collapse
I selected the C432. And I remembered to wipe out the internal storage and data after the rebrand. I honestly don't know what went wrong (besides not having USB debugging turned on).
I also tried to boot into recovery but only the first message appears. In the end I think there is no recovery at all (or is corrupted)...
But it's funny how those security features meant to protect the phone in the end make it harder to recover.
Try to reflash Boot.IMG , Recovery.IMG via ADB in Fastboot mode and SYSTEm.IMG in TWRP.. (On your own risk)... maybe it will work....
4r44444 said:
Try to reflash Boot.IMG , Recovery.IMG via ADB in Fastboot mode and SYSTEm.IMG in TWRP.. (On your own risk)... maybe it will work....
Click to expand...
Click to collapse
Where do I get those files ?
Rommco05 said:
I have full backup from STF-L09C432B130 but I don't know if is helpful here, later I can upload somewhere
Click to expand...
Click to collapse
That would be nice. I don't have the backup of full stock rom . And I agree with you, probably it won't be possible to flash it with fastboot but with DC Phoenix it might be.
Rommco05 said:
I think we are wrong, this backup is made via TWRP so is flashable only via TWRP... anyway I will postes here. You need extract full firmware B130 and this files flash via fastboot. I have this files but I don't have time today all uploaded here and posted. If want u can do by yourself. Find Huawei Extractor (is here on XDA) and download this zip :
Extract the biggest one and here u will find all staff for recover phone, I can't asist you today
FULL FIRMWARE FRD-L09C423B130
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1637/g104/v90868/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...68/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip
FULL TWRP BACKUP FRD-L09C432B130
https://drive.google.com/open?id=0B1xSFdgEasy-YTZsUTk0c3k2X1U
...I hope is able for download...
I will make maybe something like repozitory for Honor 9 but don't know when...
Click to expand...
Click to collapse
thanks, will give it a try
In the end I restored it using DC Phoenix, but it's not for free.
gljiva123 said:
In the end I restored it using DC Phoenix, but it's not for free.
Click to expand...
Click to collapse
Better than having a dead phone
Rommco05 said:
...and phone is repaired?
Click to expand...
Click to collapse
Yes it is
Hello,
I wanted to root my phone to MIUI version 13.
I have rooted before and I was at MIUI 12.6.
While I was romming my phone it failed (which i didnt see) and followed the guide and wiped everything.
Now I am stuck without an operating system, I have tried flashing but when I was flashing and it came to 1201 seconds then it said "error: flash timeout"
Does anyone know what to do?
imbadsus said:
Hello,
I wanted to root my phone to MIUI version 13.
I have rooted before and I was at MIUI 12.6.
While I was romming my phone it failed (which i didnt see) and followed the guide and wiped everything.
Now I am stuck without an operating system and I can't get any flesh/roms to work.
Does anyone know what I should do?
Click to expand...
Click to collapse
First of all, you should change the title of the thread as it is confusing to the content of the post.
nvm i fixed it
imbadsus said:
nvm i fixed it
Click to expand...
Click to collapse
Bro can you please tell me how did u fix it? Im stuck on the same thing after 700 sec it says time out and my mi pad 5 pro is stuck on fastboot now. Please help
JohnWick90 said:
Bro can you please tell me how did u fix it? Im stuck on the same thing after 700 sec it says time out and my mi pad 5 pro is stuck on fastboot now. Please help
Click to expand...
Click to collapse
im not really that sure, i just tried some stuff and ended up fixing it.
the last thing i did that i can remember was adding a firehose file into my images folder in the rom i was trying to flash
JohnWick90 said:
Bro can you please tell me how did u fix it? Im stuck on the same thing after 700 sec it says time out and my mi pad 5 pro is stuck on fastboot now. Please help
Click to expand...
Click to collapse
Bro did you fixed it. I have the same problem rn. Please help me bro
Yes bro i was able to flah official chinese rom and it was easy as a pancake
arun74140 said:
Bro did you fixed it. I have the same problem rn. Please help me bro
Click to expand...
Click to collapse
Yes bro easy peasy lemon squeezy
JohnWick90 said:
Yes bro easy peasy lemon squeezy
Click to expand...
Click to collapse
How bro. Please explain bro. My phone is stuck in fastboot mode. I don't know what to do right now. I tried flashing original rom. But it didn't work. It still says error time out
It shows this
{
"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"
}
arun74140 said:
It shows thisView attachment 5729551
Click to expand...
Click to collapse
im not good at these things but you should maybe try changing usb ports and another cable if you have one available
maybe try flashing in edl mode to, that may work but im not sure
JohnWick90 said:
Bro can you please tell me how did u fix it? Im stuck on the same thing after 700 sec it says time out and my mi pad 5 pro is stuck on fastboot now. Please help
Click to expand...
Click to collapse
Hello, how did you do it? my my pad 5 pro 5g entered fastboot mode and it doesn't work and I'm trying to flash and it says error: flash timeout 5856.. help!!
hanniakrystal said:
Hello, how did you do it? my my pad 5 pro 5g entered fastboot mode and it doesn't work and I'm trying to flash and it says error: flash timeout 5856.. help!!
Bro pls reach me on my snap im not active here snap alijunaid1990
Click to expand...
Click to collapse
imbadsus said:
Hello,
I wanted to root my phone to MIUI version 13.
I have rooted before and I was at MIUI 12.6.
While I was romming my phone it failed (which i didnt see) and followed the guide and wiped everything.
Now I am stuck without an operating system, I have tried flashing but when I was flashing and it came to 1201 seconds then it said "error: flash timeout"
Does anyone know what to do?
Click to expand...
Click to collapse
I found a way. mi flash tool seems to have a time limit of 700 seconds, so we have to flash the rom with less time than that. Previously I flashed using my old laptop (using HDD) and there was a timeout error. then I borrowed my friend's laptop which has pretty good specs (using SSD) and I managed to flash it.
Use old version of miflashtool
Ayuda no me deja flashear..
For those who have the same problem, download the most recent adb platform tools folder and replace the files in the miflash folder, that was my solution.
Hi,
Has anyone been able to successfully relock their bootloader after erasing and flashing stock firmware?
The fastboot command "fastboot oem lock" returns:
"FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
YusukeYuu said:
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
Click to expand...
Click to collapse
Unfortunately I think Sony my have blocked the ability to relock the bootloader
I am using latest 'platform-tools_r33.0.3-windows' and I've also installed specific Sony fastboot driver from Sony Developers.
I am booting into default 'fastbootd' mode.
So this command aint work ?
fastboot oem lock
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
{
"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"
}
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
Click to expand...
Click to collapse
maybe need to use the same serial number that you used to unlock the bootloader
Sakuma_Eitarou said:
maybe need to use the same serial number that you used to unlock the bootloader
Click to expand...
Click to collapse
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
rasseru16 said:
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
Click to expand...
Click to collapse
yes
if you save that number
Weird, my xperia 1 iii can relock
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
View attachment 5720029
View attachment 5720033
Click to expand...
Click to collapse
Try selecting reboot to bootloader first before using the command
YusukeYuu said:
Weird, my xperia 1 iii can relock
Click to expand...
Click to collapse
Did you also update to Android 12 bootloader?
rasseru16 said:
Did you also update to Android 12 bootloader?
Click to expand...
Click to collapse
Yes
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Will give that a go
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Unfortunately, I still receive the same error, oh well I guess only Sony can repair it and relock the bootloader.
You need to go on bootloader not fastbootd mode
YusukeYuu said:
You need to go on bootloader not fastbootd mode
Click to expand...
Click to collapse
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
rasseru16 said:
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
YusukeYuu said:
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
Click to expand...
Click to collapse
Ok thanks, I cannot get the notification icon to turn blue am I doing something wrong? :/
You should have read my Guides.
fastboot reboot fastboot is the only command You'll need to switch between fastboot and fastbootd.
But just turn off Your Phone. Hold Volume Up and Connect USB. Blue LED and Done
fastboot oem lock
Done
Do a Software Repair with Xperia Companion after. Just liike told in My Guides. Enjoy