PDA

View Full Version : error 302 on t-mobile 2.26


rabbit_ears
9th January 2008, 05:43 AM
Very interesting site, thanks to all for their hard work on this...

I have a wizard that was sim unlocked, I followed the unlocking guide to a t to cid unlock and came down to 1.05, unlocked using lokiwiz, went back and reflashed 1.05 again and attempted to put t-mobile 2.26 on and I get a error [302].

It recovers fine from the attempt by removing the battery and turning the unit on...set to 1.01 after reboot.

I guess its still locked?

Any help on what to do from here would be appreciated, I ran the procedure twice and still no joy, still get 302 error before the progress bar leaves 0%, the 1.05 goes smoothly however without errors.

rabbit_ears
9th January 2008, 06:52 PM
Anybody with a solution...tried everything and still pulling my hair out here!

I was at 1.80, went down to buttons 1.5 and unlocked with lokiwiz.

When I try to load tmobile 2.26 it returns the 302 update error before leaving 0%.

Latest wizard tool reports that is is fully unlocked, boot screen reports 1.01 and the tmobile ruu reports 1.5.

Thanks, really need any help the can be provided...don't want to mess the phone up.

zabardast_1
9th January 2008, 08:39 PM
Anybody with a solution...tried everything and still pulling my hair out here!

I was at 1.80, went down to buttons 1.5 and unlocked with lokiwiz.

When I try to load tmobile 2.26 it returns the 302 update error before leaving 0%.

Latest wizard tool reports that is is fully unlocked, boot screen reports 1.01 and the tmobile ruu reports 1.5.

Thanks, really need any help the can be provided...don't want to mess the phone up.

After again flashing Button's 1.05,you got to use lokiwiz 02b again to CID unlock and then upgrade to tmobile 2.26,or download the official carrier's Rom from it's site and flash to recover back to it's default working status and repeat the unlocking method.
Good luck

rabbit_ears
10th January 2008, 12:03 AM
Thanks for your help, I've gone through the sequences a dozen times, at the end of loading button rom the ipl/spl is at 1.01 and lokiwiz is run, shows the unit as unlocked and running t-mobile 2.26 fails a few second after launch with a 302 error.

Wizard tools shows the phone as sim/cid unlocked.

Is there any other safe way to get a good solid rom on before proceeding to flash a wm6 rom.

I was happy with the phone at 1.80, but I want to try the voip client in wm6 instead of using wm5 with sjphone because I hear that the caller can be heard through the ear speaker in wm6 with voip.

I'm not a t-mobile customer, I bought the phone unlocked some time ago so I can't download their rom witout a valid tel number.

I'd like to load mfrazzz's release 5 final.

rabbit_ears
10th January 2008, 07:15 PM
OK, got it!

I had to take an old hard disk out of the closet and put a fresh install of XP on it then installed active sync only to the new install.

Tmobile 2.26 installed then without problems...I have alot of programs on my machine, scaling down to a smaller install of XP was my last resort.

mestrini
10th January 2008, 07:29 PM
OK, got it!

I had to take an old hard disk out of the closet and put a fresh install of XP on it then installed active sync only to the new install.

Tmobile 2.26 installed then without problems...I have alot of programs on my machine, scaling down to a smaller install of XP was my last resort.

Well done m8! :)

Maybe this could serve as an example/lesson to all those with a lot of 'trash' in their systems. CLEAN UP THE HOUSE :p

zabardast_1
10th January 2008, 09:15 PM
Well done m8! :)

Maybe this could serve as an example/lesson to all those with a lot of 'trash' in their systems. CLEAN UP THE HOUSE :p

YUP !!!
I second that.

rabbit_ears
10th January 2008, 11:56 PM
Actually a very clean well organized machine, since I am a programmer and write in many languages there are many programs installed.

I used to have different machines for different purposes but with the power of processors today I simplified it all into 1 box and run vmware for testing server programs, etc.

I figured it was a communications problem, what I will do is put together a few xp boot partitions and use 1 for fussing with my phone.