[SOLVED] HELP! W350 can not turn on after firmware upgrade
Please help. I followed Flashing with jdflasher to upgrade my W350a (AT&T) and got an error:
log started. plugin compiled Jan 3 2008 / 13:54:44
create session object
used script: pnx5230.xml
turn off the phone, hold "c" button and plug usb cable
found EPIUSB2
connecting...
got response
protocol: 0301 baseband: D000
cid detect
<- cid=53 color=red platform=pnx5230
qhldr: 071213 1552 R2A022_PNX5230_FLASHLOADER.5230_53_RED
<- hello: 071213 1552 PERCXC1720441_R2A022_PNX5230_FLASHLOADER
activateloader
flashID: 897E (Manufacturer: Intel)
<- OTP: status 0 locked 1 cid 52 cert 1 IMEI 35623702xxxxxx
flashing babe: W350_R11CA002_MAIN_TAIWAN_JH_RED53.mbn
flashing 480 blocks
error: PutFiles(putfile(putfile_flash(flashbabe(get89data (IOusb::getblock(time exceed))))))
flashing babe: W350_R11CA002_MAIN_TAIWAN_JH_RED53.mbn
error: PutFiles(putfile(putfile_flash(flashbabe(header(se nd89data(IOusb::sendblock(IOusb::dcu_WriteData(tim e exceed))))))))
error: SetDirectory(setdir(cmd14(send89data(IOusb::sendbl ock(IOusb::dcu_WriteData(time exceed))))))
Now, I can't even turn on the phone. Please Help!!!
Re: HELP! W350 can not turn on after firmware upgrade
Find small program "babeck0.8" and check your .mbn file,maybe is corrupted.You can find that program here in download section - sofware
Re: HELP! W350 can not turn on after firmware upgrade
Quote:
Originally Posted by
seamonkey
Find small program "babeck0.8" and check your .mbn file,maybe is corrupted.You can find that program here in download section - sofware
The following is the result:
babecheck [sswcheck] v0.8 by den_po
loading W350_R11CA002_MAIN_TAIWAN_JH_RED53.mbn... ok
pnx5230 cid 53 red
full hash
number of blocks: 480 (0x1E0)
1st block addr: 0x20100000
1st block size: 0x10000
ok
What should I do?
Re: HELP! W350 can not turn on after firmware upgrade
did u make a back up ? and did u flash it with a full battry
Re: HELP! W350 can not turn on after firmware upgrade
Quote:
Originally Posted by
philzfog12
did u make a back up ? and did u flash it with a full battry
I didn't make a backup. I did flash it with full battery.
Right now, my phone can't turn on. Also, nothing happen when connected to PC, and even connected to power adapter. HELP ME!!!
Re: HELP! W350 can not turn on after firmware upgrade
do u have a other battry spare and se tool (just to see if it still can be ident i know u carnt use it to flash cid 53)
Re: HELP! W350 can not turn on after firmware upgrade
Quote:
Originally Posted by
philzfog12
do u have a other battry spare and se tool (just to see if it still can be ident i know u carnt use it to flash cid 53)
No spare battery. By the way, I think it should be worked when I cannected it to the power adapter even without a battery inside, but it didn't.
Re: HELP! W350 can not turn on after firmware upgrade
right if u have se tool lite con it with the 2 and 5 button just to see if it can still be detected
Re: HELP! W350 can not turn on after firmware upgrade
Quote:
Originally Posted by
philzfog12
right if u have se tool lite con it with the 2 and 5 button just to see if it can still be detected
Welcome to SEtool2 ( LITE edition ) v 1.11
supported DB2010/DB2012 CID49/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
if you like LITE edition - please visit Index of ./ and buy FULL.
Will backup GDFS now.
ChipID: D000,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:53
skipping empty loader...
phone pre-boot failed,possible RECOVERY needed.
Elapsed:9 secs.
Re: HELP! W350 can not turn on after firmware upgrade
so its still working u nead to reflash it try to use sony ericsson update service 1st if not and jdflasher wont work then u will have to use a payservice to reflash it
Re: HELP! W350 can not turn on after firmware upgrade
Quote:
Originally Posted by
philzfog12
so its still working u nead to reflash it try to use sony ericsson update service 1st if not and jdflasher wont work then u will have to use a payservice to reflash it
Finally I got it back to work. I've tried to reflash it with the same PC but got the same message. Then I tried with another PC, everything were perfact. I guess the problem might be the USB port of the first PC. Thank you all.