I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
woooz said:
I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
Click to expand...
Click to collapse
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
persona78 said:
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
Click to expand...
Click to collapse
Unlocked red.
woooz said:
Unlocked red.
Click to expand...
Click to collapse
try to unlock again, and check what it say will you try to unlock.
.
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
.
persona78 said:
try to unlock again, and check what it say will you try to unlock.
Click to expand...
Click to collapse
FAILED (remote: already fastboot unlocked)
persona78 said:
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
Click to expand...
Click to collapse
I know. Tried to flash stock boot img with fastboot and zip with magisk in twrp.
EDIT: I was able to flash boot.img after this, I guess it worked. Thanks!
I have the same problem again... But now unlocking bootloader again doesn't help.
Also reflashed twrp.
Anyone?
woooz said:
Anyone?
Click to expand...
Click to collapse
If you only want to flash boot.img you can do that in TWRP.
keikari said:
If you only want to flash boot.img you can do that in TWRP.
Click to expand...
Click to collapse
Not only and I can't.
When I try flash anything in twrp i get this error:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
woooz said:
Not only and I can't.
When I try flash anything in twrp i get this error:
Click to expand...
Click to collapse
You still didn't fixed since then?
D1stRU3T0R said:
You still didn't fixed since then?
Click to expand...
Click to collapse
When I created this topic all I had to do to fix this problem was unlocking bootloader again.
But few days ago this problem occured again and unlocking bootloader doesn't help.
It's a bug. REINSTALL default firmware it 3 buttons, let it turn on. Unlock boot again and flash twrp. If that does not work either your phone is damaged or you did something wrong in the middle.
Related
I am having a problem after rooting my phone... i want to flash the 'recovery-RA-passion-v2.2.1-CM.img but it does not allow me to.. I am using the Command Promp:
fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
this is the command..but what happens it this:
error: cannot load 'recovery-RA-passion-v2.2.1-CM.img'
Please help!
PS: phone is rooted.
ChortiRok said:
I am having a problem after rooting my phone... i want to flash the 'recovery-RA-passion-v2.2.1-CM.img but it does not allow me to.. I am using the Command Promp:
fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
this is the command..but what happens it this:
error: cannot load 'recovery-RA-passion-v2.2.1-CM.img'
Please help!
PS: phone is rooted.
Click to expand...
Click to collapse
Assuming the device is seen by fastboot, you need to specify the path to the recovery img
have you unlocked ur bootloader to run fastboot commands?
Sent from my Nexus One using Tapatalk
taodan said:
Assuming the device is seen by fastboot, you need to specify the path to the recovery img
Click to expand...
Click to collapse
Same opinion here, most likely the cause is the missing path to the file.
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?
kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks
Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..
szilard0933 said:
Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..
Click to expand...
Click to collapse
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.
czupyt said:
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.
Click to expand...
Click to collapse
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)
szilard0933 said:
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)
Click to expand...
Click to collapse
Username @Trissi puted it here: https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.
czupyt said:
Username @Trissi puted it here:
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.
Click to expand...
Click to collapse
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.
szilard0933 said:
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.
Click to expand...
Click to collapse
As far as I know, TWRP works only until you are on August Security Patch. If you had TWRP, you had to be maximum on August Patch. Maybe you used wrong boot.img. To use OST I think you have to be unlocked critical, but maybe someone smarter will correct me.
You're right, to use Ost tool u have to unlock critical!
2WildFirE said:
You're right, to use Ost tool u have to unlock critical!
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?
szilard0933 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?
Click to expand...
Click to collapse
Have you tried to switch slot to A?
czupyt said:
Have you tried to switch slot to A?
Click to expand...
Click to collapse
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...
szilard0933 said:
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...
Click to expand...
Click to collapse
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
czupyt said:
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Click to expand...
Click to collapse
Thanks GUYS!
Now its working pretty well
And a last question, how can I update the security patches because now I got update failed for 2018-07.
I found this
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
But after downloading update I got install problem..
What failed for you
czupyt said:
What failed for you
Click to expand...
Click to collapse
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..
szilard0933 said:
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..
Click to expand...
Click to collapse
There is a little bit chaos in your words. You wrote once that all is fine now, after that you said update had not worked for you, and you showed steps to OTA update with Magisk with A/B partition scheme. After that you said you reflashed with OST, but you entered fastboot flash command. You also mentioned that your critical unlock bootloader status is true.
Could you run phone in download mode and use fastboot getvar all command and paste here the results?
I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST
have you tried flaashing via edl mode ?
medkim said:
have you tried flaashing via edl mode ?
Click to expand...
Click to collapse
how to do that
Hammad1029 said:
how to do that
Click to expand...
Click to collapse
reboot into edl mode and flash stock rom by mifilash tool
medkim said:
reboot into edl mode and flash stock rom by mifilash tool
Click to expand...
Click to collapse
how do I reboot into edl mode without dissembling the phone
Hammad1029 said:
how do I reboot into edl mode without dissembling the phone
Click to expand...
Click to collapse
reboot into bootloader then issue this command via adb
fastboot oem edl
medkim said:
reboot into bootloader then issue this command via adb
fastboot oem edl
Click to expand...
Click to collapse
it gives "FAILED (remote: 'Device is already locked!')"
@__harmeet reply here please
Hammad1029 said:
it gives "FAILED (remote: 'Device is already locked!')"
Click to expand...
Click to collapse
friend
first of all, you shoud unlock the bootloader
try with this guide
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
@Hammad1029 He Is Right, Firstly Unlock The Bootloader, Then Unlock Its Critical Partition And Boot Up Into EDL Mode By Typing "fastboot oem edl#
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
have tried already it says "FAILED (remote: Flashing Unlock is not allowed"
bump...
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Nebrassy said:
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Click to expand...
Click to collapse
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Hammad1029 said:
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Click to expand...
Click to collapse
I asked you what stock rom you were on
Nebrassy said:
I asked you what stock rom you were on
Click to expand...
Click to collapse
10.0.2
Hammad1029 said:
10.0.2
Click to expand...
Click to collapse
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Nebrassy said:
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Click to expand...
Click to collapse
can I claim warranty on this issue
Hammad1029 said:
can I claim warranty on this issue
Click to expand...
Click to collapse
Hi , sorry for my bad English , if you can open you phone and enter to EDL MODE and flash the stock rom of your device may be solve your problem ,
(I get the same problem trying to install a custom rom)
If you can't acces to EDL via ABD i think that you only can enter to EDL disasembly your phone .. Suertee xd
Yo también me desesperé
same problem
i got the same problem, won't start normally, hangs in boot screen so can't enter the phone to put it in usb debugging, only responce is through fastboot mode. Every attempt is failing due to locked state and unlocking is not allowed.
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