Help LINUX CHIP ON PHONE

[Samsung786]

HI again
well there is alots of CHIP ( EMMC ) inside the Phone if you take off the Mobile Body Like this you can see the black blocks ( i forgot the name i call them CHIPS )

SO my Question is
as Android Phones are Based on Linux then WHICH CHIP CONTROL THE LINUX FILES ?
if i change them then the ALL FILES EXIST ON THE CHIPS WILL BE REPLACED

 

[lvt]

There is a flash memory where everything is stored, this memory can be divided into different partitions for different types of software, from system files to user data files... You don't need to replace the memory chip to replace the files, you can change whatever you want in the chip from a computer using a data cable if you have the software designed for that purpose.

 

[scary alien]

I'd also guess that actually replacing one of the chips / integrated circuits on a small form-factor device like a phone would be very difficult because of the very small size of the connections ( ).

Flashing / re-installing Android (and therefore Linux) is a very device-dependent task so you'd need to consult the proper and specific instructions for your device.

 

[Samsung786]

Actully Unfortunately i put the file called Restart.SH ( as we know that .sh file is used in linx) on his linux
now my phone is restart again and again after Logo i can't flash what should i Do how can i remove that File ?
is there any way ? i connect the data cable to my pc and it direct connect to linux ?

 

[Hadron]

So what is this shell script and where did you place it? Just putting a file on the phone doesn't cause a problem unless the phone has been told to execute it (e.g. you've enabled init.d support and placed it in the appropriate directory, except that the filename is wrong for that). So we'll need more information to work out what you've done. If you modified or removed an existing system file that would be used during the boot up that could cause this type of problem without you needing to have explicitly added an instruction to restart (if you crash it early in the Android boot sequence it will loop like this).

However, in order to mess the system up you presumably have root access. If so, do you have a custom recovery? If you have then you should be able to boot into recovery mode and use ADB commands over usb from a computer to replace or remove the file that's causing the problem.

 

[scary alien]

OP, are you still talking about your Samsung S3 Mini?

(http://androidforums.com/threads/device-software-uninstall.935793/ note: I moved that thread to the SG S3 Mini root area for you)