[TOOL] Newflasher (xperia command line flasher)

[munjeni]

You can't damage it further mean userdata in case you not flasher userdata or some .ta files which respond to factory reset. Experiment yourself! Never ever touch trim area otherwise hard brick is guaranted! You must find which part of the rom cause bootloop and I can't tell you that since my phone is old xperia 10 and I do not have any rollback protection nor to test anything in relation to it! So if you ask me how it work I can tell you I don't know, I have not dealt with such a problem. You should read log and try to figure it out, log is stored inside trim area and you should read them by runnig newflasher from command line with this command:

newflasher Read-TA:2:2050

it will create dump.bin file, open it with an text editor and read.

You will read something like this https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 about vbmeta error in case rollback protection caused boot loop

 

[ripppani]

You can't damage it further mean userdata in case you not flasher userdata or some .ta files which respond to factory reset. Experiment yourself! Never ever touch trim area otherwise hard brick is guaranted! You must find which part of the rom cause bootloop and I can't tell you that since my phone is old xperia 10 and I do not have any rollback protection nor to test anything in relation to it! So if you ask me how it work I can tell you I don't know, I have not dealt with such a problem. You should read log and try to figure it out, log is stored inside trim area and you should read them by runnig newflasher from command line with this command:

newflasher Read-TA:2:2050

it will create dump.bin file, open it with an text editor and read.

You will read something like this https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 about vbmeta error in case rollback protection caused boot loop

Thank you very much! I will try that and let you know how it goes.

 

[ripppani]

You can't damage it further mean userdata in case you not flasher userdata or some .ta files which respond to factory reset. Experiment yourself! Never ever touch trim area otherwise hard brick is guaranted! You must find which part of the rom cause bootloop and I can't tell you that since my phone is old xperia 10 and I do not have any rollback protection nor to test anything in relation to it! So if you ask me how it work I can tell you I don't know, I have not dealt with such a problem. You should read log and try to figure it out, log is stored inside trim area and you should read them by runnig newflasher from command line with this command:

newflasher Read-TA:2:2050

it will create dump.bin file, open it with an text editor and read.

You will read something like this https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 about vbmeta error in case rollback protection caused boot loop

Solved! The device is back alive! I downloaded and flashed the Customized HK firmware back. Now the device has no problem booting, and all my personal data are intact. Thank you so much for your suggestions!

But reading the log, I did not find any error about vbmeta, nor did I find load_and_verify_vbmeta:657: ERROR: vbmeta_a: Image rollback index is less than the stored rollback index.. The word rollback did not show up in the log at all. I think that means the problem was not caused by rollback protection. The log was dumped before I flashed the Customized HK firmware back.

I can provide the log so you can look into it, but could you first tell me, is there any sensitive information I need to redact before posting?

 

[munjeni]

No need log! Did you figured out what was the problem?

 

[ripppani]

No need log! Did you figured out what was the problem?

I'm not familiar with the Android booting process so I can't be sure, but I found this in the log:

Unable to get Panel Config, Not Found
VB: RWDeviceState: read_req err ! status: 0 read status: -15
VBRwDevice failed with: 00000050
Unable to read display cmdline: 00000050

Do you know what that means?

 

[munjeni]

Sorry don't know, here is some info in relation to VBRwDevice function https://o0xmuhe.github.io/2022/11/01/Qual-Android方案Unlock学习-以Oneplus7Pro为例/ its something in relation to verified boot chain, probably you have missed something last time when it failed to boot and that log is stored there... realy don't know, I'm not active here for almost 5 years and doing nothing on android for 5 years and forgot almost all. Things have changed a lot in 5 years, I'm not up to date! I'm just maintain newflasher and thats all, I am not interested in android hacking nor am I interested in android for 5 years : ) If you need any info please consult google search

 

[ripppani]

Sorry don't know, here is some info in relation to VBRwDevice function https://o0xmuhe.github.io/2022/11/01/Qual-Android方案Unlock学习-以Oneplus7Pro为例/ its something in relation to verified boot chain, probably you have missed something last time when it failed to boot and that log is stored there... realy don't know, I'm not active here for almost 5 years and doing nothing on android for 5 years and forgot almost all. Things have changed a lot in 5 years, I'm not up to date! I'm just maintain newflasher and thats all, I am not interested in android hacking nor am I interested in android for 5 years : ) If you need any info please consult google search

I see. You've done a great job. Thanks!

 

[FighterZ007]

Hello guys i want some help.
So i wanted to convert my japanese sony xz3 to global rom but i always get this error

 

[munjeni]

Verify cms error mean that firmware is not compatible with your device

 

[Garech]

I need some help with my Sony Xperia Pro-I. I want to root. The bootloader is unlocked. I tried to flash firmware with Newflasher and it looked like everything was going as expected. Many files flashed. Then it got to the end and my phone bricked. When I try again I get the following: "No usb device with vid:0x0fce pid:0xb00b !" Do you have any ideas? EDIT-I tried again and got the following:

 

[munjeni]

error on powerdown is not critical if the rest is flashed without error, its well known that some devices sometimes respond with error to commands sync and powerdown and thats not problem. If your device can't boot and you have unlocked bootloader thats in most case isue with rom or you have not flashed everything, its always recommend to flash whole rom including all .ta files and all .sin files, bootdelivery & partition files including userdata, than if device not booting you should than care. Also dust inside phone usb port, bad cable, shaky usb port ...etc might cause errors durring flashing.

 

[Garech]

error on powerdown is not critical if the rest is flashed without error, its well known that some devices sometimes respond with error to commands sync and powerdown and thats not problem. If your device can't boot and you have unlocked bootloader thats in most case isue with rom or you have not flashed everything, its always recommend to flash whole rom including all .ta files and all .sin files, bootdelivery & partition files including userdata, than if device not booting you should than care. Also dust inside phone usb port, bad cable, shaky usb port ...etc might cause errors durring flashing.

Thanks

 

[Garech]

error on powerdown is not critical if the rest is flashed without error, its well known that some devices sometimes respond with error to commands sync and powerdown and thats not problem. If your device can't boot and you have unlocked bootloader thats in most case isue with rom or you have not flashed everything, its always recommend to flash whole rom including all .ta files and all .sin files, bootdelivery & partition files including userdata, than if device not booting you should than care. Also dust inside phone usb port, bad cable, shaky usb port ...etc might cause errors durring flashing.

One thing though, the error I showed happens once I accept the newflasher prompts, it doesn't actually move into the flashing stage yet. Is that still normal?

 

[munjeni]

I must see log from the start to the end otherwise I have no idea

 

[Garech]

I must see log from the start to the end otherwise I have no idea

Is that a Newflasher text logged as I used it, or a phone logcat or something else? I will look for it.

 

[munjeni]

When I try again I get the following: "No usb device with vid:0x0fce pid:0xb00b !"

Are you sure you are in flash mode? Looks like you are in fastboot mode, it have diferent vid and pid! Fasboot mode is volumeup+power it give blue led, and flashmode is volumedown+power, green led light, newflasher work only with flash mode

 

[Garech]

Are you sure you are in flash mode? Looks like you are in fastboot mode, it have diferent vid and pid! Fasboot mode is volumeup+power it give blue led, and flashmode is volumedown+power, green led light, newflasher work only with flash mode

It was in recovery/flash mode, green light. Could this be due to drivers?

 

[FighterZ007]

Verify cms error mean that firmware is not compatible with your device

Thanks you

 

[munjeni]

It was in recovery/flash mode, green light. Could this be due to drivers?

Migh be! Also make sure xperia companion is fully closed otherwise usb is busy and newflasher can't see usb device

 

[Garech]

Migh be! Also make sure xperia companion is fully closed otherwise usb is busy and newflasher can't see usb device

Thanks for your helpful responses. I am pleased to report that my Xperia Pro-I US model (XQ-BE62) is rooted!