need help

---

while trying to install via adb made a mystake and instead of typing this:
dd if=/sdcard/download/boot.img of=/dev/block/mmcblk0p8

typed this:
dd if=/sdcard/download/boot.img of=/dev/block/mmcblk0p4

now device doesn´t turn on mot even shows battery charging


anyone can help?

Well, then you replaced the wrong file...

First, disconnect the battery cable. Sometimes I can't boot at first when it's connected (no idea why). Then, can you boot into recovery? (Hold Volume Down + Power + Home Button) If so, I'd advise you to flash a stock ROM. You can find them in the Galaxy W Development section. I think that'd solve the problem.

Originally Posted by Dusk252

Well, then you replaced the wrong file...

First, disconnect the battery cable. Sometimes I can't boot at first when it's connected (no idea why). Then, can you boot into recovery? (Hold Volume Down + Power + Home Button) If so, I'd advise you to flash a stock ROM. You can find them in the Galaxy W Development section. I think that'd solve the problem.

nop, doesnt turn on, doesnt go to recovery, doesnt go to download, even connected to charger doesnt show the image of battery charging, ive been reading it seems i messed with boot partition.

If you can't even boot into download, then I'm afraid I can't help you. I know of no way of changing the internal SD contents without booting into either recovery or download. I'm sorry I can't be of any help. If at least the logo showed up when you were trying to boot, then building a USB jig could allow you to get into download mode.
I'm nowhere near an expert so there might be someone out there who can help you...

Originally Posted by nemesis.sisemen

nop, doesnt turn on, doesnt go to recovery, doesnt go to download, even connected to charger doesnt show the image of battery charging, ive been reading it seems i messed with boot partition.

If you are even not able to go to download , recovery or charging mode then you have really bricked the phone.
I think the only option is left to use the RiffBox. It can repair the bad boot partition and after that you can flash any Rom.

http://www.jtagbox.com/jtag-news/sam...air-supported/

Thanks,

Dont forget to click Thanks if it really helps you.

Jeez nemesis.sisemen....

I am really sorry to see this, with that phuckin' DD command, it is soooooo dangerous, Data Destroyer....

but you don't need me saying stuff like that, I can only think that your Boot partition must have been corrupted or partially over-written by the boot.img being applied to /dev/block/mmcblk0p4

I don't even know what that block is!!!!

Hope the tool suggested by alidsd will work for you, so you can recover your device.......

I just saw that Riff Box say we have a dual-core MSM8255T Snapdragon chipset, which is interesting....

this info is not generally advertised about our device!!!

http://www.qualcomm.co.uk/products/snapdragon

Anyway, hope all goes well, if you decide to try this method, what you got to lose???

All the best.....

Originally Posted by irishpancake

Jeez nemesis.sisemen....

I am really sorry to see this, with that phuckin' DD command, it is soooooo dangerous, Data Destroyer....

but you don't need me saying stuff like that, I can only think that your Boot partition must have been corrupted or partially over-written by the boot.img being applied to /dev/block/mmcblk0p4

I don't even know what that block is!!!!

Hope the tool suggested by alidsd will work for you, so you can recover your device.......

I just saw that Riff Box say we have a dual-core MSM8255T Snapdragon chipset, which is interesting....

this info is not generally advertised about our device!!!

http://www.qualcomm.co.uk/products/snapdragon

Anyway, hope all goes well, if you decide to try this method, what you got to lose???

All the best.....

thanks for the reply. yes i saw that it messed and copied some files to the boot partition. got a friend that is trying to solve this. if not maybe i will send to warranty and see what happens

Originally Posted by irishpancake

Jeez nemesis.sisemen....

I am really sorry to see this, with that phuckin' DD command, it is soooooo dangerous, Data Destroyer....

but you don't need me saying stuff like that, I can only think that your Boot partition must have been corrupted or partially over-written by the boot.img being applied to /dev/block/mmcblk0p4

I don't even know what that block is!!!!

Hope the tool suggested by alidsd will work for you, so you can recover your device.......

I just saw that Riff Box say we have a dual-core MSM8255T Snapdragon chipset, which is interesting....

this info is not generally advertised about our device!!!

http://www.qualcomm.co.uk/products/snapdragon

Anyway, hope all goes well, if you decide to try this method, what you got to lose???

All the best.....

From RiffBox:
MSM8255T is dual core chipset – it has ARM11 and Qualcomm Scorpion cores.

Here dual core means that CPU and GPU are fabricated into one single package/chip.

Another example of multi core chip is Allwiner A10 , it has CPU+GPU+PMG and ++. by design all the chips are in a single package/chip to preserve space.

So hence we have single core CPU not dual core.