[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] himister:
Done some research trying to figure why after flashing this boot image rotational sensor stops working and few other bugs happen.

Still got no direct answer but thing is in the kernel code inside the boot.img

Here's what I've figured:

I assume this boot image is patched in ''insecure mode'' and for unknown reason, when recompiled again, something in the kernel doesn't work properly.

But that doesn't matter much, 'cause this image was made for sole purpose to get the initial root access and ease the installation of root tools such as SuperSU.

This is the very tricky job and if boot.img would be recompiled by a slightest offset regarding the boot partition size, when flashed, it will render your device useless (hard brick).

So far, I haven't seen someone reported bricking.

From that we can see how dangerous that procedure can be, and why rooting through adb transfer (by cable) is much safer.

Let's take few things under consideration. Not every boot.img is the same.

Notice, that there are few models of Grand Neo Plus i9060i and i9060i/DS so I'll assume that there are slightest differences in the the rom, that means kernel could be slight different too.

Flashing the boot.img could work but then again, errors appear and result is non functioning hardware like rotation sensor, network connection loss etc.

I hope this helps understanding the risks involved.

So what we can do?

I know few of you explained in several threads in this forum, how to repair rotational sensor but without any deeper explanation, and I'll go just a small step forward.

Advice:

Before stepping into rooting process by this method let's do something logical and try to be cautious.

1st. - Before any modification to the phone, find and download your original rom.

Without it, there's no point discussing any further repercaussions.

(see Settings > About device and check Baseband version and Build number.

This will tell you what to look for.

Find your region code, (ITV-Italy, PHE-Spain, SEE-South Eastern Europe...etc.)

Check sammobile.com, mrcrab.net, registration may be needed.

When original rom is downloaded, you can check the rom in Odin...

Unpack rom from zip. Run Odin without device connected by usb.

Load the rom image under PDA (ver3.07) or AP (ver3.09/10) and you'll see something like this:

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9060IXXU0AOC3_I9060IOXA0AOC3_I9060IXXU0AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..

Now when we know md5 checksum is ok, we can proceed to...

- Extract the rom archive from zip to *.tar.md5 (use winrar or some other archiver)

- Then extract original rom boot.img from *.tar.md5 (for this I used total commander cause it enters directly into md5 without changing the extension and can extract boot.img easily).

From within Windows Explorer you'll have to delete .md5 and leave only *.tar extension...unpack with archiver. There's your original boot.img, with exact kernel for your device.

- Here comes, one handy tool available here on the forum.

It's a Script tool for making the *.tar.md5 from *img.

This way it's easy to convert your raw boot.img into *.tar.md5 file and flash it from Odin without need for Flashify or Rashr.

Everything can be done from Odin and less chance for a failure.

Download Script Tool, unpack from zip, and put your boot.img into this folder (tar-Tool_Odin3-v3.07_by_mkh.mourad)

Run batch.bat and here you have your converted boot.tar.md5.

So, now we have two boot.tar.md5 files.

First is from this thread, use it to root your phone, and 2-nd is one you made. Don't confuse it and interchange them!!!!

The one you make is for flashing after using the Kingo root to restore your original boot.img.

Once you finish procedure, all hardware failures should disappear.

Still not sure if this trips the flash counter in Download/Odin mode.

If anyone knows, please report if this occurs or the yellow triangle appears on boot.

In short:

install drivers for your phone (if not before, download KIES3 and connect device by usb cable.)

1. Flash the boot.tar.md5 from this thread in download mode from Odin.

2. Reboot, USB debugging must be enabled, and root your phone with Kingoroot. SuperSU update, check Normal.

3. If successful, reboot into Download mode again and flash your (fresh made) boot.tar.md5 file from Odin.

Hope this helps.

And again. Everything you do to your device is on your own responsibility....guess everyone has figured that by now....I hope.

Good luck.