[au KDDI Sharp IS03] - General Info/Temporary Root/Dump

Search This thread

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Looking for anyone who can help progress things further for this phone. No, I'm not a developer, but I'm learning what I can. Your advice and suggestions are most welcome.

Here's a quick run-down of the phone (as of 10/20/2011) :
  • Full Spec Sheet
  • Model No. - IS03
  • Android Version - 2.2.1 (Froyo)
  • Baseband/Build Number - 01.01.05 (.06 is available but it breaks the temp root)
  • Bootloader/Fastboot/Recovery modes are all inaccessible
  • Short history of root attempts by Build Number (click here)
  • Open Source files from the Sharp Developer website - (click here)

Checklist GREEN : DONE | RED : NOT DONE
  • Root - Temporary ONLY (click here or scroll below)
  • Unlock nand
  • Dumps - system / recovery
  • What am I missing from this checklist?

Temporary Rooting Guide (ISuhax306)
Thanks to cielavenir, goroh_kun, and love_marijuana for the work they've been putting in. This method works if your IS03 is on 2.2.1, with Baseband/Build at 01.01.05. If your Baseband/Build is at 01.01.06 or higher, THIS WILL NOT WORK.

You will need ISuhax306.7z, which is attached in this post.

Do this at your own risk. We are not responsible for any adverse effects that you may cause by attempting these methods.

### This is based on the idea that SuperOneClick is useful to make is03break stable. Thank you reporters. ###

1. prepare (on PC)
adb push data_local /data/local/
adb shell chmod 755 /data/local/is03break
adb shell chmod 755 /data/local/psneuter
adb shell chmod 755 /data/local/busybox
adb shell chmod 755 /data/local/lcd_density
adb shell chmod 755 /data/local/market.sh
adb shell chmod 755 /data/local/autoexec.sh
adb shell chmod 755 /data/local/exploit.sh
adb shell chmod 755 /data/local/finalize.sh
adb shell chmod 755 /data/local/pu
adb shell chmod 755 /data/local/pu.sh
adb shell chmod 755 /data/local/prepare_busybox.sh
adb shell chmod 755 /data/local/reboot
adb shell /data/local/prepare_busybox.sh
adb shell rm /data/local/prepare_busybox.sh
adb shell mkdir /data/local/tmp
adb shell chmod 777 /data/local/tmp

2. prepare su (on PC)
[3.0]
adb push su/30efgh/su /data/local
adb install ISuhax306.apk
[2.3.6.3]
adb push su/23efgh/su /data/local
adb install ISuhax2363.apk

3. exploit (on IS03)
$ /data/local/exploit.sh

---alternatively, on PC---
adb shell rm /data/local/tmp/sh
adb shell rm /data/local/tmp/boomsh
adb shell /data/local/psneuter
adb shell /data/local/psneuter
adb shell /data/local/is03break
---

4. finalize (on IS03)
$ /data/local/tmp/sh
# /data/local/finalize.sh

---alternatively, on PC---
adb shell
$ /data/local/tmp/sh
# cat /data/local/local.prop > /data/local.prop
---

5. reboot

6. utilize root
adb shell rm /data/local/psneuter
adb shell rm /data/local/is03break
adb shell rm /data/local/exploit.sh
adb shell rm /data/local/finalize.sh
adb shell
$ au
# cd /data
# ln -s local root
# chmod 777 local #sed requires directory write permission to change lcd_density.

* ISTweak - toggle /sbin/su http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=single&lid=19&cid=3
* jackpal.androidterm - Terminal
* revised busybox with wget: http://www.mediafire.com/?495qvu33lj6l8 see busybox.7z (use /data/local/prepare_busyboxciel.sh)
 

Attachments

  • is03-1.jpg
    is03-1.jpg
    37.9 KB · Views: 1,146
  • is03-2.jpg
    is03-2.jpg
    40.7 KB · Views: 1,112
  • is03-3.jpg
    is03-3.jpg
    28.3 KB · Views: 1,051
  • is03-4.jpg
    is03-4.jpg
    42.5 KB · Views: 1,243
  • is03-5.jpg
    is03-5.jpg
    30.6 KB · Views: 1,165
  • is03-6.jpg
    is03-6.jpg
    34 KB · Views: 1,143
  • ISuhax306.7z
    1.9 MB · Views: 803
Last edited:
  • Like
Reactions: lundman

pboos

Member
Feb 8, 2009
20
20
You are not alone! :)

I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).

I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon :).

I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone :D. Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au :(. If I could I would. That is why i need wifi tether as soon as possible :D.

Any recommendations on Rooting? Let me know and I will try! :)
 

razor950

Senior Member
Aug 2, 2010
74
29
Hialeah
Have you tried the regular rooting tools, just for kicks?

such as z4root and try both perm and temp root...

If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc :p)
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
You are not alone! :)

I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).

I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon :).

I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone :D. Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au :(. If I could I would. That is why i need wifi tether as soon as possible :D.

Any recommendations on Rooting? Let me know and I will try! :)

Thank you for your response! I recognize you from twitter when I tried to google up information regarding the IS03. I'm trying ADW right now after you suggested it. I was using Launcher Pro, it was all right; however, ADW seems to be a little smoother.

I'm really scared to try to attempt any rooting procedure with my phone too. I do have a backup phone but I'd hate to brick my new purchase so I definitely need to do my research.

That's cool that you work with tonchidot, I've used Sekai Camera a couple times to test it out, but there really isn't too much activity around me other than a lot of landmarks.

Anyways, if I come up with any information I'll let you know on this thread.
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Have you tried the regular rooting tools, just for kicks?

such as z4root and try both perm and temp root...

If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc :p)

I haven't tried any regular rooting tools just yet. I'm still just getting used to using it. As I find out more, especially in terms of bricking, booting into recovery, etc, I'll probably try some rooting tools.

Thanks for your response too, I will PM you with my information shortly.
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
just trying to boot into recovery mode...

I was trying to see if I could boot the phone into recovery mode in the first place, all my attempts have failed so far.

There's the power button, volume up and volume down buttons, and the camera button. Hidden from view (need to take off the back cover) is the reset button.

On a sidenote, I timed the startup process just for kicks:
~2 seconds - "Android au with Google" logo appears
~30 s - IS03 animation appears
~40 s - screen brightens slightly
~43 s - Monochromatic menu lights up, IS03 animation is still playing
~50 s - "Reading au card..." message replaces IS03 animation
~53 s - Home screen with Unlock pattern appears

Anyways, back to this recovery mode business: I tried a method that a couple of other websites suggested which was a combination of Vup and CAM being pressed while being powered on. That didn't work, so I tried all sorts of combinations:

Hold POWER throughout startup
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X

Power on and release power button but
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X

During Startup
Hold CAM, press HOME X
Hold Vup and CAM, press HOME X

At this point, I tried messing around with the reset button. All the reset button does is restart the phone while powered on. Nothing happens if the reset button is pressed while the phone is off. I still tried various combinations anyways but nothing worked.

After perusing some of the other threads, perhaps my phone has this recovery option disabled (likely), doesn't have such a mode (erm, unlikely?), or I just haven't found the right combination yet (also likely).

It's too bad this phone is only in Japan in the moment. I better brush up on my Japanese...
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Tested some Android codes via this page

The only code that seems to work is *#*#4636#*#* which brings up general information that is otherwise easily accessible in the normal menus in this phone.

Hmmm.
 
Last edited:

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
z4root attempt

I've just successfully used z4root's temporary root feature to root the phone. <---- I jumped the gun when I ran z4root for the first time and it said it was successful, oops.

Now what? I don't want to try the permanent root solution yet, especially if I don't know how to get my phone into recovery mode yet.

At the moment:
1. z4root temporary root 'works' (USB debugging needs to be checked)
2. Superuser icon is in the drawer
3. BusyBox is not installed as z4root says it will do
4. Downloaded Titanium Backup, program doesn't work (asks to verify rom root and installation of BusyBox)
5. Installing BusyBox from Titanium Backup doesn't seem to work
6. Installed BusyBox installer from the Market, that works
7. Running the newly installed BusyBox installer, it tells me that I don't have root

Regarding step 7: I'm guessing that BusyBox failed to install during the z4root process even though z4root 'worked', plus trying to install via Titanium Backup didn't work as well. At this point, looks like the temporary root solution is a false positive pending further testing.
 
Last edited:

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Universal Androot time.

That was quick. Attempting to install Superuser for Android 2.0-2.2 (or even 1.5-1.6) didn't work. Here's what I get:

*Rooting your device, please wait...
Generating exploit .. [OK]
Generating su .. [OK]
Generating Superuser.apk .. [OK]
Generating root script .. [OK]


*after about 10 seconds, changes to Installing toolkit ..

After roughly 20 seconds, I get this message:

Failed ! No ~~~ Fu goo ~~~

It looks like the process fails somewhere during the toolkit installation.

Boo.
 
Last edited:

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
ADB issues

Did it really take this long just to resolve all the ADB issues? All I wanted to do was take a simple screenshot of my phone :(

When I plugged my phone into my computer, all of the drivers EXCEPT the ADB installed just fine.

1. Install Android SDK and JRE SDK, Eclipse is optional since I'm not really a developer (link)

2. Install PDAnet for Android (link)

3. Ensure that your ADB files are in the correct folder (at least for the ddms.bat stuff...) (link)

So...I can take some screenshots now...yippee.
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Trying SuperOneClick

Decided to give this program a chance too since I tried the other ones, and I was finally able to get the ADB driver to work.

First Method

1. Restarted the phone
2. USB Debugging is CHECKED
3. Plugged phone into the netbook
4. Started SuperOneClick, clicked Root
5. SuperOneClick will start looping after running RATC and trying to restart the ADB server. Left it like this for 5 minutes.
6a. IF I uncheck USB debugging while it says "Waiting for device" with the USB connection sound indicating a detected device, USB disconnection sound will play and program will wait. If I check USB DEBUGGING again then the program will resume looping
6b. IF I uncheck USB debugging at any time during the loop when the USB disconnection sound has already played (so before the starting up sound can play), the program will be unable to resume looping and just freeze despite shutting off any processes related to this procedure. At this point I need to restart both my netbook and my phone
7. Letting SOC loop for about 10 minutes will result in the program saying NOT RESPONDING and would then need a fresh restart

Code:
Killing ADB Server...

OK

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...
21 KB/s (5392 bytes in 0.249s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...
OK

***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***

Killing ADB Server...

OK

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK

Waiting for device...

OK

Running rageagainstthecage...
OK

***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***

Second Method

1. Leave USB DEBUGGING unchecked
2. Plug phone in, start SOC, click Root
3. When SOC says "Waiting for device", check USB DEBUGGING
4. RATC should start
5. When SOC says "Starting ADB server", uncheck USB DEB, check USB DEB, uncheck USB DEB again before the "Waiting for device" message appears again

I usually can't get this timing right due to some lag on my phone. I got it right a couple of times and after about a minute, SOC will have the NOT RESPONDING indicator on again. At this point, I can check USB DEB and the program might start on a loop again, or I need to restart...again.

With either of the two methods, if I go into my Task Manager on my netbook and kill one of the two ADB.exe (usually the one with the lower memory value) processes, then the program will say FAILED, like so:

Code:
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***

Killing ADB Server...

OK

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK

Waiting for device...

OK

Running rageagainstthecage...

FAILED

Third Method

1. Power off phone, restart netbook
2. Start SOC, click Root
3. When "Waiting for device" message appears, connect phone to netbook
4a. If USB DEB was checked before turning off the phone, SOC will do the looping thing again when the phone is finished turning on
4b. If USB DEB was unchecked before turning off the phone, nothing happens when the phone comes back online

== tl;dr ==

It looks like it's getting stuck at the RATC process and loops from there until it freezes. Range of problems may include: bad USB cables, bad USB ports, and/or this IS03 is one tough SOB.
 
Last edited:

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
z4root permanent root option

Just tried the permanent option with z4root.

Similar process that the temporary process did except the phone rebooted. After the reboot, everything seemed to be working as normal.

BusyBox, Titanium Backup, and Wireless Tether all say I am not rooted, though.

So much for that.
 
Last edited:

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Safe Mode

My efforts to boot the phone into recovery mode have led me into Safe Mode instead.

No big deal.

I still haven't found a surefire way to get into Safe Mode except to keep mashing the Volume Up and Camera buttons while pressing the monochromatic buttons when they finally light up just before the home screen appears.
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Universal Androot 1.6.2 beta 5, Recovery Mode

Interesting thing about this version is that it adds a Soft Root as well as logging to the SDCARD.

1. Uninstalled Universal Androot 1.6.1 (stable)
2. Installed Universal Androot 1.6.2 beta 5 from the SDCARD using App Install
3. Tried all options, including the option not to install Superuser

RESULT: Failed! No ~~~ Fu Goo ~~~

Would you look at that? I can put my phone into recovery mode through adb commands...huh.
 

lundman

Member
Dec 21, 2010
14
2
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...

Thanks for your comments. I feel I'm not really doing much except for poking around to see what kind of reaction I get from the IS03.

If I stumble on something worthwhile, it'll be posted here.

As far as your Skype problem is concerned, when you use Skype, it switches from your WiFi connection to 3g? I believe I can use Skype with my WiFi, but I'll have to pay closer attention to that.
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
Bootloader and Recovery reboot via ADB

Let's see what happens if I try to reboot my phone via ADB in either recovery or bootloader mode.

According to this site, if I'm not mistaken, I anticipate seeing some menu options pop up when I get into either recovery or bootloader mode.

Rebooting into Recovery Mode
1. Unmount SDCARD
2. USB DEBUG is checked
3. Plug the phone into the netbook
4. Windows+R 'cmd' to bring up the prompt
5. get to android-sdk-windows/tools directory
6. adb devices to ensure that the device is listed
7. adb reboot recovery to restart the phone into recovery

Phone reboots and shows a white triangle with a yellow exclamation mark with the green droid icon in front of it. What happens when I do some button combinations? Let's see...

VolUP + CAM = FAIL
VolDN + CAM = FAIL
POW + CAM = FAIL
POW + VolUP = FAIL
POW + VolDN = FAIL
POW + VolUP + CAM = FAIL
POW + VolDN + CAM = FAIL
VolDN + VolUP + CAM = FAIL
Randomly pressing all buttons = FAIL

I can't access any menu here...

Rebooting into Bootloader Mode
Same steps as before, except
7. adb reboot-bootloader to restart the phone into bootloader

The phone restarts and the Android AU with Google logo appears...and it seems to be stuck at this part. Button presses do nothing, no menu or text.

With either method, I have to take out the battery.

Mistaken, I am.
 

somazero

New member
Dec 22, 2010
2
1
ADB Driver

Greetings!

It seems this is the only place I've seen for english speaking IS03 help. I saw that you were able to install the ADB drivers. Are you using a Japanese version of windows?

I was able to get the USB drivers from Sharp's site, but no luck in getting them to work...

I'm using Win 7 64bit, but it seems I can't get the ADB interface to be recognized.

Anyhow, any help would greatly appreciated.
 

pboos

Member
Feb 8, 2009
20
20
adb reboot recovery

starts recovery.. but do not get the menu (no matter which buttons i press)

adb reboot bootloader => hangs in booting? or is that the bootloader?
fastboot devices => no devices.. well. it was worth a try
 

somazero

New member
Dec 22, 2010
2
1
IS03 ADB Drivers

Well, strangely enough, the IS03 drivers wouldn't install for me, but these would:

sh-dev.sharp.co.jp/android/modules/driver/index.php?/003sh/download

(forum wouldn't let me post the link...)

When I have my phone plugged in and I have an emulator running, I get this:

List of devices attached
SSHEV080667 device
emulator-5554 device

I'm assuming the SSHEV device is my IS03, and the other is obvious...

I haven't gotten to much farther than this, but I thought I'd share...The drivers specific for the IS03 Win 7 64bit at this address:

k-tai.sharp.co.jp/support/a/is03/download/usb/index.html

...they didn't work for me. When trying to install the drivers, they weren't recognized.

I'll post more when I get a bit farther...
 
  • Like
Reactions: SharpIS03

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Looks like there is a minor update for IS03.

    http://www.au.kddi.com/seihin/up_date/kishubetsu/au_info_20111006.html

    Among the changes, looks like screenshots will be enabled and the authentication process for sending and receiving emails is going to be strengthened. I wonder if this will have any effect on rooting the phone?
    1
    Looking for anyone who can help progress things further for this phone. No, I'm not a developer, but I'm learning what I can. Your advice and suggestions are most welcome.

    Here's a quick run-down of the phone (as of 10/20/2011) :
    • Full Spec Sheet
    • Model No. - IS03
    • Android Version - 2.2.1 (Froyo)
    • Baseband/Build Number - 01.01.05 (.06 is available but it breaks the temp root)
    • Bootloader/Fastboot/Recovery modes are all inaccessible
    • Short history of root attempts by Build Number (click here)
    • Open Source files from the Sharp Developer website - (click here)

    Checklist GREEN : DONE | RED : NOT DONE
    • Root - Temporary ONLY (click here or scroll below)
    • Unlock nand
    • Dumps - system / recovery
    • What am I missing from this checklist?

    Temporary Rooting Guide (ISuhax306)
    Thanks to cielavenir, goroh_kun, and love_marijuana for the work they've been putting in. This method works if your IS03 is on 2.2.1, with Baseband/Build at 01.01.05. If your Baseband/Build is at 01.01.06 or higher, THIS WILL NOT WORK.

    You will need ISuhax306.7z, which is attached in this post.

    Do this at your own risk. We are not responsible for any adverse effects that you may cause by attempting these methods.

    ### This is based on the idea that SuperOneClick is useful to make is03break stable. Thank you reporters. ###

    1. prepare (on PC)
    adb push data_local /data/local/
    adb shell chmod 755 /data/local/is03break
    adb shell chmod 755 /data/local/psneuter
    adb shell chmod 755 /data/local/busybox
    adb shell chmod 755 /data/local/lcd_density
    adb shell chmod 755 /data/local/market.sh
    adb shell chmod 755 /data/local/autoexec.sh
    adb shell chmod 755 /data/local/exploit.sh
    adb shell chmod 755 /data/local/finalize.sh
    adb shell chmod 755 /data/local/pu
    adb shell chmod 755 /data/local/pu.sh
    adb shell chmod 755 /data/local/prepare_busybox.sh
    adb shell chmod 755 /data/local/reboot
    adb shell /data/local/prepare_busybox.sh
    adb shell rm /data/local/prepare_busybox.sh
    adb shell mkdir /data/local/tmp
    adb shell chmod 777 /data/local/tmp

    2. prepare su (on PC)
    [3.0]
    adb push su/30efgh/su /data/local
    adb install ISuhax306.apk
    [2.3.6.3]
    adb push su/23efgh/su /data/local
    adb install ISuhax2363.apk

    3. exploit (on IS03)
    $ /data/local/exploit.sh

    ---alternatively, on PC---
    adb shell rm /data/local/tmp/sh
    adb shell rm /data/local/tmp/boomsh
    adb shell /data/local/psneuter
    adb shell /data/local/psneuter
    adb shell /data/local/is03break
    ---

    4. finalize (on IS03)
    $ /data/local/tmp/sh
    # /data/local/finalize.sh

    ---alternatively, on PC---
    adb shell
    $ /data/local/tmp/sh
    # cat /data/local/local.prop > /data/local.prop
    ---

    5. reboot

    6. utilize root
    adb shell rm /data/local/psneuter
    adb shell rm /data/local/is03break
    adb shell rm /data/local/exploit.sh
    adb shell rm /data/local/finalize.sh
    adb shell
    $ au
    # cd /data
    # ln -s local root
    # chmod 777 local #sed requires directory write permission to change lcd_density.

    * ISTweak - toggle /sbin/su http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=single&lid=19&cid=3
    * jackpal.androidterm - Terminal
    * revised busybox with wget: http://www.mediafire.com/?495qvu33lj6l8 see busybox.7z (use /data/local/prepare_busyboxciel.sh)
    1
    IS03 ADB Drivers

    Well, strangely enough, the IS03 drivers wouldn't install for me, but these would:

    sh-dev.sharp.co.jp/android/modules/driver/index.php?/003sh/download

    (forum wouldn't let me post the link...)

    When I have my phone plugged in and I have an emulator running, I get this:

    List of devices attached
    SSHEV080667 device
    emulator-5554 device

    I'm assuming the SSHEV device is my IS03, and the other is obvious...

    I haven't gotten to much farther than this, but I thought I'd share...The drivers specific for the IS03 Win 7 64bit at this address:

    k-tai.sharp.co.jp/support/a/is03/download/usb/index.html

    ...they didn't work for me. When trying to install the drivers, they weren't recognized.

    I'll post more when I get a bit farther...
    1
    Yeah you said there is no recovery mode, but some of the output you are showing (the # prompt etc) lead me to believe you had a shell, on the hardware itself, which was of root privilege levels.

    Since you could run command "mount" to remount, that would seem to be the case. So you need to find out a sequence of commands that would let you change/modify something on /system, to use later. I don't know if yaffs actually lets you run in rw mode, but at the very least, you should be able to "dd" in the mtd image (instead of mounting it) and copying it to SD card, and we can mount it on regular unix and see..

    dd if=/dev/block/mtdblock4 of=/path/to/SDcard/image.dump bs=2048

    (Make sure "if=" ie 'input-from' is on mtd, so you don't accidentally overwrite your flash)

    But perhaps we already have a copy/dump of the system yaffs? I've not actually looked
    1
    ISO3 USB Driver and Ashot Screencast

    Hi all. Fellow IS03 user here. I got a couple quick questions I am not a developer but trying to get this program to work will be a useful tool on my android website about app reviews and such. I have tryed talking with the developers no success.

    Here goes. Ashot screen capture software for android it claims it will screen cast your android screen without having to root your phone. If nobody knows about it just google android ashot screen capture or visit the mightypocket website.

    Anyways I follow the instructions but for some reason I cannot get the USB driver to install I have the latest Google USB Folder download but when I try and find it comp says doesn't have the proper files to install driver. Was thinking maybe something being restricted by AU.

    If anyone is up the challenge and might be able to get it to work and explain what I am missing would be appreciated greatly. I have tried running this program on XP, Vista, and Linux Ububtu 10.10 Meerkat with no success.

    Thanks.