Related
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
simms22 said:
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
Click to expand...
Click to collapse
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Click to expand...
Click to collapse
it is easy, enjoy
simms22 said:
it is easy, enjoy
Click to expand...
Click to collapse
So to reassure, the process I listed is good to use for updates?
Forerunner326 said:
So to reassure, the process I listed is good to use for updates?
Click to expand...
Click to collapse
yea, its fine, but you dont have to reboot the bootloader after each flash.
simms22 said:
yea, its fine, but you dont have to reboot the bootloader after each flash.
Click to expand...
Click to collapse
Rebooting the bootloader like this doesn't hurt correct?
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
i wouldnt think so
simms22 said:
i wouldnt think so
Click to expand...
Click to collapse
What does rebooting the bootloader do?
Forerunner326 said:
What does rebooting the bootloader do?
Click to expand...
Click to collapse
just that, reboot the bootloader, nothing else. its been too long since i flashed a factory img! good thing too
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked?
Click to expand...
Click to collapse
You don't.
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
efrant said:
You don't.
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
Click to expand...
Click to collapse
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Forerunner326 said:
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Click to expand...
Click to collapse
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
efrant said:
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
Click to expand...
Click to collapse
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Forerunner326 said:
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Click to expand...
Click to collapse
Yes.
This is my method verified with 5.1.0 D and E variants, this will not wipe your device.
Download images from: https://developers.google.com/android/nexus/images#shamu
Extract all files to your comp including the main .tgz and the .zip inside that
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img (optional if keeping TWRP or you can flash the latest TWRP here)
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot (Or enter recovery and re-root if you kept TWRP)
efrant said:
Yes.
Click to expand...
Click to collapse
Is there anything else I should know before I flash any update files onto the device?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
gee2012 said:
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
Click to expand...
Click to collapse
What about the cache image? Would it go after boot.img gets flashed? Or do I not worry about it?
This is what I have so far.
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. Connect to pc and load platform tools command window
4. fastboot flash bootloader {bootloader-shamu-xxx.img}
5. fastboot reboot-bootloader
6. fastboot flash radio {radio-shamu-xxx.img}
7. fastboot reboot-bootloader
8. fastboot flash system system.img
9 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
10. Boot into TWRP by selecting Recovery Mode on device and pressing power button
11. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm)
12. Reboot (Main menu > reboot)
You can do that after boot:
fastboot erase cache
fastboot flash cache cache.img
11, 12, 13.
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
ONLY FOR 3, NOT 3T!!!!
1- Download the two files:
https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc
https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
you only need
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
and it work on 4.0.2 too
psxsnake said:
you only need
and it work on 4.0.2 too
Click to expand...
Click to collapse
Read:
Migdilu said:
If you have 4.0.2 or older just do steps 3 and 4.
Click to expand...
Click to collapse
You only need that if you are on 4.0.2 or older. The problem is when you are in 4.0.3, that commands dont work on 4.0.3 firmware.
Moderator Information,
I am closing this thread: We have a thread here for this issue: [HOW TO][DM-VERITY FIX]Easy and fast method for removing DM-verity screen
Hello guys no matter what i flash the twrp even its success i cant boot to twrp i followed many instructions but the same i cant boot to twrp some one help please
Arrenlaxmali said:
Hello guys no matter what i flash the twrp even its success i cant boot to twrp i followed many instructions but the same i cant boot to twrp some one help please
Click to expand...
Click to collapse
Can you share us a screenshot when we can see what are you doing to install TWRP recovery?
sakilxda said:
Can you share us a screenshot when we can see what are you doing to install TWRP recovery?
Click to expand...
Click to collapse
Yow hello bro as always you are active helper . I did thisfastboot oem nubia_unlock NUBIA_NX629J
Then fast boot flash recovery recovery.img " i rename the twrp with recovery.img and i cant boot to twrp why im confused i follow the instructions here in xda
Arrenlaxmali said:
Yow hello bro as always you are active helper . I did thisfastboot oem nubia_unlock NUBIA_NX629J
Then fast boot flash recovery recovery.img " i rename the twrp with recovery.img and i cant boot to twrp why im confused i follow the instructions here in xda
Click to expand...
Click to collapse
its for chines version only
if you have Chinese version you have to unlock the bootloader first and then you will be able to flash the twrp recovery
unlocking the bootloader should be on the setting
you cant unlock the bootloader using the oem command in fastboot , you have to unlock it from the setting in developer option
and then enter fastboot and enter the command
fastbooot flashing unlock
remember unlocking the bootloader will erase all your data
em90256 said:
its for chines version only
if you have Chinese version you have to unlock the bootloader first and then you will be able to flash the twrp recovery
unlocking the bootloader should be on the setting
you cant unlock the bootloader using the oem command in fastboot , you have to unlock it from the setting in developer option
and then enter fastboot and enter the command
fastbooot flashing unlock
remember unlocking the bootloader will erase all your data
Click to expand...
Click to collapse
It was unlock bro still i cant enter twrp my rm3 version is 2.27
Arrenlaxmali said:
It was unlock bro still i cant enter twrp my rm3 version is 2.27
Click to expand...
Click to collapse
am in version 2.27 and twrp working fine with me
you have to enter the command
fastboot flashing unlock
and when you boot there is a yellow warning message showing that you have unlocked the bootloader
after that just flash the right twrp file posted on the fourm
good luck
em90256 said:
am in version 2.27 and twrp working fine with me
you have to enter the command
fastboot flashing unlock
and when you boot there is a yellow warning message showing that you have unlocked the bootloader
after that just flash the right twrp file posted on the fourm
good luck
Click to expand...
Click to collapse
I did but look it was success but i cant boot to twrp
Arrenlaxmali said:
I did but look it was success but i cant boot to twrp
Click to expand...
Click to collapse
you doing it wrong, please copy my commands ,
first you have to unclock oem in developer option under settings this is important and then please copy this
fastboot devices
fastboot flashing unlock
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
in your photo you have only used this command
fastboot oem nubia_unlock NUBIA_NX629J
but this is wrong
you have to use
*
fastboot flashing unlock
*
this is important
and then you will be able to flash twrp recovery
em90256 said:
you doing it wrong, please copy my commands ,
first you have to unclock oem in developer option under settings this is important and then please copy this
fastboot devices
fastboot flashing unlock
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
in your photo you have only used this command
fastboot oem nubia_unlock NUBIA_NX629J
but this is wrong
you have to use
*
fastboot flashing unlock
*
this is important
and then you will be able to flash twrp recovery
Click to expand...
Click to collapse
I did all of this but still the same why i dont understand. When i reboot to recovery its show just a fastboot mode why
Arrenlaxmali said:
I did all of this but still the same why i dont understand. When i reboot to recovery its show just a fastboot mode why
Click to expand...
Click to collapse
You can find the solutions here.
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page7
sakilxda said:
You can find the solutions here.
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page7
Click to expand...
Click to collapse
I mean i can boot to system but i cant boot to recovery to twrp
Arrenlaxmali said:
I mean i can boot to system but i cant boot to recovery to twrp
Click to expand...
Click to collapse
Twrp recovery is only for Chinese firmware, did you know?
What's your problem exactly? What do you want to do?
sakilxda said:
Twrp recovery is only for Chinese firmware, did you know?
What's your problem exactly? What do you want to do?
Click to expand...
Click to collapse
Since i csnt update using OTA. I want to flash twrp so i can flash cn roms or global, yes i am cn firmware. i dont understand why i cant update in OTA and flash twrp. Look at the photo failt ota and successful twrp flash but i still i cant boot to twrp
Bro, step by step...
First, lock again the bootloader.
Second, unlock bootloader again.
Third, flash the archives from Europe or Chinese ROM, all the from the same firmware. (Boot, recovery, system, parameters, etc...)
You can see that in the other link.
If you get do all ok, try flash with OTG since Recovery.
sakilxda said:
Bro, step by step...
First, lock again the bootloader.
Second, unlock bootloader again.
Third, flash the archives from Europe or Chinese ROM, all the from the same firmware. (Boot, recovery, system, parameters, etc...)
You can see that in the other link.
If you get do all ok, try flash with OTG since Recovery.
Click to expand...
Click to collapse
Okay bro thanks i will do it
Arrenlaxmali said:
Okay bro thanks i will do it
Click to expand...
Click to collapse
Did you succes?
I have a problem with twrp to, after finish with all step twrp shown once after boot then when I try to reboot twice twrp gone.
Arrenlaxmali said:
Okay bro thanks i will do it
Click to expand...
Click to collapse
Did it work? I have the same problem with my global version.
Fix for "The system has been destroyed" Redmi note 8/8T
This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
Method 1:
1. Install the .exe from here (PC installation).
2. Download Vbmeta and copy to the installed folder.
3. Connect the phone with PC in Fastboot mode.
4. Run "cmd-here.exe" from the installed folder.
5. Run this command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6. Download and Flash recovery using this command fastboot flash recovery recovery.img and Boot to recovery (Vol+ and Power).
7. Flash recovery.zip again in Booted recovery.
If this doesnt work try with the next method
Method 2
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked but wipe everything
2. save user data: will save your data if any and bootloader unlock
3. clean all and lock: wipe everything and will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
5. Internet to download files
enweazudaniel said:
For unlocked bootloader only...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
SIMPLE SOLUTION:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
Click to expand...
Click to collapse
To be fair you dont even need the flash tool having the fastboot rom. Which is really nice if you are not running Windows. Just extract the fastboot package and run the script you need from the folder ( *.sh for mac and linux, bat for windows).
Worked like a charm and fixed my destryoed system.
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Sent from my Redmi Note 8 using Tapatalk
DailyRoutine said:
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Click to expand...
Click to collapse
This didn't work for me
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
Maybe you put the wrong command?
It did work for me. Destroyed after flashing custom rom, flash vbmeta, back to normal.
Sent from my Redmi Note 8 using Tapatalk
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
enweazudaniel said:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
Click to expand...
Click to collapse
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
thanks @the_weird_aquarian, will try it next time if i face this again!
have a good day
Worked
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Wow Thanks a lot. Xiaomi ADBFastbootTool was not working on my systems had tried everything. But thanks to you I was able to boot into recovery within minutes :good:
geekyhellboy said:
Wow Thanks a lot. Xiaomi ADBFastbootTool was not working on my systems had tried everything. But thanks to you I was able to boot into recovery within minutes :good:
Click to expand...
Click to collapse
Happy to help
I wanted to thank you very much because your advice saved my phone
:highfive: :good:
enweazudaniel said:
For unlocked bootloader only...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
SIMPLE SOLUTION:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
Click to expand...
Click to collapse
Phone not detecting in mi flash tool what should I do now
---------- Post added at 07:49 AM ---------- Previous post was at 07:48 AM ----------
DailyRoutine said:
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Sent from my Redmi Note 8 using Tapatalk
Click to expand...
Click to collapse
Give vbmeta link or attached file
---------- Post added at 07:50 AM ---------- Previous post was at 07:49 AM ----------
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
Update drivers and try again
Even with the drivers, my phone is no longer recognized on the pc with fastboot, when sending the command, Wait devices...
mudinhu said:
Even with the drivers, my phone is no longer recognized on the pc with fastboot, when sending the command, Wait devices...
Click to expand...
Click to collapse
try this, in mi flashing tool, first send command then connect device
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Can you give more details about the last step i am trying to go into recovery and cant
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Yup, this method saved me from a bootloop!!!
RoxtarKaran.RK said:
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
Click to expand...
Click to collapse
I saw your video, followed link to your zip file. Nothing to download but wave browser and other junk. Lots of thank u comments but no file.
RoxtarKaran.RK said:
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
Click to expand...
Click to collapse
I found your video and the links are to malware and there are 100 nearly identical videos with the same people thanking different presenters. That is very suspicious sir.
I havew a redmi note 8 global
System has been destroyed after trying to update magisk on Lineage OS
I am unable to boot into "FASTBOOT"
Is there a solution "fix" for that?
I had this happen once before and was able to boot into "fastboot" and fix the problem but this time the only thing I get is "System Has Been Destroyed"
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
unknown option --disable-verity. Can u help me?
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
refresh5 said:
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
Click to expand...
Click to collapse
Just patch boot.img and flash it
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Adnan008 said:
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Click to expand...
Click to collapse
Xperiafirm on xda to download full fw and newflasher to flash it
King081 said:
Xperiafirm on xda to download full fw and newflasher to flash it
Click to expand...
Click to collapse
do we lose data when flashing firmware?
Adnan008 said:
do we lose data when flashing firmware?
Click to expand...
Click to collapse
You can choose using newflasher
King081 said:
Just patch boot.img and flash it
Click to expand...
Click to collapse
Can you tell me how?
zaxdamian said:
Can you tell me how?
Click to expand...
Click to collapse
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
King081 said:
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
Click to expand...
Click to collapse
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
zaxdamian said:
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
Click to expand...
Click to collapse
I don't know what twrp you have, because we don't have one here and clearly your phones bootloader locked, this is about root and not twrp
Ok. I cant unlock bootloader, so how to get boot.img from stock file?
Unlock bootloader:
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
I tried it. Either I'm doing something wrong or it's not working
Everything works, I unlocked it myself, I just don't remember which command:
fastboot oem unlock
or
fastboot flash unlock
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
On comand fastboot flash unlock i have "fastboot: error: ANDROID_PRODUCT_OUT not set"
zaxdamian said:
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
Click to expand...
Click to collapse
Did you do that in fastboot or fastbootD
Fastboot D