MacBook Pro "Core i5" 2.7 13" Early 2015 2.7 GHz

CygnusX1 wrote:

Zaya wrote:

CygnusX1 wrote: Need a dump - 2015 - A1502 - MacBook Pro "Core i5" 2.7 13" Early 2015 2.7 GHz Core i5 (I5-5257U)

Anyone!?


Thanks Guys!

What clip do you use with the a1502?

Prototype clip

Is that a brand ?

no, it's a developmental prototype. i've also got a modified KT clip which does the job.

hi CygnusX1
any luck with the a1502 machines? (the 2015 model)
did you also had any succesful attempts on unlocking 2015 models?

i should get a kadentech's 2015 cip pretty soon
to try and unlock mine - an 16gb 2015 model

if i would be able to do so i can send you a clean\original dump
to try on your machine

but would it be the same dump since it's 16gb?

I'm not sure if the ram makes a difference, or if it's just the CPU.

I would advise against using the established method to reprogram in circuit on a1502.

As it stands, the safest way to do this model is to remove the chip and program out of circuit.

I have a KT clip, and while you may interface with the EFI chip with it, something else is going on and causing problems. This is supposedly specific to the a1502 and a1466.

reverendalc wrote: I'm not sure if the ram makes a difference, or if it's just the CPU.

I would advise against using the established method to reprogram in circuit on a1502.

As it stands, the safest way to do this model is to remove the chip and program out of circuit.

I have a KT clip, and while you may interface with the EFI chip with it, something else is going on and causing problems. This is supposedly specific to the a1502 and a1466.

Few posts ago you confirmed the clip was working for 2015 models,
So now its not?
i'm confused

the clip is working. you can successfully interface with the EFI chip with the clip.

the procedure involving using the raspberry pi is what's not working. there is going to be a new procedure very soon

reverendalc wrote: the clip is working. you can successfully interface with the EFI chip with the clip.

the procedure involving using the raspberry pi is what's not working. there is going to be a new procedure very soon

Ok but did you have any succes reading the chip with another programmer?

why yes i have, thanks for asking (-;

reverendalc wrote: why yes i have, thanks for asking (-;

You dont want to share?

my apologies, that was pretty snide of me.

i absolutely want to share, and it's almost ready for sharing. everybody will have access to a newer faster easier process quite soon