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 ((
Related
Today I bricked my phone when I try to flash back to 6.0 because I was lazy and use dd to flash modem(radio).
And here is a warningO NOT flash your nexus 6p's bootloader,radio directly,becuase radio,bootloader image for this phone is packed.Using dd to flashing it directly will make you phone bricked.
And my phone is locked because I want to use device protection.So no luck flash radio via fastboot directly.
So I manage a new way to let bootloader thought bootloader can be unlock.
I learn about "factory reset protection"(frp) partition from
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
.
So all factory reset protection problem is just about that frp partition.You just need to dump it out using dd,then use winhex or other software edit the last bit to 01,then your phone is able to unlock.No need for password.
And don't give the device protection too much hope.Many people can unlock it easily because you just need to edit frp partition.Use jtag tools,wire emmc out,even UART or just download mode,and edit that bit then your phone is unlocked.
Apple is the same.Although apple will check iDevices ID,but many people who fix phones in China has some backdoor to unlock it(means reuse it again,data is loss,but who care these data).
{
"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"
}
akaHardison said:
Today I bricked my phone when I try to flash back to 6.0 because I was lazy and use dd to flash modem(radio).
And here is a warningO NOT flash your nexus 6p's bootloader,radio directly,becuase radio,bootloader image for this phone is packed.Using dd to flashing it directly will make you phone bricked.
And my phone is locked because I want to use device protection.So no luck flash radio via fastboot directly.
So I manage a new way to let bootloader thought bootloader can be unlock.
I learn about "factory reset protection"(frp) partition from
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
.
So all factory reset protection problem is just about that frp partition.You just need to dump it out using dd,then use winhex or other software edit the last bit to 01,then your phone is able to unlock.No need for password.
And don't give the device protection too much hope.Many people can unlock it easily because you just need to edit frp partition.Use jtag tools,wire emmc out,even UART or just download mode,and edit that bit then your phone is unlocked.
Apple is the same.Although apple will check iDevices ID,but many people who fix phones in China has some backdoor to unlock it(means reuse it again,data is loss,but who care these data).
View attachment 3679303
Click to expand...
Click to collapse
can you detail the process with pictures if possible.. should help a lot of ppl around here..
rohit25 said:
can you detail the process with pictures if possible.. should help a lot of ppl around here..
Click to expand...
Click to collapse
run "adb shell" in PC
then
"cd /dev/block/platform/s*/f*/b*n*"
then type "dd if=frp of=/sdcard/frp",then the frp partition is dumped in the /sdcard.
use winhex or else edit the last 00 bit to 01,then save the files.
put the frp files back to /sdcard,use "dd if=/sdcard/frp1 of=frp"to flash the unlocked frp back(make sure you are in /dev/block/platform/soc.0/f9824900.sdhci/by-name)
reboot to bootloader,use "fastboot flashing unlock",select yes,then good to go,
Genius ...... Very bad English and grammar.....but I see what you are saying and is pure genius.
What I'm saying is its hard to follow.
Genius guy , dd is dangerous but life saving too
Sent from my Nexus 6P using Tapatalk
Wow, mosdef badass
cool, I wondered about this method months ago but too scared to try it. thanks for trying and sharing it here. cheers!
if you have adb access you can dd a modified devinfo partition back.it will unlock your phone directly.
Sent from iPhone ,using Tapatalk.
this way can work when i have adb access very good idea , what about if i don't have access to adb just fastboot and stock recovery is there any method to unlock my n6p .
Thanked
tenfar said:
if you have adb access you can dd a modified devinfo partition back.it will unlock your phone directly.
Sent from iPhone ,using Tapatalk.
Click to expand...
Click to collapse
hi,
what do you mean by this? I have a LG V10 H901 and I have adb access. what do you mean by modding the devinfo
sorry for being noob
thanks
SuperZoilus said:
hi,
what do you mean by this? I have a LG V10 H901 and I have adb access. what do you mean by modding the devinfo
sorry for being noob
thanks
Click to expand...
Click to collapse
maybe modding devinfo only works for Nexus 6p. try OP's method
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
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and fastboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
biggestpoyo said:
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and flashboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
Click to expand...
Click to collapse
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Ebebeeh said:
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Click to expand...
Click to collapse
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
{
"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"
}
biggestpoyo said:
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
Click to expand...
Click to collapse
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Let me know if it works.
Click to expand...
Click to collapse
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Click to expand...
Click to collapse
Try using mi flash tool with the same image file, you will find the tool on their official website.
biggestpoyo said:
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Click to expand...
Click to collapse
You have MTK variant (Nikel) and trying to flash Snapdragon (Mido) TWRP.
updated to 11.0.2 MIUI and root disapeared , using ADB for TWRP installing , everything goes ok, but after command fastboot reboot , when phone reboots, there is no TWRP , only standart recovery, What I am doing wrong?
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
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