Hi all,

I took my bricked Iphone and checked the source code of Geohots hw upgrade tools.

My symptoms are the following:

ienew stuck at waiting for data

iunew stuck at Spamming AT, Waiting for response

Now I checked the source code and found two possible reasons for this:

Eather a write call is blocking, or the select call is only returning 0 or blocking.

iunew (iunlocker):

void getheader()
{
fd_set nfp;
FD_ZERO(&nfp);
FD_SET(fp, &nfp);
struct timeval tv;
tv.tv_sec=0;
tv.tv_usec=10000;
hlen=0;
while(select(fp+1,&nfp,0,0,&tv)>0)
{
hlen+=read(fp,data+hlen, 0x1000-hlen);
printf("Attempting to read[%d]...%x\n",hlen,data[0]);
}
}

And in main:

printf("Spamming AT, waiting for a response\n");
do {
data[0]='A'; data[1]='T';
if(write(fp,data,2)==-1) {printf("Can't write\n"); return -1; }
//else printf("W\n");
getheader();
}while(hlen==0||data[0]!=0xc0);

I guess that those calls are pretty close to the hardware and I assume that
the reason for those calls could be a broken trace (A17 ? ), I'm going to check that and maybe try to fix it then ....

Maybe somebody has another idea why those calls fail ...

schueppi

hi schueppi,

where are you from?

i have the same problem here.
another person told us the same that the reason is a broken trace.
now i think about how to check the trace. a magnifying glass is not good enough.

what are you gonna use to check the trace? and if its really broken how you gonna fix it??

thx
gstar

edit:
question: if you can fix it what unlock do you choose? the HW unlock or the new SW unlock? iam just curious.

A Magnifying glass should be enough to check the trace.
In any case, try redoing the trace with a pencil, the graphit in there might be enough to connect it again. If its not you might want to solder them back together.

you mean a "bleistift" is enough? and this can fix it forever?
i thought about a conductive pen for trace repairing.

Hi, I am trying to upgrade my unlocked iPhone 1.1.2 OTB using the Official 1.1.3 Upgrader but my iPhone got stuck at "Writing image: 49%". What should I do? Please help. Thanks.

Yes a "bleistift" might be enough to fix it
Well if you have such a pen then use that one instead but watch out that you do not hit any other traces connecting them!

@techcity: Put it in dfu mode, restore to 113 using itunes then use ziphone to activate and jailbreak.
Then install bsd and anysim1.3, set auto-lock to never, put the phone in airplane mode and run anysim1.3

this is not mine - and i cannot find the thread to quote - but thanks to original poster


this worked for me:

make sure the CommCenter plist is unloaded. make sure, while inside folder, you chmod 777 *. if that fails, type ps -A and find the PID's of everything running in the /System/Library/Fr... and then issue kill -9 123 (replace 123 with the PID number of the process). once all those are killed, try bbupdater -f *fls -e *eep command and hopefully it works.

and by the way - when i was stuck @ "AT spamming" or "can't write data" i DID turn the phone on and off cause the terminal was not responding.

everything is working - now but do at your own risk