yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
As much as I would like to have root ASAP, I can't try until felica chip confirmation or teiki expiration, whichever comes first.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I want that function too but I haven't set it up until I confirm that all is OK after root...
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
In the SGN2 I think it works as long as the stock recovery is kept, that's why if possible I would go for a root only tool through ODIN, and leave alone the recovery.
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Sorry, been a bit busy lately.

I just checked the rom, and I think something went wrong with rooting... MY BAD! :( ... sorry.

New images have been uploaded and all links refreshed in the original post here...

Regards,

David
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
That is great to hear! That makes life much easier.

I will make a list of apps to remove later on. Can you add cwm, rom manager, and liberty toolbox by any chance?
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
im trying to do that too but still dont clear about the part that after factory reset,my phone still have SuperSU @@

as soon as i know why i will try too.
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
I'd rather if CWM would be a separate flash file. Don't care much about the rest as the osaifu keitai and mobile tv are left in (aside from touchwiz stuff like S Planner)
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
i used same method with Watha and successful unlockedmy phone with 3G but no LTE :D
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Bloatware:

AllShare (about 3 in total)

Chat On

Disaster kit

Dmarket

Dmenue

D... (about 5 in total)

Docomo (about 2 total)

Group Cast

S... (about 7 in total)

しゃべって

タイマー

ドコモバックアップ

ドコモ音声スカ

Application requests: (I will provide apk if needed!)

Cwm

Maildroid

Go launcher ex

Go contacts ex

Go sms pro

Twitter

Line

Mx player

Rocket player

Google calendar
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Perhaps it's better if you can be more specific based on this list I pulled from the ROM. Some modules I am reasonably sure of, but for most of the ones you would like to have removed, it's a bit of a risk for me to guess which apk is which :) ...

AreaMail.apk

CAMobileDaemon.apk

CAnewsWidget.apk

DcmAppManager.apk

DcmContacts.apk

DcmCrossDbService.apk

DcmDatabackup.apk

DcmiConcier.apk

dcm_location_noicon.apk

dcm_location_sub.apk

DcmSaigaiban.apk

DcmSchedulememo.apk

DcmSocialPhonebookService.apk

DcmVoiceEditor.apk

DcmVoiceRecognition.apk

DcmVoiceSearch.apk

DcmWapPushHelper.apk

DecoEmojiManager.apk

dmenu.apk

docomoAccountAuthenticator.apk

DocomoHome.apk

DocomoInitialization.apk

Docomoremotelock.apk

DocomoScreenLockService.apk

docomoset.apk

FeliCaLock.apk

FeliCaRemoteLock3LM.apk

FeliCaRemoteLock.apk

FeliCaTest.apk

FlashBarService.apk

FmmDM.apk

FmmDS.apk

iConcierContents.apk

iWnnIME_M3.apk

JContacts.apk

JpnDioDict3.apk

JpnEpsonMobilePrint.apk

MobileFeliCaClient.apk

MobileFeliCaMenuApp.apk

MobileFeliCaSettingApp.apk

MobileFeliCaWebPluginBoot.apk

MobilePrint.apk

MobileTrackerEngineTwo.apk

MobileTV_JPN.apk

MobileFeliCaMenuMainApp.apk

MobileFeliCaWebPlugin.apk

ContentsHeadline.apk

ContentsSearchWidget.apk

DcmBusinessCard.apk

DcmiChannel.apk

DcmMascot.apk

dMapNavi.apk

DocomoMenu.apk

docomo_remote.apk

docomoWiFi.apk

Gguide.apk

ICTag.apk

iDSetting.apk

JpnManualStubGQ.apk

KoenoTakuhaibin.apk

PacketCounter.apk

PhotoCollection.apk

SindanTool.apk

spmode_mail_downloader.apk

Toruca.apk
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I went into application manager to look at the name bit it didn't show the full apk name...

How about we just play it safe and remove what we (by we I mean you) know is OK to remove?

Good looking out man!
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
In any case once attained root those apps are easily removable/freezeable, and also is quite easy to edit the system part of the rom in case of need.

As of the list of apps to be added, looking at them they have nothing out of the ordinary (that can't be downloaded from the play store)

That depends on how did you set up the APN and what frequencies your current carrier supports (or if it even supports LTE to begin with)
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
convenience my friend.
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
what about

area mail

iコンシェル

omakase lock

The news cafe

ドコモ音声入力

osaifu ketai

???
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
I use the osaifu keitai, and omakase lock I think it's related to that (to lock the felica chip).
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
yes we do need that!

I want to use osaifu keitai after it is confirmed that it works if rooted...
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
We don't seem to have it working on the gn2, but that might be due to the unsecured kernel.
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
I read somewhere that if you leave stock recovery and stock rom with only root it worked fine. Will post a link if I find it.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
hmm.... well if that is the case we are going to have to have rooted rom and several flashes after that to please the osaifu keitai crowd and also future dev...

so prollly 2 roms I will bump up to the front?

1. For osaifu keitai users

-rooted rom... thats it

2. For dev happy ppl

-cwm

-mass bloatware removal

-array of bells and whistles
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
damn... didn't see this post until now... i would have done this the other day if i would have known

:crying::crying::crying::crying:

Did anyone test this out yet? I still have another hour until the file downloads.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Flashing now... lets see if this will work!
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
It's a bit frustrating for me to not be able to thoroughly test these roms before making them available, so apologies in advance if there's any inconvenience caused :(

(I can only test on phones I have, eh?)

I am 99,9% sure though that it should now give you root access :)
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Super SU installation failed!

improvment from last time though!...

lookin here for fix"

http://xdaforums.com/showthread.php?t=1900217
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
do you have the luxury to factory reset and wipe cache? I think that's the quickest way to find out if the ROM does what it's supposed to do (by getting rid of any external 'noise' in user data space)

It is kind of strange, because this is a straight forward rooting procedure with the exact same components and steps for all other Jelly Bean rom images I've done for other Galaxy models... :(
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
yup, i did factory reset and wipe cash.

it says in superuser: su binary not found

and there is no "tap to check for updates" by it...
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
Docomo's kernel contains a mandatory access control feature which will remove the binaries.

The ramdisk needs to have this mac service removed to prevent the binaries from being deleted. This is what I was told by jcase, and he unlocked the optimus G on docomo. I've been trying to figure out where the mac service is for the gn2 but couldn't find it.

The same needs to be done for the s3 alpha,
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Ok, thanks for the heads up... I have some homework to do...back to the drawing board.

Stay tuned...
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Thanks both of you... please let me know if I can do anything...
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
can anyone post rom stock image of Sc 03 e or show me how to get it ?

my sc 03e cannt connect to my computer(kies reco since i flashed my phone with david 's rom image (i dont have any back up cause my phone got brick )

sorry for my very bad english :(
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Unaltered stock rom (as is delivered via Kies) can be downloaded here...

Can you provide some details regarding your phone's current status? When you say 'brick', does it boot to a certain stage and no further? Any feedback would help in diagnosing the problem. Thanks.
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
No,my phone already bricked before I flashed my phone with u rom.not u rom cause my phone brick.

what I want to say is with u rom,my phone cannot connect to pc via usb (kies recognized my phone as Sc 03 e but keep showing connecting page all over the time)

thanks for u support.
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
fixed problem with usb connection.i changed Qualcomm USB Setting to DM+MODEM+ADB to unlock my phone and forgot to change it back to MTP+ADB. :D
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
So are there any updates with the root procedure? I am ready to test if there are!
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
From mid-March I wont be in Japan for a while, so I wont have to rely on the FelICa chip and will be able to play with the device too.

Also a bit off-topic. Someone knows if the standard international battery works on the SC-03E even if its 1800mAh instead of 2100mAh?
[Galaxy S III Q&A, Help & Troubleshooting] djnomi:
after reading 12 pages can you guys please confirm if . pre rooted rom is working i mean Root is working?

also please confirm i want to get rid of all JAP applications any english rom is available and also confirm if sms charcatres can be increase more then 160
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Unfortunately, the pre-rooted rom will not work... you can thank Docomo for that :)

Currently it is simple to get rid of certain system apps (like the operator's bloatware) and repackage the rom... it's the standard pre-rooting procedure which will not stand up against the kernel's security measures.
[Galaxy S III Q&A, Help & Troubleshooting] djnomi:
so until now no luck and we have to just wait and watch
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Yeah... up to now lParryU has tested the images that I uploaded a few times, but I was actually making 'blind' changes to the ROM image without knowing the outcome... I might get an SC-03E sometime around summer to test my changes before putting them online. That would make my input/feedback less interesting for you guys for now, since you must be anxiously awaiting some kind of (working) rooting solution, and I understand that.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Yup... loads of fun. Hell, if you get this model, we can buy a 12 pack and test it out together...

:good:
[Galaxy S III Q&A, Help & Troubleshooting] Watha:
There seems to be a new small update out
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
The ROM image of the latest update (MB1) has been made available here...

Currently only stock ROM images are available for download and you can at least restore your phone back to stock using Odin, in case an experiment renders your device inoperable.

Sorry, still no root at the moment...but... stay tuned.
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
I am posting this on behalf of member aki0306.

I have no way of testing the rooted image, so realize that you will be flashing at your own risk. Do however post your results and feedback for others to benefit and learn from. What we all would like to know as well is whether this image will trip the custom counter after you flash it with Odin.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Good morning and thanks for this.

Before I test this, do you know this person well enough to vouch for his/her work?

Was this posted anywhere else so we can read feedback?
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
it seem like PM???i think so.
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
If they used the make factory fs root script from the kbc developers then I'd say it's safe to try out. I'd like to know if this works for you as I tried it for the note 2 system.img, and had mixed results, still had problems with busybox.

Keeps us informed :sly::thumbup:
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
I'm sorry, I actually don't know this xda member. I wanted to analyze his rom image prior to relaying his message to you guys, but I currently just can't allocate enough time to do that.

Again, if anyone does decide to attempt to root based on this member's instructions/method, you are doing it at your own risk.
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
OK, I will pass on testing this for now. This phone is required for work so no **** ups allowed.
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Here's an analysis of the rooting procedure given by aki0306...

1.flash stock rom

※ex u wanna flash MB1 root ROM, u can flash MB1 stock before flash root ROM

This is required because the pre-rooting firmware file only contains the system and cache images (partitions). So you have to flash the original firmware file first to get boot.img, hidden.img, modem.bin, param.bin, recovery.img, sboot.bin and tz.img on your phone in sync with whats to follow. The maker could've packaged it all in that one rooting file to avoid having to flash twice (this is merely a suggestion).

2.into recovery and wipe/factory reset

This is highly recommended to clear any data elements and leftovers from a previous firmware version to prevent unexplainable problems and clashes with the new version

3.flash root ROM

This step flashes the modified system and cache partitions

4.boot

During boot, I suspect that the original kernel will scan and annihilate traces of root (su binary for example). The modified system partition, flashed in step 3, kind of hijacked the install-recovery.sh shell script which was intended to restore a stock recovery partition in case it was corrupt, and uses this script to install/copy the su binary and busybox (straightforward copy/install procedure)

5.install SuperSu or SuperUser from Play Store

SuperSu/Superuser is not included in the image, so that's why you are asked to get it from the Play Store.

Conclusion...

The above presented rooting procedure seems ok. It should work if the root annihilation process takes place prior to execution of the install-recovery.sh shell script... if yes, then it also survives a reboot, because during the next reboot, that script runs again to give you root-access again.

There are no custom kernel and recovery partition images being flashed (all stock), so your custom counter is not triggered.

DISCLAIMER: Regardless of the above analysis, you are still responsible for your own device, so flash at your own risk.
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
I retried the Note 2 version I created from the kbc developers .sh script and can confirm that it does allow for superuser binary to be reinstalled and busybox can also be updated.

You will have to update the su binary each time you reboot as it gets removed on each boot, but it does seem that most root apps work, even stericsons busybox and orange backup that wouldn't work on the root we tried previously on the note 2. The only problem I've had is with Solid Explorer trying to move system objects.

I recommend someone trying it out
[Galaxy S III Q&A, Help & Troubleshooting] aki0306:
i hv root rom on sc-03e

but i cant post outside url

coz i need 10posts

if u need root rom

u can send message to me

thx

---------- Post added at 12:35 AM ---------- Previous post was at 12:11 AM ----------

SC-03E MB1 Root Rom

how to flash

flash from odin

1.flash MB1 stock rom

2.into recovery, wipe/factory reset

3.unzip MB1 Root Rom

4.Flash MB1 Root Rom from odin

5.boot

6.installe Supersu or Superuser on play store

i hv MA6 Root Rom

if u need, u can send message to me

hv fun

thx:D
[Galaxy S III Q&A, Help & Troubleshooting] mikebai:
mark for my friend's sc-03e...

thank you
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I can test this out tomorrow morning, but if anyone can she'd some light on this it would make me feel more comfortable...
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
let me do it first,ill try it tomorrow.my custom counter has been triggered (1 for now) so nothing left for me =))
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I am on 4...
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
sorry guys.first of all i am new to android so can someone explain me this thing.

i followed link posted by aki,got to a china website and saw this pic.

something seem not right :(

link to website

http://lt.imobile.com.cn/forum.php?mod=viewthread&tid=10282917&extra=&page=1
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
This is the kind of stuff I am worried about... that model is it even close to ours and could result in a hard brick.

We will have to wait until someone can put together a ROM based on our phone.

If anyone wants to be the lab rat with this... by all means take one for the team.

If I knew how to make the root image and what not, I would do the development myself.

Anyone care to send me some info to get started on that?

Edit after second look at the image:

sorta reminds me of the SC-02B CM10 procedure where we had to make it look like an I9100 to bypass ROM verification in CWM.

BUT I don't know this author and I can't risk losing what is on this phone or spending JPY70,000 to buy another one...
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
I'm guessing they used the resources from this github, as did I in making the image for the note 2. credit to kbc developers.

https://github.com/kbc-developers/make_rooted_system

If you've got the firmeware.tar you can pull the cache.img and system.img and place them in a directory with all the file from this github and run the script to make a rooted factory system.img

You'll need to be running linux to use it, but its pretty straight forward, although I dunno if they've updated it with your particular model, but all you'd need to do, I would think from looking at the fstab in your ramdisk, is adjust the the script for the SC-02E to refer to the SC-03E

EDIT* It contains a config for your model, I checked. If you don't trust the other user's source, then one of ya should give this a go. Like I say its easy to do.
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
u can bought it with 38000 yen through musbi :D
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I will get on this today. Need to do my research first and my computer is at my gf's house... No linux at work.

that is good to hear. Need to keep a mental note of that!
[Galaxy S III Q&A, Help & Troubleshooting] aki0306:
this cn Rom is working on sc-03e

i flashed this Rom
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
Just a few questions:

1. Android version 4.1.2

-When did this come out?

2. Model Number

-Why is it GT-I9300?

3. Build number

-Why is it jishuzu.taobao.com rather than a build number?
[Galaxy S III Q&A, Help & Troubleshooting] aki0306:
hi mate

1.not yet

2.Rom is GT-I9300

boot(kernel) is MA6

3.sorry i dont know

this rom is better than sc-03e stock rom:good:
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
By all means, I bet it is, but just out of self security... if that firmware is not out yet, how is it there?

care to explain your procedure for making that rom?
[Galaxy S III Q&A, Help & Troubleshooting] aki0306:
gt-i9300 come out JB4.1.2

sc-03e is not yet

transplant gt-i9300 rom to sc-03e
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
The build number is easily edited within the build.prop.

Technically the latest firmware from Samsung is 4.1.2, I don't know why the updated docomo software isn't, probably cos they haven't been able to hack their crappy palette ui into it yet.

If this is a custom rom that is why most likely you see the differences. We run att and other international roms which change or phone to n7105 and 4.1.2 and it works no problem. As long as the system.img has been packaged correctly it shouldn't be a problem to flash.

Like you say it can be an expensive risk.

Sent from my SC-02E using Xparent Skyblue Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
I will just root the rom myself for now.

I just have to extract the cache.img and system.img, put it into the root of the folder, and run the shell script right?

is there anything else I am missing cause this looks too easy...
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
Yeah just the cache.img and system.img. Follow the directory structure laid out in the git comment, it translates fine into English if needed, and you shouldn't have a problem.

All the hard works been done for us, lol!

Sent from my SC-02E using Xparent Skyblue Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
it seem simple and have a certain way to root.but why sometimes it fail???? :(
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
What do you mean fail?

Sent from my SC-02E using Xparent Skyblue Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
phone not being root like the one by david :( correct me if im wrong
[Galaxy S III Q&A, Help & Troubleshooting] IparryU:
So when you flashed the binaries were not installed?

Or making the ROM yourself failed?

Or the ROM from the Chinese source failed?
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
no,i mean with certain step to root phone why it still take a lot of time to root a phone @@ and sometime fail like one post by david (it didnt root phone).
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
The problem here is the carrier docomo have some sort of access control that on boot or init remove the su and busybox binary from the system, thus rendering regular root methods redundant.

I've been told that it is some sort of MAC service that would be in the ramdisk of our boot.imgs but I have yet to find the culprit. If its in the init then we need the kernel source.

The make factory . sh is a work around that applies a temporary fix by reapplying the su and busybox binary after the process which wiped them finishes. It does this on every boot.

Until someone can figure out how to disable this, it's the only way we have full root access in between boots. For the most part it works. The only problem I've had is with solid explorer still causing a hot restart when performing a root access action.

Sent from my SC-02E using Xparent Skyblue Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] davidcsv:
Wow.... been away half a day and you guys have been busy... :)

The traditional rooting method of injecting SU into the system image (effectively pre-rooting it) does not work with the docomo phone for reasons already explained by robobob1221. I don't have this phone, so when I released the pre-rooted image and lParryU tested it, it seemed not rooted, because the SU binary was being deleted during kernel boot.

I can, but I won't mess with the kernel (boot.img), because I do not know how to re-package it with Samsung's signature to prevent triggering the custom counter. There are ways... but you always need a rooted environment to start off with...kind of chicken & egg scenario. Note, it's no big deal to customize the kernel module...the signature is the problem.

The method (presented by aki0306) that I analyzed earlier should work. I will prepare a new stock docomo image with that method later today/tomorrow, but with some minor adjustments to avoid making changes to the /system partition during every boot; I need to test this method on my Korean S3 first before applying it to your phone's image.
[Galaxy S III Q&A, Help & Troubleshooting] didoka_702:
Kies has uploaded Firmware for SC 03E :laugh:
[Galaxy S III Q&A, Help & Troubleshooting] ndruqltn:
tried this with odin 3.07 and got this message:

<OSM> MD5 hash value is invalid

<OSM> SC03E-ROOTED-system_MB1.tar.md5 is invalid.

<OSM> End...

i clicked on PDA...
[Galaxy S III Q&A, Help & Troubleshooting] Robobob1221:
remove the md5 tag from the end so that it ends .tar