[Q] <Q> How to root Sharp Sh 12-c

cheeseus · May 20, 2013

Great! Thank you! I don't have the SH-12C but I will try this once my brother returns - or once I get my hands on my friend's SH-12C. Meanwhile, other owners of the SH-12C can try this and report.

cheeseus · Jul 24, 2013

I am trying to root the SH-12C by following the instructions... They're not working... Something is not right, something is missing maybe.

To begin with, the root package is now impossible to find. I did manage to find it a couple of weeks ago (not from the original download location) and have uploaded it to my website for those who might need it.

I do not understand the command:

cd 初回導入用 ***(just cd into this directory, copy and paste the Japanese into the command prompt or rename the folder to something memorable in English)***

Where is this 初回導入用 folder? I don't have it in the package I downloaded. What's supposed to be in it?

I skipped this line, and continued with the other commands. These three seem to execute without problems:

Code:

adb shell mkdir /data/local/bin/
adb push flash_image /data/local/bin/
adb shell chmod 755 /data/local/bin/flash_image

But this one doesn't make sense:

Code:

adb push Superuser2.3.6.3\su /data/local/bin/

The Superuser I have in the package is just "Superuser.apk", the version isn't part of the name, although the file seems to be this exact version.
Then, the backslash after "Superuser" is strange. What does it mean? Normally, it would mean "inside the Superuser folder". So, I tried "push Superuser.apk\su" and "Superuser\su" and "Superuser2.3.6.3\su" but of course I get "no such file or directory".

So, instead, I pushed "Superuser.apk" and "su" separately. Then I executed this:

Code:

adb push autoexec.sh /data/local/bin/

without problems.

After that I rebooted. Launched SHBreak4 once. Tapped the "Exit" button after a few (ten-twenty) seconds. Then waited for more than 30 seconds. Tapping on SHBreak4 does nothing. I can't seem to launch it again. I tried this a couple of times (after rebooting). In one attempt, SHBreak4 appeared in the list of running apps (tap the right hand side button of the Home launcher). But nothing afterwards...

When I try the "su" command via ADB I get "permission denied" meaning SHBreak4 hasn't managed to do what's expected.

Any ideas? Has anyone got further than this?

ghostparty13 · Jul 24, 2013

Yo I'll try to help you out!

To begin with, the root package is now impossible to find. I did manage to find it a couple of weeks ago (not from the original download location) and have uploaded it to my website for those who might need it.

Hmmm I'm not having any problems downloading the root package from her: http://sun.dyndns.info/sh12c/sh12c_boot_rescue0910.zip

Where is this 初回導入用 folder? I don't have it in the package I downloaded. What's supposed to be in it?

If you're able to download the package from the link I posted immediately above then it should definitely have this folder in it. If you're running Windows XP it's possible you don't have the East Asian languages pack so some of the folder names will just appear as a bunch of squares instead of Japanese characters. Try downloading the root package from the link above and extract it somewhere. Inside there should be four folders and some files. To make entering commands easier it might be best to just change the folder names to "a" "b" "c" and "d". The 初回導入用 folder should have a Superuser folder inside of it as well as three small files. This is the main one.

Code:
I skipped this line, and continued with the other commands. These three seem to execute without problems:

Code:

adb shell mkdir /data/local/bin/ adb push flash_image /data/local/bin/ adb shell chmod 755 /data/local/bin/flash_image

But this one doesn't make sense:

Code:

adb push Superuser2.3.6.3¥su /data/local/bin/

The Superuser I have in the package is just "Superuser.apk", the version isn't part of the name, although the file seems to be this exact version.
Then, the Yen sign (¥)... What does it mean? I have no way to write this sign in my CMD window, and pasting it doesn't work (a question mark is pasted instead).

Again, if you can get the link above to download the Superuser file should definitely have the version name attached. As for the Yen sign... yeah my bad. My computer has a Japanese version of Windows on it and that means that instead of a backslash " \ " it appears as a Yen sign. Just replace the Yen sign with a backslash and you should be fine.

After that I rebooted. Launched SHBreak4 once. Tapped the "Exit" button after a few (ten-twenty) seconds. Then waited for more than 30 seconds. Tapping on SHBreak4 does nothing. I can't seem to launch it again. I tried this a couple of times (after rebooting). In one attempt, SHBreak4 appeared in the list of running apps (tap the right hand side button of the Home launcher). But nothing afterwards...

Not sure why SHBreak4 is failing to open a second time for you but it could possibly be related to one of the problems we ran into above. Try running through the guide using the download attachment link I posted and replacing that Yen sign with a backslash!

Good luck and sorry for totally missing that Yen sign! Let us know how it goes!

cheeseus · Jul 24, 2013

ghostparty13 said:
Yo I'll try to help you out!
Good luck and sorry for totally missing that Yen sign! Let us know how it goes!

Success!

I had to do some of the stuff differently - but in the end it all worked out.

The first problem was the SHBreak4 not wanting to run properly the second time it is launched. So, I decided to "help it out". I installed SHBreak_1.7, ran it, got temp root, installed SHBreak4. Now, when I launched it again, I did see the "Break" option but got an error some files were missing in /data/data/jp.marijuana.SHBreakV4/app_bin/au --- in fact, there was no folder called "app_bin".

Using the temp root permissions I had acquired, I copied manually all the necessary files into /data/local/ and /data/local/bin. --- NOTE that the file "nandunlockshspamp" is not mentioned in the instructions, so at first I didn't copy it, but now I did.

Running SHBreak4 succeeded this time. The "break" option worked nice and easy.

Then I did all the backup. However, I couldn't get SU via ADB ("permission denied"). So, I installed Superuser.apk on the phone, then installed Terminal Emulator.

I ran all the backup commands from the Terminal Emulator. All smooth.

Then pulled the images via ADB, compared them, all was OK.

Again, I couldn't flash to recovery via ADB, so I flashed via Terminal Emulator - smooth.
Booted into recovery, completed the rest of the backup activities.

Successfully pushed "su" into /system/bin/.

Skipped the install Superuser.apk part - I had already installed it.

In the last section (#12),

Code:

su
mount _sd
mount _data
flash_image recovery /mnt/sdcard/mtdbackup/recovery.img
flash_image boot /mnt/data/local/boot_rescue0910.img

I couldn't mount _sd or _data --- got some error that something was missing (in /etc/...). The first "flash_image" command worked via ADB, the second didn't. So I ran the second via Terminal Emulator - no problems.

Well, that's it, I guess. The phone is now fully rooted.

I suppose the first thing I'll try to do is merge the updated apps with their earlier versions in /system/app --- in order to free up some ROM space. That's what I did with my SH-01D and my 005SH.

And, since this isn't my phone, but belongs to a friend, and I will be helping him try to sell it, I won't play with it too much. I managed to put my SH-01D in a boot loop two days ago because I did something really stupid (edited build.prop and changed ALL instances of the phone's name, whereas I should have only changed it in one instance), and it is now travelling to Japan, and I'm hoping Docomo will fix it for me for free...

Thanks for the translation of the root instructions! I only saw your post after I had finished rooting BUT I will soon be re-doing this procedure, as my brother's SH-12C will need rooting too (in a month or so).

....Just tried again, I can't open that link. I guess it is only accessible from Japan. Can you please email it to me --- cheeseus at dir dot bg.

cheeseus · Jul 25, 2013

Guys, HELP please!

The SH-12C went into a boot loop - after the Docomo logo, the Aquos Phone logo loads, rotates for a while, and then pauses... and starts again (just like my SH-01D).

After rooting it, I used Link2SD to integrate the updates of system apps into /system/app, and that's it. The phone was working fine until now, when I decided to reset it to factory defaults (Settings > Privacy). The phone booted into service mode (or whatever it is called) with the droid and the box, did the deleting part, and then rebooted again... into a boot loop.

I tried to start recovery mode - after the Home button starts flashing, I pressed it, it started flashing faster. The Docomo logo stayed for longer, then the Aquos Phone logo appeared, and ...

When I connect the phone to the PC, and type "adb reboot recovery" the droid with a triangle and an exclamation mark appears... But nothing after that.

EDIT: Reading and trying to make sense of the Readme file. Particularly this part:

◆
◆ Key functions
◆
　・Key functions before entering rescue mode
　POWER key : Boot from NAND
　CAMERA key : Boot from SDHC (if the files are in /mnt/sdcard/sdboot/)
　HOME key : Switch to rescue mode
　SEARCH key : Enable the su in adb (flashing button until the end) until the start of the boot. Does not enter rescue mode. Primarily for debugging.

　・Key functions in rescue mode
　POWER key : Boot from NAND to exit the rescue mode
　CAMERA key : Boot from SDHC to exit rescue mode (if the files are in /mnt/sdcard/sdboot/)
　HOME key : Boot from NAND, exit the rescue mode
　SEARCH key : Restart adbd. Primarily for debugging.

I've tried all the buttons... nothing happens --- In some of the cases, the phone will show the Aquos logo and then loop in it.

------------------------------------------------------------------------------------------
26.07.2013
------------------------------------------------------------------------------------------
EDIT 2: OK, I can start SU in ADB.
I am able to mount_sd / mount_data. So I reflashed that boot_recovery0910.img --- first to recovery, then to boot, no errors. When I try to boot - normally or into recovery - I still get to the Aquos Phone logo loop...

The only idea and hope I have at the moment is to find the built-in versions of all those apps in /system/app that I updated and integrated the update of. Because that's the only thing I've done since rooting the phone (I didn't freeze any apps) that could be preventing the phone from booting properly. When I get them, I will push them to /system/app to overwrite the updated ones, and hope this was the problem...

Oh, dear... Just found this text in the Readme:
・RECOVERYパーティションを書き換えたまま、設定＞プライバシー＞オールリセットすると、起動時無限ループに陥って文鎮化するそうなので注意して下さい（未確認）
・If you overwrite the RECOVERY partition, and then reset the phone from Settings > Privacy > reset all, this might brick your phone by causing it to loop infinitely at boot.

cheeseus · Jul 26, 2013

Resurrected!

Sorted! When the phone booted completely and loaded the Home screen, I shouted "aaaaaaaaaaa" and even startled my girlfriend

So, here's what to do if you find yourself in the same situation:

1. Power up the phone. Wait a few seconds till the buttons start flashing. Press HOME - they fill start flashing faster. You are now in recovery (rescue) mode.

2. Plug the USB cable to connect the phone to the PC. Start ADB.

3. Type:

adb shell

You will see $. Now type

su

The cursor will change to #. You now have SU.

4. We assume that you have backed up both the recovery and boot partitions of the phone to the microSD. Now type:

mount_sd

Now type:

flash_image recovery /mnt/sdcard/mtdbackup/recovery.img

If you get a "can't open" error and you are sure the folder and file exist, just change the file's permissions:

chmod 755 /mnt/sdcard/mtdbackup/recovery.img

Now do the same with the boot image:

flash_image boot /mnt/sdcard/mtdbackup/boot.img

Now type:

reboot

The phone should now boot normally. You will not have root permissions. If you want them, you'll need to re-root.

At least I can confirm that updating the system apps and integrating the updates into /system/app is safe and is not the cause for my sufferings.

ghostparty13 · Jul 26, 2013

Sorry a cold has knocked me out for the past few days, glad you were able to get out of boot loop!
From the sound of it it looks like you're saying that you will not normally have root on your phone now. However, I think that su does reside in your system folder (not positive cause I don't have your exact model of phone). Somewhere in this thread somebody posted a link to a widget apk that you could install that supposedly would allow you to flip su on and off at will. Might not hurt to check it out!

cheeseus · Jul 26, 2013

ghostparty13 said:
Sorry a cold has knocked me out for the past few days, glad you were able to get out of boot loop!
From the sound of it it looks like you're saying that you will not normally have root on your phone now. However, I think that su does reside in your system folder (not positive cause I don't have your exact model of phone). Somewhere in this thread somebody posted a link to a widget apk that you could install that supposedly would allow you to flip su on and off at will. Might not hurt to check it out!

I managed to root again. The instructions - as provided, and as posted on my website - do not work for me. This is because the first part, where we push the various files to /data/local or /data/local/bin just won't work on my phone --- although ADB reports that the files were pushed normally.

To overcome this, I put the files on the microSD, then install SHBreak_1.7, get temp root, install Terminal Emulator, and via it copy the files to /data/local (I didn't bother create a /bin/ folder, just put everything in /data/local). Then I run SHBreak4, it does the thing it does. Then I proceed with the instructions - to flash to recovery, again from the phone, via Terminal Emulator (can't get # SU via ADB).

Then reboot to recovery, then copy the SU file to /system/bin. The flash to boot...

As I am selling the phone, I will need to reset it to factory defaults if someone buys it. I hope it won't go into a boot loop again. But even if it does, I should be able to flash the backup image(s) back to the phone, and save the day...

Please, download that package for me (from the original site) and email it to me. I have tried so many times now, it just won't open from here (Bulgaria, the other side of the world). Maybe the reason why I've had to do things differently is because I'm not using the original package?

And get better soon!

--------------------------------------------
EDIT: There is this text in the Readme, and I'll appreciate some help making full sense of it:

・build 01.01.02以前のSH-12CへこのカスタムROMを導入すると無線LANがエラーで利用不能になるようです。
　ソースファイルを追った所、SYSTEMパーティションにある古いファイルとの齟齬が原因と思われますが、
　手元に01.01.02のSYSTEMが無い為、再現が出来ず該当ファイルの特定には至っていません。

Here is my translation (with the help of Google Translate) of the first line, but I'm not absolutely sure it's correct:

After installing this custom ROM, wireless LAN may be unavailable and throw an error message for builds earlier than 01.01.02.

Does it say "earlier than 01.01.02"? Or is 01.01.02 included?

The phone I've rooted has 01.01.03. But my brother's SH-12C, which I will be try to root soon, has 01.01.02 I think. And I'd like to know if his version is at risk of losing wi-fi connectivity...

ghostparty13 · Jul 28, 2013

Again, sorry for the delay!

Try downloading the package from my dropbox here:

https://www.dropbox.com/s/gwhxsvdcmmkcczr/sh12c_boot_rescue0910.zip

If you still can't download it I'll email you!

cheeseus · Jul 28, 2013

ghostparty13 said:
Again, sorry for the delay!

Try downloading the package from my dropbox here:

https://www.dropbox.com/s/gwhxsvdcmmkcczr/sh12c_boot_rescue0910.zip

If you still can't download it I'll email you!

Got it, thank you! This package contains more files than the one I got - it looks like someone has removed "unimportant" bits from it and put it on Mediafire (if I remember correctly). Well, the essential files are the same, which is good.

Meanwhile, I have been struggling with the English translation of the Readme.txt file. Do you feel like helping complete it? It contains a lot more info, and important info, than the general instructions. Here's the link: https://www.dropbox.com/s/fzomulcvx5ioo39/readme_EN.txt

Where I am sure I've got the meaning correctly, I've deleted the Japanese text. Where I'm in doubt, the English translation is next to or above the Japanese text, and some bits haven't been translated at all because I can't make any sense of the Google Translate output.

When this translation is ready, I will upload it to my website - the complete root package - for people to use it

robotechno · Aug 11, 2013

Sorry..i have a sh-12c locked pattern...plz help me find out the way to unlock...google mail account didnot help

Sent from my LT18i using xda premium

cheeseus · Aug 11, 2013

robotechno said:
Sorry..i have a sh-12c locked pattern...plz help me find out the way to unlock...google mail account didnot help

Sent from my LT18i using xda premium

I don't know a way to recover the unlock code/pattern. Never use lock codes/patters that you aren't absolutely sure you remember!

You can try rebooting the phone in Safe Mode. Maybe from there you can reset to factory settings. To boot into Safe Mode: Shut down the phone. Wait for 20 seconds. Press and hold the MENU button. Without releasing the MENU button, press POWER. Do not release the MENU button until the phone has booted completely. You will see "Safe Mode" in the lower left corner.

cheeseus · Aug 29, 2013

Rooting software version 01.01.02

Just rooted my brother's SH-12C, which runs 01.01.02. As the rootikit warns, for software version under 01.01.02, wi-fi may stop working. Indeed, it won't start - returns an error.

The solution is to complete the rooting procedure, i.e. the flash boot_rescue0910.img to the boot partition, do whatever you want to do --- in my case, install Link2SD, TitaniumBackup, and AutoStarts, then integrate all updates to /system/app, backup and uninstall (or freeze) the unwanted built-in apps, and finally, disable a bunch of start-up bloatware items --- then flash the original (backed up) boot.img and only have root access in recovery mode.

If anyone has an idea how to solve this issue --- get wi-fi to work when rooted --- please share your ideas.

P.S. The complete rooting procedure instructions are now available on my website, plus all required files. Using SHBreak v.4 is not mandatory. The initial temp rooting can be done using SHbreak 1.7 / 1.8 + ISTweak too, which are much lighter.

minhdangoz94 · Sep 21, 2013

bootloader

juzz86 said:
Okay, so with the help of xerxesnet and the USB drivers last night, I had a bit of a fiddle around and this is what I found out. I'm sure it's nothing we don't already know. I used a WIndows 7 x64 machine, by the way:

1. Not sure if this is just limited to me or not, but I could only get USB debugging to enable under MTP mode. Sending adb and fastboot commands in other modes would have no effect, as the device can't be found.

2. adb works, and I could access the recovery easily enough. There are no menu items in the recovery, though. I tried tapping all over the screen, all the hardware buttons and quite a few different combinations, but couldn't make any options of any type appear.

3. I couldn't adb or fastboot reboot into the bootloader. It just boots straight into the OS every time. It seems strange that there would be zero access at all.

4. Obviously, fastboot oem unlock didn't work. However, I got an infinite 'waiting for device' loop rather than an error. All drivers were properly installed, so not sure whether the oem unlock command may actually work or not.

I'll have a crack at SuperOneClick tonight, with both psneuter and GingerBreak exploits. I'll also see if I can make any headway with pushing the oem unlock command. It'd be nice if that was all that was standing in the way of removing the NAND lock, although I'm not too hopeful.

I'll have a bit more of a poke around adb and fastboot also, try some of the other commands and see what I turn up. I'll report back in the morning.

Cheers!

thanks so much !
We can't enter to bootloader mode
also can't do anything with recovery
What can we do if Sh12c got brick?

terry11xx · Oct 3, 2013

Could somebody help me !!

I've read cheeseus post about how to restore from boot loop. I tried using his method but it didn't work. My sh12c cannot boot into recovery.

I've bricked my phone when I tried to root it by SHBreak and do a factory reset, after that it won't boot anymore. It stuck in a docomo screen, and not even passing to the AQUOS screen.

Could somebody help me.

(I did not backup my phone before it's bricked and the firmware link in "http://xdaforums.com/showthread.php?t=1332375" isn't working. Could somebody please upload it again?)

cheeseus · Oct 3, 2013

terry11xx said:
I've read cheeseus post about how to restore from boot loop. I tried using his method but it didn't work. My sh12c cannot boot into recovery.

I've bricked my phone when I tried to root it by SHBreak and do a factory reset, after that it won't boot anymore. It stuck in a docomo screen, and not even passing to the AQUOS screen.

Could somebody help me.

(I'd not did backup my phone before it's bricked and the firmware link in "http://xdaforums.com/showthread.php?t=1332375" won't working. Could somebody please upload it again?)

The resurrection method I've described ONLY works if you've rooted the phone using the rooting method described in the same article.

SHBreak only gives you temporary root so it's strange that you're stuck in a boot loop. You have probably disabled or uninstalled some system apps - and this ALWAYS leads to a boot loop if you perform a factory reset. I am sure that other people beside me have warned of this - I sure have in the relevant article on my website.

I'm afraid your only option now is to send the phone to Docomo in Japan.

terry11xx · Oct 3, 2013

Thank you for your reply.

sorry to hear that, I got this phone about a year ago, I've used SHBreak when this tool was just created, and anyone didn't know it'll cause a boot loop.

I tried bringing it back to docomo shops in Japan, but they kept asking me a contact I don't have
(Being a traveler, I can't buy a phone in Japan, so I bought it in a second hand shop.)

According to the shop's policy they cannot restore it for me.

ftck4 · Apr 1, 2014

Root Fujitsu F03D

Hello, Is anyone who help me to root my Fujitsu F03-D ?
Or can said how to use flash tool to make a android version which is rooted ?
Thanks for all answers

:fingers-crossed:

[Q] <Q> How to root Sharp Sh 12-c

Senior Member

Senior Member

ghostparty13

Guest

Senior Member

Senior Member

Senior Member

ghostparty13

Guest

Senior Member

ghostparty13

Guest

Senior Member

New member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Member

Similar threads

Top Liked Posts