voltage on vpp pin

[*MaTeOoSh*]

Hi,

I think I found the reason of my fbus flashing problems. I just measured the voltage between vpp and gnd, and during booting is 0.16 V - far too low, isn't it ?

can you give me a hint, what to check ?

[g-gabber]

Originally Posted by *MaTeOoSh*

Hi,

I think I found the reason of my fbus flashing problems. I just measured the voltage between vpp and gnd, and during booting is 0.16 V - far too low, isn't it ?

can you give me a hint, what to check ?

Hi,

NO, this is not the reason.
VPP is turning no only during flashing.
And VPP voltage is between 9 and 12 volts depend on phone model.

If you what to find the reason of your problem just post the "flash log" file here.

ps. Alex tell on the official forum how to turn on the flash logging.

[*MaTeOoSh*]

yep, switched the logging on, and right, the vpp is turned on by the software. And indeed, everythings right, ~10V appears on vpp pin at end of the cable. So, OK. Anyway phone (N82) refuses to be flashed. There's a known llimitation described in readme regarding fps devices and n82, but no word about fls-5. Anyway, I still fighting ...

EDIT: I restore all loaders from version 8.36.02 and I receive

[ 61.578](195) xx ERROR xx Failed FLE5SendBootstrapDCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)
[ 61.578](195) xx ERROR xx SearchForBootstrap_DCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)

so, followed bph&co notice and copied RAPIDOv11_2nd.fg from 8.24.010 over. And guess what ? Flashing started

BTW. on whole loaders pack 8.24.010 always became "status response ..." which pointed me wrong to failure in VPP. Seems, it was loaders problem ...

Uff ...

[xpmobile]

Originally Posted by *MaTeOoSh*

yep, switched the logging on, and right, the vpp is turned on by the software. And indeed, everythings right, ~10V appears on vpp pin at end of the cable. So, OK. Anyway phone (N82) refuses to be flashed. There's a known llimitation described in readme regarding fps devices and n82, but no word about fls-5. Anyway, I still fighting ...

EDIT: I restore all loaders from version 8.36.02 and I receive

[ 61.578](195) xx ERROR xx Failed FLE5SendBootstrapDCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)
[ 61.578](195) xx ERROR xx SearchForBootstrap_DCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)

so, followed bph&co notice and copied RAPIDOv11_2nd.fg from 8.24.010 over. And guess what ? Flashing started

BTW. on whole loaders pack 8.24.010 always became "status response ..." which pointed me wrong to failure in VPP. Seems, it was loaders problem ...

Uff ...

It is loaders problem. However you can try it on the previous phoenix. Regarding VPP, you can remove diode from your cable to have higher voltage.

Best Regards
Alan Tan

[g-gabber]

Originally Posted by *MaTeOoSh*

yep, switched the logging on, and right, the vpp is turned on by the software. And indeed, everythings right, ~10V appears on vpp pin at end of the cable. So, OK. Anyway phone (N82) refuses to be flashed. There's a known llimitation described in readme regarding fps devices and n82, but no word about fls-5. Anyway, I still fighting ...

EDIT: I restore all loaders from version 8.36.02 and I receive

[ 61.578](195) xx ERROR xx Failed FLE5SendBootstrapDCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)
[ 61.578](195) xx ERROR xx SearchForBootstrap_DCT5 : Timing Values were not passed to an FLE5 function that uses MODE_CONFIRM - 65 (41h)

so, followed bph&co notice and copied RAPIDOv11_2nd.fg from 8.24.010 over. And guess what ? Flashing started

BTW. on whole loaders pack 8.24.010 always became "status response ..." which pointed me wrong to failure in VPP. Seems, it was loaders problem ...

Uff ...

Hi Mate,

nice to heard it


ps. Phoenix's logging system in very powerful debugging system

[*MaTeOoSh*]

Hi,

As I said - finally managed to flash this n82 via fbus, but it was a real pain

1. on loaders 8.32.02 always "Timing Values ..."
2. on loaders 8.24.010 always "status response ..." - this have me mislead
3. on loaders 8.32.02 and RAPIDOv11_2nd.fg from 8.24.010 - success !!

So, once again bugz in Nokia software - no little wonder, that their stocks are falling ...

Indeed, Phoenix logging system is quite comprehensive - lot a useful infos can be read from it.

Anyway, thanks to all for help.

[Bph&co]

Hi,

Very good research. Thanks for posting it!

Regarding VPP, it is switched on and off in a combination of command to
the running algorithm + toggle of the voltage. It is done dynamically
based on settings declared in the flash files + info returned from the
Flash chip. Could be put on for erase of certain blocks, or programming
of some blocks, etc. But i can confirm that is never on while booting(before
the algo is executed).

Regarding the problem with the latest loaders - yes it is really sad.
Let's hope they fix in next Phoenix, i still prefer good old Fbus flashing
to the USB flash.

BR

[*MaTeOoSh*]

Originally Posted by Bph&co

Hi,

Very good research. Thanks for posting it!

Regarding VPP, it is switched on and off in a combination of command to
the running algorithm + toggle of the voltage. It is done dynamically
based on settings declared in the flash files + info returned from the
Flash chip. Could be put on for erase of certain blocks, or programming
of some blocks, etc. But i can confirm that is never on while booting(before
the algo is executed).

Regarding the problem with the latest loaders - yes it is really sad.
Let's hope they fix in next Phoenix, i still prefer good old Fbus flashing
to the USB flash.

BR

Yep, it's noticeable in log - some VPP parameters come from 2nd loader. Interested thing, before I thought, that it's only a stupid voltage applied to flash chip to enable erase - however there's some intelligence

No I see how much work you had to put into fls-5 reversing. Respect !