Menu
Sites
Language
SEC S5PC210 Test B/D

The device U1HD is off and doesn't respond to any actions. My Windows OS finds it as SEC S5PC210 Test B/D. I don't know how it happents.I had a vacation and dodn't switch on it for one week. Now it doesn't work.

Any sugestions? 

Regards,

Roman

Edited on 18 03, 2014
List

Responses

9 Replies
Peter Wegner
You have an bigger problem, because Bootloader erased... maybe Memory dead. Use Google for: SEC S5PC210 Test B/D Only in THEORY it is possible to write Boot with cable + special Software and Tools... But this is Samsung Secret. One real solution is to use JTAG... you need to solder wires... Maybe you have chance by your Samsung contact... by replace this bricked handset or they would repair for you... Sorry. Best Regards
Johan Nenzén
Hi, I'm stuck in the same situation as the OP. But after some Googleing I have found out that it might be a way of reserruct the device. This tool http://forum.xda-developers.com/showthread.php?t=1257434 can reserruct the old SGS1 despite a broken bootloader. (I have done it successfully) The application somehow writes a new bootimage directly to the memory spot without being in download mode. If we just could get some info on what addresses and files we need for our Tizen device we can do the same.
Johan Nenzén
Oh, and here is the tool that it uses to write the image: http://www.fluff.org/ben/smdk/tools/
Peter Wegner
Thank you Johan. Short tested with Windows and OTHER handset... Little progress and success. But it seems HIBL is mandatory because Security... And I failed to use BL3... instead SBL... So I think for Tizen + unsupported device... you need someone with high skills in Bootloader Developement/.eversing... Expect no official support... Maybe chance to ask Samsung direct, if they would repair or replace your device... Faster solution. Best Regards
Peter Wegner
Forgotten. Is SEC S5PC110 similar SEC S5PC210... so Question if HIBL is compatible for both... ??? I had never success with Original Tool like dnw... because Security of Retail devices much higher... as Development Board. Best Regards
Peter Wegner
My fault. I can use HIBL + unmodified BL3 For Download Mode I have only fast enough to press Key Combination... like in normal handset... But then next problem... Security... Multiloader not usable... "Warring : Security fail!!" Maybe my fault, because handset complete empty... NV items missing... I have no idea if with Tizen device and S5PC210 easier... So I think this is very tough task... to find solution for Tizen test device... Good luck. Best Regards
Johan Nenzén
Hi, What files did you flash and to what addresses? Have you flashed to the S5PC210 device? As far as I can see the s-boot.bin contains the IBL+SLP. This i s astring from the binary file: "Samsung SLP bootloader IPL" Which in turn tries to boot u-boot.bin. So I think it if we flash both s-boot.bin and u-boot.bin to the appropriate addresses the device might start again. The problem is that I dont know what addresses to to flash to. If you have some kind of IM, let me know. Might be easier to collaborate with direct chat :)
Peter Wegner
Sorry, I am Android idiot... no knowledge about SBL and so on. For my S8500, which is S5PC110 I have more knowledge... Addresses depend on Bootloader/BL3 Version... XXJB6 BL3 working address is: 0x42380000 XXJF4 BL3 working address is: 0x42480000 BL3 is an part of file boot_loader.mbn... also sometimes as ELF available... so much easier to find start address... Also I have RIFF JTAG for emergency... But I have no Tizen testdevice nor someone who is willing to help... It seems Tizen devices can work with Tool RDX_5.3.exe Ram Dump eXtractor... So in theory on working Tizen device in Debug Level High it is possible to dump something... In case of S8500 whole OneNAND Area including Boot... Or someone is able to analyze existing files... http://download.tizen.org/releases/system/ Sorry, I have not enough time nor enough skills yet to find correct "file" + correct address for any Tizen device. Best Regards
Peter Wegner

Magic seems u-boot-mmc.bin...

Renamed as u-boot.bin it seems possible to restore from internal Memory or from external SD card...

It seems VFAT is used...

 

Short investigation of u-boot... same address as in SBL shows RAM address...

Latest u-boot loaded into RAM at 0x43E001C0 and executed from here...

 

I can't test... because I have no eMMC device for Tests... to expensive... for me.

 

Best Regards