yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] sericss:
I couldn't get the root kit to work on the 102sh(ii) even after running it I have no access to the /data, it appears the permissions are not set. :crying:
[Android Q&A, Help & Troubleshooting] cheeseus:
I don't know if this rootkit will work for the 102SH(ii). I guess you can first try the other rootkit, the one that gives you temp root, and then try the instructions I've provided. Good luck!

But are you sure you don't have RW permissions for /data? I was able to write a file (a custom font) in /data/font using ADB even without root on the SH-10D and the SH-02E.
[Android Q&A, Help & Troubleshooting] hek805:
I have a Sharp sh102II and I updated it to 4.04, temprooted and then unlocked with sharp-ste.

The phone works fine until I turn on mobile data. After a while the mobile data kills 2g/3g connection. The phone can see mobile network, but it has dropped off the network. Sometimes the phone reboots suddenly. If I use wifi (and mobile data off), this will not happen.

Anybody knows the cure for this problem ?
[Android Q&A, Help & Troubleshooting] ChinaMobile:
sharp 102sh2 cant root unlock .help

Sharp AQUOS PHONE Softbank 102SH2 Android 4.0.4 Ice

but cant root sim unlock
[Android Q&A, Help & Troubleshooting] cheeseus:
My SH-01D went into a boot loop. It is my fault - I edited build.prop to change the model number so that I could download something from Google Play, but foolishly I changed all instances of the model number... I first rebooted the Android interface only (from Link2SD) and everything was fine but Google Play still wouldn't let me download that app so I made a full reboot... well, I never managed to... the phone got stuck at that moment where it vibrates once while showing the Aquos Phone logo, just before loading the Home screen. And starts spinning the Aquos logo again.

At first I had ADB access to it, I was even able to get SU access. But then lost it - "device not found".

I sent the phone to Japan, it's there now, but my friend realised my guarantee had expired - he will check soon how much they'd charge me for an out-of-guarantee repair. If it's more than a 5-6000 Yen, I'll just leave it. A new SH-01D costs 7,000-10,000 Yen. And my friend told me that for a simple thing like replacing the outer shell Docomo charge 31,500 Yen (#$#@!!&^*) --- they do give a 90% discount if the phone has the "insurance pack" - but mine doesn't...

As a way of repairing the phone, I'm thinking --- if I only manage to get SU access again --- mounting /system as RW and pushing the original "build.prop". I actually tried doing just that -- but without mounting system -- but I would get "device not found", and then all attempts to mount /system failed with "device not found"...

Anyway, if anyone has any ideas how to resurrect my phone, please share!
[Android Q&A, Help & Troubleshooting] cheeseus:
Got to love Docomo!

My friend in Japan managed to get the phone out of the boot loop by overwriting the edited build.prop with the original. Then I asked him to update it. After rebooting, it got stuck at the "update failed" screen. But Docomo accepted it for repairs even though the guarantee had expired - not sure if they would have if it hadn't got stuck during the update. And now they have given me a completely new phone! And re-unlocked it for free!

If anyone's interested in purchasing a brand new SH-01D, shoot me your offer :)
[Android Q&A, Help & Troubleshooting] blackwp:
Hi Cheeseus,

I'm glad to hear that you got your phone sorted. Have you tried to root it? I guess it will be the latest build so I would be very interested to hear if you can get it to permanent root?!
[Android Q&A, Help & Troubleshooting] cheeseus:
Still waiting for it to arrive, should be here tomorrow. I am a bit busy and I'm not sure if I will have the time to play with the rootkit but, on the other hand, it really itches me to :D Surely I will try to root it, and will post again when I do. Hope it all goes smooth.
[Android Q&A, Help & Troubleshooting] blackwp:
If you can perm root it I might be interested in buying it ;)
[Android Q&A, Help & Troubleshooting] cheeseus:
No luck rooting, so far. The automated rootkit "works" like before, that is, it returns a bunch of errors and does nothing.

The real obstacle is I have no access to /data/ --- I can't push the necessary files there. I don't remember how I did it before but I think the rootkit somehow managed to give me temp root and let me push files to /data/local/.

When I try to view this folder using ES File Manager, it says "empty directory" and using Total Commander I get "no permission".

I tried SHBreak 1.7, 1.8, 2.0, 4.4. ... nothing... With 1.7 / 1.8, when I hit "break1" it just starts thinking... and thinking, then I get the "SHBreak is not responding" - I chose to "Wait" but even after choosing this twice, nothing happens, so eventually I kill it.

SHBreak 4.4 loads the first screen with only the "exit" button. On second launch, however, it still loads the same screen --- unlike the SH-12C where RAM is insufficient, here it launches immediately, but does nothing.

I'll keep trying...
[Android Q&A, Help & Troubleshooting] cheeseus:
Hours spent trying different stuff... It's like Sharp tech staff have seen that I've been messing with /data/local and have additionally blocked my access to it...

I found out that I can write to the /data/fonts folder. So I started adapting the rootkit commands to use that folder but no luck. Then I decided to try the first rootkit by Ryu Kenshin...

I can't push files to /data/local, so instead I push them to /data/fonts. But I can't change permissions to 755. When I do it from the PC, I don't get an error, that is, it seems to work but when I got to the reboot part I got a list of "operation denied link failed" messages.

From the phone, I can change folder permissions to 755 or even 777 of the folders inside /data/fonts --- I have created "temp", "local.ln", "local.org" but I can't change the permissions of the files inside these folders, e.g. I can't execute "chmod 755 /data/fonts/local.org/onload.sh" ("operation not permitted").

I can delete all files from inside the "fonts" folder and subfolders but I can't delete the subfolders I have created.

:confused::eek:
[Android Q&A, Help & Troubleshooting] cheeseus:
I am reaching the conclusion that build 2.00.06 can't be rooted. I tried everything.

The first part of the rooting process, the "restore" command doesn't seem to do its task, which is to make /data writeable.

c:\root>adb restore f10d/f-10d_2.ab

c:\root>adb shell
shell@android:/ $ cd /data/data/com.android.settings/a/
cd /data/data/com.android.settings/a/
shell@android:/data/data/com.android.settings/a $ ls -l -d
ls -l -d
drwxrwxrwx system system 2013-09-21 19:08 .
shell@android:/data/data/com.android.settings/a $ ls -l
ls -l
drwxrwxrwx system system 2013-09-21 19:08 file00
drwxrwxrwx system system 2013-09-21 19:08 file01
.............................................................
drwxrwxrwx system system 2013-09-21 19:08 file98
drwxrwxrwx system system 2013-09-21 19:08 file99
shell@android:/data/data/com.android.settings/a $ cd /data/data/com.android.settings/
com.android.settings/ <
shell@android:/data/data/com.android.settings $ ls -l
ls -l
[B]opendir failed, Permission denied[/B]
255|shell@android:/data/data/com.android.settings $

I was able to push "mkdevsh" and "sh01d_unlock" (and all other files) to /data/local/tmp and was even able to chmod them to 777.

The next stem - creating the symbolic link:

adb shell ln -s /sys/kernel/uevent_helper /data/local/tmp

also seems to work.

But I can't get write access to /data to create the /data/local.org folder.

I tried something I though would trick the system -- rather than creating the "local.org" folder inside /data, I created it inisde the only writeable folder -- /data/local/tmp/data/local.org and continued executing the rest of the commands like that...

But the main thing -- getting temp root -- which is accomplished by running the "mkdevsh" script -- just doesn't happen. Strange, because after I chmod 777 mkdevsh, I can execute it (or so it seems):

adb shell /data/local/tmp/mkdevsh

OR

adb shell /data/local/tmp/data/local/tmp/mkdevsh

executes without errors. This means it's working, doesn't it? But when I try to call

/dev/sh

which is supposed to trigger the root access, I get "does not exist".
[Android Q&A, Help & Troubleshooting] Trution:
How i wish theres an installation where we can install stock android on this phone, while still have every feature available. Then this phone would be awesome. Now mine is full of unresponsive apps from time to time and lagging and low batt life.
[Android Q&A, Help & Troubleshooting] blackwp:
Fantastic effort. I thought maybe I was going mad when I couldn't get perm root on my v2.00.05 but they are obviously making a real big effort to shut down root access now with v2.00.06. You really have poked at every back door possible. I guess the moral of the story is to get a v2.00.04 phone, root that and be happy.

As for v2.00.06 do you see any improvement or do you think they just released it to stop root access?
[Android Q&A, Help & Troubleshooting] Jesus Army:
Hi,

I have just tried both rootkits available on cheeseus website (Great site thanks!) and failed on my 102SH (I wanted to try to SIM unlock it before the last update that the phone want to install since a few days, in case they lock this possibility. My softbank contract will be over in a few month and I want to switch to B-mobile).

The one supposed to give temp root does not and I cannot execute the first step after the script because I don't have access to /data/.

The one with temp root is ok until command "adb push mkdevsh /data/local/" because in the same way I get a permission refused for folder /data/.

But I think there might be something to do if I run again

adb shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; done"

and

adb restore f-10d_2.ab

again after reboot and before

adb push mkdevsh /data/local/
adb shell chmod 755 /data/local/mkdevsh
adb shell "echo /data/local/mkdevsh > /sys/kernel/uevent_helper"

I will try that and let you know if I succeed! If yes, I might try to follow the perm root kit after...

But by the way, is there some hidden menu on this phone that can prove that it is SIM-locked? Cause I tried to put a foreign SIM inside and the phone did not complained (But refused to list available network or connect to any but this might be normal as it is an old disabled card from my country that will not work in Japan in any phone...)
[Android Q&A, Help & Troubleshooting] cheeseus:
For the SH-01D, write access to /data/ was disabled in the most recent build version (2.00.05). It's quite possible they did the same with the 102SH. I keep an eye on the 2CH forums, the SH-01D Root thread in case there's any development but nothing so far, just a couple of other people confirming that they can't root it on 2.00.05. Let us know your build version please.

If you've managed to SIM unlock, this won't change with updates. On Docomo phones you can check the SIM lock status by dialling *#*#4669#*#* .

But I don't think this menu is present on SoftBanks.

Anyway, if the phone now accepts a non-SoftBank SIM and you can get access to the home screen/drawer, this means you've successfully unlocked it! Otherwise you wouldn't be able to go past the USIM MEP screen shown as soon as the phone completes boot.
[Android Q&A, Help & Troubleshooting] Jesus Army:
As you predicted, the *#*#4669#*#* menu seems to be disabled on Softbank as it does not show anything but only make the number disappear when you type the last "*". Strange thing is that is does accept a foreign SIM card and let me use the phone (at least with wifi), but I did not launched the very last script of the process that is supposed to SIM unlock the phone... So was the phone sold unlocked??? But from Softbank and don't believe that they would do that...

My build number seems to be different from Docomo because it is "S1020" (And I did not performed the last software update yet).

If I understand it correctly, launching

adb shell "while : ; do ln -s /FOLDER /data/data/com.android.settings/a/file99; done"

and pushing at the same time

allows you to get temporary access to the "/FOLDER" folder right? But I must be wrong because said like this looks too easy...
[Android Q&A, Help & Troubleshooting] cheeseus:
If you can use the phone with a foreign SIM card inside, it must be unlocked. Try a different - active - SIM (by Docomo) and see if you can connect to the Docomo network. If you can, then there's no doubt it's unlocked. However, you won't be able to use carrier data as Docomo filter phone access to data networks by IMEI.

Yes, it should be fairly easy and quick.
[Android Q&A, Help & Troubleshooting] onigami888:
Hi there, been following this thread with interest. Just wondering what would the output be normally if say the command:

adb shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; done"

is executed? I keep getting "link failed File exists" repeated until I Ctrl+C or the phone reboots.
[Android Q&A, Help & Troubleshooting] Jesus Army:
If I don't misunderstood things, this command alone is useless and it is normal to get that reply. It is a loop that has to be executed while you are pushing another command at the same time in order to exploit some kind of system vulnerability. And in this case you will notice a different reply from the loop but it will disappears and go up very quickly...

By the way, my phone is somehow now SIM unlocked without launching the command that I have indicated in my previous post. So I did not completed the tutorial until the last commands but I can use a Docomo SIM card in my 102SH now. Wish I could get root in order to use Data2SD and get a faster phone with a good MicroSD, but it does not seems possible to get perm root with last updates... :(
[Android Q&A, Help & Troubleshooting] cheeseus:
I think you're right but I'm not too sure as I don't have complete understanding of the rooting procedure tricks/exploits.

No, root is not possible for build 02.00.06 on the SH-01D, and maybe the same with the latest build of the 102SH. :(

But great about the SIM unlock!
[Android Q&A, Help & Troubleshooting] onigami888:
I am just trying to achieve a SIM unlock. Here r details of what I got:

SBM102SH

Build S1010

Android 4.0.4

Baseband 01.00.00

Kernel 3.0.21

sharp@B1725003L #1

SMP PREEMPT Thu Aug 30 22:09:13 JST 2012

It was suffering from a boot loop, but occasionally it can boot past "Checking USIM" n get into desktop. Even if it does it will randomly reboot.

I somehow managed to "stabilize" it while trying different things in this thread to quickly temp root it n unlock it while I have a chance to boot to desktop, but lost it after trying a few things. Don't know what I did allowed me to stabilize it, so I "reset all" and going to try again in a controlled fashion

I got access to a "live" Softbank SIM n a prepaid Telstra SIM (Aust) with no credit, so will try to recreate the stabilized condition somehow. I am in Australia at the moment.
[Android Q&A, Help & Troubleshooting] Jesus Army:
With the build S1040 I have just tried to temp root using cheesus's tutorial and now the phone is unlocked even if I did not complete the last steps of the tutorial : http://sharp.cheeseus.org/index.php?page=Applications&id=56

Did not encountered any boot loop luckily...
[Android Q&A, Help & Troubleshooting] ivilvend:
Hi. I have 102sh with s0006 build number, i dont live in japan but the major update is available on my phone, can i update this to ICS? I have read that some have bricked their phone because they have started the ICS update without having the latest build of gingerbread. I wonder what's the last gingerbread build for this phone, i'm worried that i might brick my phone if ill update it.
[Android Q&A, Help & Troubleshooting] ivilvend:
I have successfully upgraded my 102sh II from Gingerbread S0006 build to ICS 4.0.4 S1020 build, then rooted and unlocked it using this tutorial http://sharp.cheeseus.org/index.php?page=Applications&id=56

I have encountered some problems with the last few steps of the tutorial and had to edit some of the directories. Please see the screenshot below.
[Android Q&A, Help & Troubleshooting] onigami888:
Cheers for the update there ivilvend. Sorry for the lack of response, the silly season kicked in and this got put on the backburner. Will give that alternate directory a go when I can.

FYI my reboot loop problem was the reason I'm looking into this root access/unlock information not the other way around. So a reboot loop is not a possible by-product of the steps that has been tried here, unless someone else reported otherwise.
[Android Q&A, Help & Troubleshooting] cheeseus:
Rooting attempt on Build 2.00.06.

I have been working to translate into English the two most recent versions of SHARP Android Rooting Tools (5 and 6.1). In 6.1 I spotted a line of text saying the rootkit might work for unlisted devices as well. So I decided to give it a go (the Temp Root option). The script reports "Rooting successful" at the end but after rebooting, there's nothing. Then I tried running it for the second time but stop before the final step where the phone is rebooted. Tried accessing the /data folder and enabling the root access function in Total Commander but failed, despite what the script said.

Anyway, what the script is reporting while getting executed might be useful. I don't really have the time now to explore this further. I will try to upload the completed translation of version 6.1 to my website later today.

Below are the screenshots. It seems that the last message "root successful" (yeah, I've fixed the typo now :D) appears by accident. Still, it makes me think that there might be a way to root the phone.

Meanwhile, I have found out the I can still write files to /data/local/tmp and change their permissions to 777 but that's it. Can't go any further.
[Android Q&A, Help & Troubleshooting] Saburr:
Hello,

someone get a method, to update the device outside Japan?

Greetings
[Android Q&A, Help & Troubleshooting] blackwp:
My final entry

After mush fun with my sh01d I'm finally giving up on rooting and sadly giving up my 3d in favour for a S5. Farewell all....
[Android Q&A, Help & Troubleshooting] cheeseus:
Time to move on, it seems.

The SH-01D is now old in terms of hardware. I am contemplating upgrading to a new model too. Most likely the SH-01F but waiting for prices to drop some more.

The new SH-01D Docomo gave me after I bricked mine developed some issues. This game I play - heavy on graphics - heats up the device a lot. But now the overheating eventually resulted in damaging the display. About two months ago, three small white streaks/spots appeared right above the processor due to this overheating. And a couple of days ago I noticed that the touch screen isn't registering touches as accurately as before, e.g. I try to scroll, it registers a touch, or doesn't register a touch at all.

Well... all good things must come to an end...
[Android Q&A, Help & Troubleshooting] blackwp:
Oh yes the heat spots. They are horrible. I have had this on both my sh01d that I have owned and always in the same place. They are a shame as the 3d display was nice.

And yes it is heat, what I have noticed is how little heat my sammy s5 produces even when playing games and how long the battery lasts. May be they will make 3d phones again one day...
[Android Q&A, Help & Troubleshooting] sony_mlog:
anyone success in rooting SH102? i hate his default app :(
[Android Q&A, Help & Troubleshooting] blackwp:
Good bye

Good bye sh01d

I hope a 3d phone may return again someday
[Android Q&A, Help & Troubleshooting] spox_kuba:
Hello, Anybody know how to Hard reset SH-01F ? My phone is locked of patten lock screen :(
[Android Q&A, Help & Troubleshooting] whynot4444:
any one can root 104sh new build ? i cant unlock this with new build
[Android Q&A, Help & Troubleshooting] zenithzaw:
All things sh-01d - http://androidrooting.wiki.fc2.com/wiki/DOCOMO%20SHARP%20Android%

happy :)
[Android Q&A, Help & Troubleshooting] y2kbugleung:
Can you please post the original link of the file?

(Not the file hosting, but the message)

The words in readme.txt are all broken...
[Android Q&A, Help & Troubleshooting] Ryu Kenshin:
You mean this link: http://logsoku.com/thread/anago.2ch.net/smartphone/1325071707/ right? or the file?

2012/2/5の#用rootkitツールを利用しています

●前準備
・ターミナルエミュレータをandroidマーケットでインストールする
Android Terminal Emulator
Jack Palevich
https://market.android.com/details?id=jackpal.androidterm&hl=ja

・端末操作（スマホ）の
設定→アプリケーション→開発→USBデバッグにチェックする
・端末とパソコンをusbケーブルで接続
・↓のシャープのホームページで
USBドライバとADB USBドライバーをパソコンにインストール
https://sh-dev.sharp.co.jp/android/modules/driver/

●一時root取得テスト
1.rootest_v2.batを実行する
約30秒後、端末の１回目の自動再起動　3分程度待つ
起動して操作できるようになってから、さらに30秒後に次の操作
【端末操作】
端末の設定アプリケーション->microSDと端末容量->マウント解除

drwxrwx--x system system 2010-01-28 10:34 video
drwxrwxrwx app_81 app_81 2011-12-07 17:44 media
drwxr-x--- root log 1980-01-06 09:00 dontpanic
drwxrwx--- radio radio 2012-02-07 02:32 radio
drwxrwx--x system system 2012-02-07 02:34 dalvik-cache
drwx------ system system 2012-02-07 02:34 backup
drwx------ root root 2012-02-07 02:34 property
drwx------ root root 2012-02-07 02:34 sb
drwxrwx--x shell shell 2012-02-07 02:30 local
drwxrwxr-x system system 2012-02-07 02:31 anr
drwxrwxr-x system system 2012-02-07 02:35 system
drwxrwx--- root root 1980-01-06 09:00 lost+found
↑が表示ならマウント解除の操作は成功して権限取得OK

約10秒後、
【端末操作】
端末の設定アプリケーション->microSDと端末容量->マウント解除

lrwxrwxrwx shell shell 2012-02-07 01:46 recovery -> /dev/shdisp
drwxrwx--- root root 1980-01-06 09:00 lost+found
↑が表示ならマウント解除の操作は成功して権限取得OK

約30秒後、、端末の２回目の自動再起動　3分程度待つ
起動して操作できるようになってから、30秒後に次の操作
【端末操作】
端末の設定アプリケーション->microSDと端末容量->マウント解除

crw-rw-rw- system cache 232, 0 2012-02-07 02:44 shdisp
↑が表示ならマウント解除の操作は成功して権限取得OK

約10秒後、
【端末操作】端末で端末エミュレーターを起動し#が表示される事を確認する。
#が表示さる場合は、一時rootが成功しています

※#が表示されない場合
rootest_v2.batを実行中に黒い画面に
Permission deniedが表示された場合は
一時root取得に失敗してる。
表示された場合は、
マウント解除の操作のタイミングをずらして、
もう一度rootest_v2.batを実行して見てください。

------------------------------------
解説
1.スマホ端末をパソコンからコマンドで操作できるようにするソフト
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll

2.rootkit関係
breaksuidhsdiag
breaksuidshdisp
libsdservice_jni.so
shdisphook
onload.sh

3.ワンクリツールのテストbat
起動直後の↓の操作はタイミングによっては、system権限が取れていないときがあります。
端末の設定アプリケーション->microSDと端末容量->マウント解除

そんな時はrootest_v2.batの
[Android Q&A, Help & Troubleshooting] y2kbugleung:
I have disabled the "area mail" (for notifying about earthquakes) by inserting a Docomo SIM.

However, this message is still showing up very often.

I believe this message does not relate to the "area mail" but something else.

I am using Prey (tracking lost phone).

After switching to the new service provider, Prey always sends me report about my "lost phone".

So I think the notification should be related to changing of base station?
[Android Q&A, Help & Troubleshooting] hkhkhkhk:
This message shows up cause u're using 123

If u wanna get rid of the message go for 3/PCCW/SMV

123/1010 or CSL will have this error message
[Android Q&A, Help & Troubleshooting] y2kbugleung:
I know.

I have been using SMV, and just switched to 123.

I believe there should be a way getting rid of it.
[Android Q&A, Help & Troubleshooting] y2kbugleung:
The message quotation is not finished yet, right?
[Android Q&A, Help & Troubleshooting] hkhkhkhk:
No that's the end of the quotation

This phone got no update for non-japan users and the system is really working like sh*t

I mean the config is actually nice but it's slow comparing to devices with similar config

and the phone hangs a lot too

I am really considering to sell this phone unless any real nice update comes
[Android Q&A, Help & Troubleshooting] y2kbugleung:
sigh...

I was using SMV and the 3G speed is slow. It disconnects often when I am on call.

Now I have switched to use 123, and there is drop-line problem.

(When the notification is shown, there should be connection lost temporary!)

iOS is really a nice OS, but I don't wanna use iPhone.

I love Japanese phone...

I am considering to switch to another Japanese phone...
[Android Q&A, Help & Troubleshooting] y2kbugleung:
そんな時はrootest_v2.batの

It seems that the message is not ended yet...