[RECOVERY] xRecovery 0.3 | Fixed Mass Storage mounting | 31/07/2011

Search This thread

DaRk_dOg

Senior Member
Oct 2, 2010
918
2,042
A question:

By changing /dev/block/mtdblock2 with /dev/block/mtdblock0 for system and

/dev/block/mtdblock0 with /dev/block/mtdblock3, in your scripts, will it work on mini/mini pro, or my phone will turn to a flaming firework? :D

Thank you in advance for your reply sir.

D_d
 

indianl

Senior Member
Oct 8, 2009
95
18
Run into this problem too, no matter if I use terminal, via ADB shell or via gscript :(
Code:
mkdir failed for /data/local/tmp/xrecovery, File exists
mount: Device or resource busy
rm failed for -rf, No such file or directory
cp: write error: No space left on device

edit: solved by starting the shell script via Root Explorer!
 
Last edited:

iridaki

Retired Forum Moderator
Feb 21, 2007
4,532
5,190
37
Edinburgh, Scotland
Run into this problem too, no matter if I use terminal, via ADB shell or via gscript :(
Code:
mkdir failed for /data/local/tmp/xrecovery, File exists
mount: Device or resource busy
rm failed for -rf, No such file or directory
cp: write error: No space left on device

edit: solved by starting the shell script via Root Explorer!
That worked for me too!
Thank you! :)
 

zdzihu

Retired Recognized Developer
Sep 28, 2008
651
5,141
A question:

By changing /dev/block/mtdblock2 with /dev/block/mtdblock0 for system and

/dev/block/mtdblock0 with /dev/block/mtdblock3, in your scripts, will it work on mini/mini pro, or my phone will turn to a flaming firework? :D

Thank you in advance for your reply sir.

D_d
Actually it *might* work fine... recovery auto-detects partitions, so you only need to adjust /system and /appslog paths in chargemon and installation script!


As for installation, the best thing would be to write a simple app which would replace .sh script (copy 2 files into /system and 1 into /appslog). Unfortunately I hate java so much that I won't even try :D Anyone interested in helping?


Cheers!
 
Last edited:

DaRk_dOg

Senior Member
Oct 2, 2010
918
2,042
Actually it *might* work fine... recovery auto-detects partitions, so you only need to adjust /system and /appslog paths in chargemon and installation script!


As for installation, the best thing would be to write a simple app which would replace .sh script (copy 2 files into /system and 1 into /appslog). Unfortunately I hate java so much that I won't even try :D Anyone interested in helping?


Cheers!

Thanx for your quick reply sir.

I'll try it as soon as i get home from work.
 

zdzihu

Retired Recognized Developer
Sep 28, 2008
651
5,141
Thanx for your quick reply sir.

I'll try it as soon as i get home from work.
I just did it. Now I need some brave owners to try it out.

The file is shared between X10 mini and X8. The installation process is exactly the same.

IT'S NOT FOR X10 MINI PRO!

IT IS NOT TESTED! I CANNOT TEST IT MYSELF! IT MAY WIPE OR DAMAGE YOUR DEVICE!
Let me know if it works.

xrecovery-0.0.1-beta-mini-X8.tar.bz2
 
Last edited:

Azdar

Member
Jan 23, 2009
20
1
Paris

I just did it. Now I need some brave owners to try it out.

Hello !

Thanks a lot for your job ! I tried it two minutes ago and it worked fine !
I used "Easy Setup" with GScript Lite.
Do you want me to try something more particular ?

I will finish this message with a famous sentence ... Sorry for my bad English ! =D
 

zdzihu

Retired Recognized Developer
Sep 28, 2008
651
5,141
Hello !

Thanks a lot for your job ! I tried it two minutes ago and it worked fine !
I used "Easy Setup" with GScript Lite.
Do you want me to try something more particular ?

I will finish this message with a famous sentence ... Sorry for my bad English ! =D
Hi there, which phone was that? :)

Cheers!
 

rmourar

Senior Member
Aug 19, 2010
313
44
40
São Paulo, SP
Hey Z, I've had the same problem of some other people:

mkdir failed for /data/local/tmp/xrecovery, File exists
mount: Device or resource busy
rm failed for -rf, No such file or directory
cp: write error: No space left on device

then I've ran it from root explorer like it was suggested and it worked, but when I open the recovery menu it shows in the middle of the screen "E:Can't open /tmp/recovery.log
and it seems that I can't make backups, I click in backup and it shows
sd card space free 3221MB
Backing up system...

and it just goes back to the recovery menu...
 

crecsky

Senior Member
Nov 17, 2009
169
12
Calgary
It's basically like starting up your phone and going in the back door and not running your software right away.

It makes you able to flash custom roms as well as backup your own.

Edit: I'll shortly be posting a nandrecovery of a stock rogers rom.
 
Last edited:

Azdar

Member
Jan 23, 2009
20
1
Paris
Hey Z, I've had the same problem of some other people:

mkdir failed for /data/local/tmp/xrecovery, File exists
mount: Device or resource busy
rm failed for -rf, No such file or directory
cp: write error: No space left on device

then I've ran it from root explorer like it was suggested and it worked, but when I open the recovery menu it shows in the middle of the screen "E:Can't open /tmp/recovery.log
and it seems that I can't make backups, I click in backup and it shows
sd card space free 3221MB
Backing up system...

and it just goes back to the recovery menu...

Did you try even to access to the recovery ?
 

Hypercore

Senior Member
Apr 16, 2009
504
49
Vancouver
So basically what you're saying is we now have access to flashing custom ROM's like stock Android 2.2 (Not the AOSP)?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 237
    This is a custom recovery for Xperia X10 based on ClockworkMod recovery source.
    Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!


    rec1s.png
    rec2d.png


    How?
    Press BACK button few times right after white SE label appears.


    Controls:
    Use VOLUME-UP and VOLUME-DOWN to browse, HOME to select, BACK to go back.


    Features:

    • ADB root shell
    • Reboot
    • Install update.zip from SD Card
    • Factory reset (full wipe)
    • Wipe cache partition
    • Install custom zip
    • Backup and Restore
    • Partition tools
      • Mount/unmount partitions
      • Format partitions
      • Mount as USB Storage
    • Advanced options
      • Wipe Dalvik cache
      • Wipe battery stats
      • Fix permissions for apps (FC fix)

    Installation:

    A: Install the zip package via your current recovery

    9131112.jpg


    1. boot into recovery
    2. connect with adb (adb shell)
    3.
    Code:
    rm -r /sdcard
    mkdir sdcard
    chmod 777 sdcard
    4. Now you will be able to see your SD Card and install fixed xRecovery

    or

    B: unpack all of the files to the relevant folders on your mobile

    or

    C: ask your ROM provider to include it :)


    I am not responsible for any damage this software may cause to your phone.
    Use it at your own risk!


    Requirements:
    1. 2.3 STOCK ROM
    2. Phone must be rooted

    3. Busybox from the market installed


    Changelog:
    0.3-release-GB: fixed Mass Storage mounting issues
    0.3-release-GB: fixed SD Card mounting issues
    0.3-release: unified version for all X10 variants and partition layouts
    0.2-release: fixed installation issues for those with trashed mtd0 partition
    0.1-release: xRecovery installer app - thanks zoz33!
    0.0.1-beta: Initial release (for testers)


    Download:

    For now please use xRecovery 0.3: xRecovery_0.3_GBready.zip


    snapshot_13-01-2011_xRecovery.tar.bz2 - source code
    38
    Q&A:

    Q: How to use "boot custom ROM/kernel" option?
    A: this is designed for ROM developers. This option executes a custom script (/system/kernel/boot.sh), which may be used for multiple puproses like:
    - boot custom kernel
    - boot custom ROM from SD Card
    - dual-boot
    - etc

    Q: can you give an example?
    A: Sure. Here's the simple boot.sh script to boot the custom kernel:
    Code:
    #!/sbin/sh
    # zdzihu: boot custom kernel
    
    insmod /system/kernel/splboot.ko
    sync
    cat /system/kernel/miniloader > /proc/splboot/image
    cat /system/kernel/boot.img > /proc/splboot/boot_img
    sleep 3
    echo > /proc/splboot/boot

    Q: What's edify scripting?
    A: http://xdaforums.com/showthread.php?t=936175

    Q: Will it work with X8/X10mini/X100/T1000?
    A: Yes and no. Yes, because it's compiled in compatibility mode (armv6).
    But not this particular release. The init files must be changed by X8/X10mini/X100/T1000 devs first. Please check in the relevant threads.
    14
    xRecovery 1.0.0 released.

    New features:

    - shutdown option
    - custom boot
    - updated recovery-script
    - working regardless of busybox version
    - many more :)


    Cheers,
    z
    8
    New version released, please check 1st post again.

    Cheers,
    z

    LOL, So you couldn't wait till I posted it on this thread at least :0P
    6
    @z, can you please upload v1.0 sources, so we mini pro users, can mod it to fit our devices, thanks.
    Soon. At the moment I'm working on integrating update-binary into recovery - without it update.zip might either not flash or damage /system partition. Let's say it's a critical update :)

    Cheers,
    z