[TOOL][LB] Recovery Installer [WIN/LINUX/MAC]

[Rohit@91]

Yeah!! Same problem here!

 

[Gabboxxx]

I dont kbow if i Only me or is a bug, when i go down or up the screen go left to rigth, and if i install something, this not apear, o.o
Thanks

Sent from my C2104 using XDA Premium 4 mobile app

 

[dywerd]

some report...

Hi!
After some hour of use:
-if I flash something, its not there
-I can make a backup, but can't restore it
-the only way to reboot is that wipe cache and dalvik cache, after that i have to confirm to flash or not flash the stock recovery about two
-when wipe dalvik cache the recovery says: E:unknown wolume for path [/sd-ext]
-I cant mount system, cache, and when want to flash something it someimes says that can't mount system partition (I think thats the problem why we can't see anything that flashed)
There is nothing else I find yet, but when I will, I will report back!
Hope there will be some solution!
Keep up the good work!!
We have recovery!!!

 

[Mrcl1450]

CWM for Locked Bootloaders!!! Thanks, you just made my day :victory:

 

[Deleted member 4736004]

Hi!
After some hour of use:
-if I flash something, its not there
-I can make a backup, but can't restore it
-the only way to reboot is that wipe cache and dalvik cache, after that i have to confirm to flash or not flash the stock recovery about two
-when wipe dalvik cache the recovery says: E:unknown wolume for path [/sd-ext]
-I cant mount system, cache, and when want to flash something it someimes says that can't mount system partition (I think thats the problem why we can't see anything that flashed)
There is nothing else I find yet, but when I will, I will report back!
Hope there will be some solution!
Keep up the good work!!
We have recovery!!!

hi,
I've noticed this too.
/system can't be mounted [It's mounted ro instead of rw]
This is why you can make backup but can't restore it [writing /system fails]
I'm looking into it. This could be due to ric service started in init.target.rc
but thats unlikely because install-recovery.sh in init.rc reboots the device. After reboot we run init.recovery.rc which executes the patched sa77_recovery binary in system/bin. So init.target.rc isn't started second time (possibly)
However, I've noticed this :

#init.recovery.rc

on early-init
    start ueventd

on init
#/* [SA77] S Bruce_Chen Bug#291 recovery mode shall be mount system (except FOTA) */
    export PATH /sbin:/system/bin
#/* [SA77] E Bruce_Chen Bug#291 recovery mode shall be mount system (except FOTA) */
    export ANDROID_ROOT /system
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard

    symlink /system/etc /etc

    mkdir /sdcard
    mkdir /system
    mkdir /data
    mkdir /cache
    mkdir /tmp
    mount /tmp /tmp tmpfs

    chown root shell /tmp
    chmod 0775 /tmp

    [COLOR="Red"]mount ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system ro barrier=1 wait[/COLOR]
[COLOR="Blue"]#WHY?
[/COLOR]
    write /sys/class/android_usb/android0/enable 0
    write /sys/class/android_usb/android0/idVendor 05C6
    write /sys/class/android_usb/android0/idProduct 9025
    write /sys/class/android_usb/android0/f_diag/clients diag
    write /sys/class/android_usb/android0/functions diag,adb
    write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
    write /sys/class/android_usb/android0/iProduct ${ro.product.model}
    write /sys/class/android_usb/android0/iSerial ${ro.serialno}
    write /sys/class/android_usb/android0/enable 1
    start adbd

on boot

    ifup lo
    hostname localhost
    domainname localdomain

    class_start default

service ueventd /sbin/ueventd
    critical

[COLOR="SeaGreen"]service recovery /system/bin/sa77_recovery[/COLOR]
[COLOR="Blue"]#Recovery loads from here
[/COLOR]
service adbd /sbin/adbd
    disabled


# Restart adbd so it can run as root
on property:service.adb.root=1
    write /sys/class/android_usb/android0/enable 0
    restart adbd
    write /sys/class/android_usb/android0/enable 1

@[NUT]can you look into this?

EDIT: Guys. I won't be available until late march due to unavailability of both phone and laptop.
However, I've asked some other guys to contribute to the source.

 

[dywerd]

Thanks for your work!
Take your time! If I can help you anyway just let me know ! I will test when you ready!!

 

[varun.chitre15]

Hi!
After some hour of use:
-if I flash something, its not there
-I can make a backup, but can't restore it
-the only way to reboot is that wipe cache and dalvik cache, after that i have to confirm to flash or not flash the stock recovery about two
-when wipe dalvik cache the recovery says: E:unknown wolume for path [/sd-ext]
-I cant mount system, cache, and when want to flash something it someimes says that can't mount system partition (I think thats the problem why we can't see anything that flashed)
There is nothing else I find yet, but when I will, I will report back!
Hope there will be some solution!
Keep up the good work!!
We have recovery!!!

Can you post log files from /cache/recovery folder?

hi,
I've noticed this too.
/system can't be mounted [It's mounted ro instead of rw]
This is why you can make backup but can't restore it [writing /system fails]
I'm looking into it. This could be due to ric service started in init.target.rc
but thats unlikely because install-recovery.sh in init.rc reboots the device. After reboot we run init.recovery.rc which executes the patched sa77_recovery binary in system/bin. So init.target.rc isn't started second time (possibly)
However, I've noticed this :

#init.recovery.rc

on early-init
    start ueventd

on init
#/* [SA77] S Bruce_Chen Bug#291 recovery mode shall be mount system (except FOTA) */
    export PATH /sbin:/system/bin
#/* [SA77] E Bruce_Chen Bug#291 recovery mode shall be mount system (except FOTA) */
    export ANDROID_ROOT /system
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard

    symlink /system/etc /etc

    mkdir /sdcard
    mkdir /system
    mkdir /data
    mkdir /cache
    mkdir /tmp
    mount /tmp /tmp tmpfs

    chown root shell /tmp
    chmod 0775 /tmp

    [COLOR="Red"]mount ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system ro barrier=1 wait[/COLOR]
[COLOR="Blue"]#WHY?
[/COLOR]
    write /sys/class/android_usb/android0/enable 0
    write /sys/class/android_usb/android0/idVendor 05C6
    write /sys/class/android_usb/android0/idProduct 9025
    write /sys/class/android_usb/android0/f_diag/clients diag
    write /sys/class/android_usb/android0/functions diag,adb
    write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
    write /sys/class/android_usb/android0/iProduct ${ro.product.model}
    write /sys/class/android_usb/android0/iSerial ${ro.serialno}
    write /sys/class/android_usb/android0/enable 1
    start adbd

on boot

    ifup lo
    hostname localhost
    domainname localdomain

    class_start default

service ueventd /sbin/ueventd
    critical

[COLOR="SeaGreen"]service recovery /system/bin/sa77_recovery[/COLOR]
[COLOR="Blue"]#Recovery loads from here
[/COLOR]
service adbd /sbin/adbd
    disabled


# Restart adbd so it can run as root
on property:service.adb.root=1
    write /sys/class/android_usb/android0/enable 0
    restart adbd
    write /sys/class/android_usb/android0/enable 1

I think this can be probably solved by mounting the complete block world writable just within the recovery binary but I am not sure.
I wonder how the stock sa77 recovery works with read only system partition. Sony's recovery binary might be mounting the complete block as world writable. If it is so, I can replicate it within CWM as well. I just need the logs.

Sent from my C2104 using Tapatalk

 

[dywerd]

Can you post log files from /cache/recovery folder?

I have to reflash the rom because some problem in the flash process ,but will try another and make a log but don't know how, 'cause didn't make one or another yet

 

[varun.chitre15]

I have to reflash the rom because some problem in the flash process ,but will try another and make a log but don't know how, 'cause didn't make one or another yet

You don't need to follow any extra procedure. Just try flashing that same zip which doesn't work and upload all files under /cache/recovery


Sent from my C2104 using Tapatalk

 

[dywerd]

@varun.chitre15

So there it is!
I try to install "Xperia Tablet S Keyboard port For any device by ThilinaC", but no succes
after install, in recovery/advanced menu - show log:
" I:Can't partition non-vfat: auto
I:Can't format unknown volume: /emmc"
say that... if its help....

 

[varun.chitre15]

@varun.chitre15

So there it is!
I try to install "Xperia Tablet S Keyboard port For any device by ThilinaC", but no succes
after install, in recovery/advanced menu - show log:
" I:Can't partition non-vfat: auto
I:Can't format unknown volume: /emmc"
say that... if its help....

Ok now do this
In CWM go to mounts and storage section
And select mount /system option and post another log.

Sent from my C2104 using Tapatalk

 

[dywerd]

@varun.chitre15

it was on unmount /system
and says: error unmounting /system! when I press on it...

 

[SlikToxic]

@varun.chitre15

it was on unmount /system
and says: error unmounting /system! when I press on it...

I got the same problem too, that's maybe why we can flash anything?

 

[[NUT]]

Hey, that's genius, nice work @Rachit Rawat

Anyone with this installed, could you try to connect your usb cable and run adb shell when in recovery?

If you can, type 'mount' or if that does not work, 'cat /proc/mounts' and copy and paste the output here.

Chances are you need the flashtool drivers installed for this to work.

 

[dywerd]

@Nut
Hi! I hope I do it right or this can help! I have to install adb driver manually when my phone in that cwm. After that on windows run adb shell and write in "mount" and "cat /proc/mounts", working that two, and the log attached...
If I can help somehow, let me know
Good luck!

 

[[NUT]]

@Nut
Hi! I hope I do it right or this can help! I have to install adb driver manually when my phone in that cwm. After that on windows run adb shell and write in "mount" and "cat /proc/mounts", working that two, and the log attached...
If I can help somehow, let me know
Good luck!

Thanks, that confirms my suspicion: in adb shell, type 'umount /system' and post the result here.

 

[dywerd]

Thanks, that confirms my suspicion: in adb shell, type 'umount /system' and post the result here.

Ther it is...
I was not sure that you type incorrect or thats the code (umount), so I type in two other ways... hope you understand... :angel:

 

[[NUT]]

Ther it is...
I was not sure that you type incorrect or thats the code (umount), so I type in two other ways... hope you understand... :angel:

I do, but i know my linux/android commands, so don't worry

Can you please execute the following and report the findings:

'mount -o remount,rw /system'

and

'busybox lsof'

And again, put them here

You are doing a great job dude, thanks for helping out :good:

 

[dywerd]

I do, but i know my linux/android commands, so don't worry

Can you please execute the following and report the findings:

'mount -o remount,rw /system'

and

'busybox lsof'

And again, put them here

You are doing a great job dude, thanks for helping out :good:

So there it is...
I know you are not "launchie" (from Ender's Game ), its me who don't know about these commands
Anyway I'm glad to help :victory:

 

[[NUT]]

So there it is...
I know you are not "launchie" (from Ender's Game ), its me who don't know about these commands
Anyway I'm glad to help :victory:

Ooh wow, that's both good and bad news...

Can you try the remount command again and then type 'mount' after it and provide me the log again?