Announcement

**followmsi** · 17 March 2017, 22:12

If you have any questions, pls feel free to ask.

**tacotime82** · 18 March 2017, 03:10

Greatly appreciate the info. I will dig into trying to get this installed.

Each time I try to push any recovery.img and then reboot into recovery I get the stock android recovery not TWRP. Odd. Ill keep digging and see what kinda things I can break!!

Thanks for all of your help

**tacotime82** · 18 March 2017, 03:48

Once I have everything setup where can I call a .sh script to be ran after bootup?

I assume init.d somewhere but I am having no luck and Im just too flustered to find it right now. Ive been looking for a while and my hair is being pulled out.

**tacotime82** · 18 March 2017, 07:12

Originally posted by followmsi View Post

If you have any questions, pls feel free to ask.

Ok I do have a few questions on where I am going wrong. .. I sort of have this working. But not auto installing after flashing my custom rom.

Here is what I have found.

1) system.img has to be a ext4 format (already noted previously in this post, but worth mentioning)

In your Update.ZIP_TWRP_RK3229_v161122-4.zip
Under system
in etc
install-recovery2.sh - the line of code

Code:

dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/ff0f0000.rksdmmc/by-name/recovery

Did not work

Code:

dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/30020000.rksdmmc/by-name/recovery

Is the directory we need to write the twrprecovery.img file to.

This also did not work, and I was wondering why.
So after some trial and error I did the following.

1) Whiped the box clean.
2) Flashed my most recent version of my firmware (1.0) with ext4 system.img
3) Unzipped the Update.zip_TWRP_RK3229_v161122-4.zip
4) and entered the following via command line

Code:

adb connect 192.168.0.126     #obviously your ip address of your box
adb root
adb connect 192.168.0.126     #same as above
adb remount
adb shell mkdir /system/twrp
adb push -p twrprecovery.img /system/twrp
adb shell
cd /system/twrp
dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #found it needed to zero fill the recovery partition before new recovery installed
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #write the twrprecovery.img to the recovery partition
exit
adb reboot recovery

And that actually worked. Sweet.

Now I wanted to make it auto install when the rom was flashed after the first boot.

So I have read as much as I can, Looks like the init.rc file in the boot.img needed to be edited.

I unpacked and checked through that file. found where install-recovery.sh was called.
Changed that line to install-recovery2.sh (removing the install-recovery.sh so we wouldn't be fighting ourselves)
Took the install-recovery2.sh from your update.zip and put it in the system.img in the bin folder.

Orriginally this

Code:

#!/system/bin/sh

if [ ! -e /data/twrp.installed ]; then
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/ff0f0000.rksdmmc/by-name/recovery
touch /data/twrp.installed
fi

to this (modified to reflect the changed I found )

Code:

#!/system/bin/sh
if [ ! -e /data/twrp.installed ]; then
dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/30020000.rksdmmc/by-name/recovery
touch /data/twrp.installed
fi

Repacked the rom with new boot.img and system.img again.

and Flashed.

On first boot. Directly to android stock recoverty....

Im officially lost. Its time for bed.

In theory I think its sound. But I'm not sure where to go from here.

Thank you for all of your work getting TWRP Update Zip. Greatly appreciate it. It shows life. But my skills are still new, and Im not sure where I am going wrong.

**followmsi** · 18 March 2017, 10:24

Originally posted by tacotime82 View Post

On first boot. Directly to android stock recoverty....

Im officially lost. Its time for bed.

In theory I think its sound. But I'm not sure where to go from here.

Thank you for all of your work getting TWRP Update Zip. Greatly appreciate it. It shows life. But my skills are still new, and Im not sure where I am going wrong.

Thanks .. Yes .. this value needs to be changed in the install-recovery-2.sh script ..
The old value was still from rk3368 layout.

Have corrected this and uploaded a new version into the RK3229 folder.

You can also "wipe" your recovery first .. like you did ..
dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery

How did you integrate TWRP.img into system.img if you compile the ROM again ?
This should work too .. but you need to integrate the twrp copy into build process.

Do you use the ready compiled images and just modify them and repack ?
It seems here you still have an issue with boot.img.
Need to have proper "KRNL" header ..

System.img is more easy to modify .. just plain ext4.

What about root .. supersu ?
On Rockchip we have to make "system-mode" and not systemless installation, like on "all" other Android 6 systems.

SuperSU system install is using excatcly this service .. install-recovery.sh
and changes the file to ..

Code:

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, that will 
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.

/system/etc/install-recovery-2.sh

Thats why the script is called "install-recovery-2.sh" ...

Have uploaded this file to the RK3229 folder too...
SuperSU-v2.79-201612051815-forced-system-mode.zip

If you keep everything like it is .. and just install Update.ZIP_TWRP_RK3229_v161122-4.zip and SuperSu-forced-system-mode.zip it will work.
Once installed via TWRP, make directly a "dd" of your complete system.img .. from recovery via adb - like you did.

example:

Code:

dd if=/dev/block/mmcblk0p12 of=/sdcard/Download/new.system.img

Then you have a pre-rooted and TWRP included system.img which will work and boot

Keep all your original compiled .img files and just use the new system.img to build a new Update.IMG via rockchips tools.

Maybe this way it's easier ..

As well you can change bootanimatiion or other stuff.. replace libs ... etc. etc .. and just "dd" the complete system partition again - to make a new system.img

Cheers

**tacotime82** · 18 March 2017, 14:34

Please see notes below I added in, best way I could figure to anwer questions and ask new

Originally posted by followmsi View Post

Thanks .. Yes .. this value needs to be changed in the install-recovery-2.sh script ..
The old value was still from rk3368 layout.

# OK great I was grasping at straws im glad I found the right one

Have corrected this and uploaded a new version into the RK3229 folder.

You can also "wipe" your recovery first .. like you did ..
dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery

# I tried it without over ADB and it did not work and retested with a whipe and it did work.

How did you integrate TWRP.img into system.img if you compile the ROM again ?

# Possible communication error on my part (still a newbe) I did not compile the rom, I mounted the system.img
made directory twrp/ in the system.img copyed the twrp.img into that directory
Once all other modifications to the system.img and boot.img I unmounted and used imgrepackerrk to repack everything into a new firmware file.

This should work too .. but you need to integrate the twrp copy into build process.

# I do not understand this line (hopefully it was resolved by my above note.

Do you use the ready compiled images and just modify them and repack ? # Your right I did not compile my own. I modified the ones and repacked. My error in wording.
It seems here you still have an issue with boot.img.
Need to have proper "KRNL" header ..

# Ok here is where you've got me at a disadvantage. I know at this point verry little about KRNL header's (or modifying boot.img
here is what I did to modify the init.rc file in the boot.img
1) used imgrepackerrk to unpack known working custom firmware 1.0 (the version that I can get TWRP to work fully on)
2) Pulled the boot.img file from that output.dump
3)used imgrepackerrk to un pack the boot image resulting in a :
boot.img.dump foler and a boot.img.cfg file
under boot.img.dump folder
a ramdisk.dump and a second.dump and a kernel file (never noticed that before writing this)
I modified the init.rc file the way I mentioned removing the install-recovery.sh changing to install-recovery2.sh (now seeing that that is wrong)
After all modifications I used imgrepackerrk to repack ramdisk.cfg and then second.cfg. then boot.img.cfg
resulting with a new boot.img with the modification to the init.rc file I previously wanted.

System.img is more easy to modify .. just plain ext4.

# Yes easily modified with a sudo mount system.img (mount point)
direct your terminal over there and make the changes you wish.

What about root .. supersu ?
On Rockchip we have to make "system-mode" and not systemless installation, like on "all" other Android 6 systems.

# I unfortunatly donot understand all of this at this point. and from here out I think I have an Idea of how to proceed with the
information below. I will edit this if I have any further questions and will hopefully post results soon

SuperSU system install is using excatcly this service .. install-recovery.sh
and changes the file to ..

Code:

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.

/system/etc/install-recovery-2.sh

Thats why the script is called "install-recovery-2.sh" ...

Have uploaded this file to the RK3229 folder too...
SuperSU-v2.79-201612051815-forced-system-mode.zip

If you keep everything like it is .. and just install Update.ZIP_TWRP_RK3229_v161122-4.zip and SuperSu-forced-system-mode.zip it will work.
Once installed via TWRP, make directly a "dd" of your complete system.img .. from recovery via adb - like you did.

example:

Code:

dd if=/dev/block/mmcblk0p12 of=/sdcard/Download/new.system.img

Then you have a pre-rooted and TWRP included system.img which will work and boot

Keep all your original compiled .img files and just use the new system.img to build a new Update.IMG via rockchips tools.

Maybe this way it's easier ..

As well you can change bootanimatiion or other stuff.. replace libs ... etc. etc .. and just "dd" the complete system partition again - to make a new system.img

Cheers

**tacotime82** · 18 March 2017, 15:50

Originally posted by followmsi View Post

Have uploaded this file to the RK3229 folder too...
SuperSU-v2.79-201612051815-forced-system-mode.zip

If you keep everything like it is .. and just install Update.ZIP_TWRP_RK3229_v161122-4.zip and SuperSu-forced-system-mode.zip it will work.
Once installed via TWRP, make directly a "dd" of your complete system.img .. from recovery via adb - like you did.

example:

Code:

dd if=/dev/block/mmcblk0p12 of=/sdcard/Download/new.system.img

Then you have a pre-rooted and TWRP included system.img which will work and boot

Keep all your original compiled .img files and just use the new system.img to build a new Update.IMG via rockchips tools.

Maybe this way it's easier ..

As well you can change bootanimatiion or other stuff.. replace libs ... etc. etc .. and just "dd" the complete system partition again - to make a new system.img

Cheers

So I did another clean flash of my 1.0 working custom firmware with a ext4 system.img
Installed TWRP manually by this process

Code:

 
 adb connect 192.168.0.126     #obviously your ip address of your box adb root adb connect 192.168.0.126     #same as above adb remount adb shell mkdir /system/twrp adb push -p twrprecovery.img /system/twrp adb shell cd /system/twrp dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #found it needed to zero fill the recovery partition before new recovery installed dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #write the twrprecovery.img to the recovery partition

I then copied the
SuperSU-v2.79-201612051815-forced-system-mode.zip
and
Update.ZIP_TWRP_RK3229_v161122-4.zip (fresh download and confirmed the /dev/block/platform/30020000.rksdmmc/by-name/recovery change was made)
To the /sdcard/Download

rebooted into TWRP recovery (still so awesome that this is actually working, Happy every time I see it)

Select Install
navigate to /sdcard/Download
and attempt to flash Update.zip ** OR ** SuperSU.zip
and both fail
"Failed to mount '/internal_sd' (invalid argument)"
(I wish I knew how to pull recovery log files for you but I havent the foggiest idea)

So stumped yet again.

**followmsi** · 18 March 2017, 16:43

They have installed correctly .. Pls check again .. Do you understand the message "Failed to mount '/internal_sd' (invalid argument)" ... Do you have android 6 ? .. You have adopted storage in L.

**followmsi** · 18 March 2017, 16:46

Originally posted by tacotime82

So I did another clean flash of my 1.0 working custom firmware with a ext4 system.img
Installed TWRP manually by this process

Code:

 
 adb connect 192.168.0.126     #obviously your ip address of your box adb root adb connect 192.168.0.126     #same as above adb remount adb shell mkdir /system/twrp adb push -p twrprecovery.img /system/twrp adb shell cd /system/twrp dd bs=1024 if=/dev/zero of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #found it needed to zero fill the recovery partition before new recovery installed dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/30020000.rksdmmc/by-name/recovery     #write the twrprecovery.img to the recovery partition

I then copied the
SuperSU-v2.79-201612051815-forced-system-mode.zip
and
Update.ZIP_TWRP_RK3229_v161122-4.zip (fresh download and confirmed the /dev/block/platform/30020000.rksdmmc/by-name/recovery change was made)
To the /sdcard/Download

rebooted into TWRP recovery (still so awesome that this is actually working, Happy every time I see it)

Select Install
navigate to /sdcard/Download
and attempt to flash Update.zip ** OR ** SuperSU.zip
and both fail
"Failed to mount '/internal_sd' (invalid argument)"
(I wish I knew how to pull recovery log files for you but I havent the foggiest idea)

So stumped yet again.

After installation . check your system partition for the twrp folder ..
And you will see the install-recovery-2.sh.

"Failed to mount '/internal_sd' (invalid argument)"
We can not mount internal-sd if there is no internal-sd anymore.
The twrp is for old lollipop too ..
And dual images .. Etc.

**tacotime82** · 18 March 2017, 16:59

I wanted to make this a little easier on myself to keep trying to get this right so I made a Linux shell script to install the twrp image into my firmware after it is flashed. I thought others might find it usefull. All credit and thanks should goto followmsi if this works for you. It has worked for me.

at

Error 404 (Not Found)!!1

https://drive.google.com/open?id=0BwSfaTJJD6K3cXRIWmJYTEZieVE

you will find a TWRP-install-script.zip
Simply download on linux
Unzip
run ./install.sh -i 0.0.0.0 # your ipaddress not 0.0.0.0

I made this file by researching how to program sh files and looking through examples of adb being used in sh files. Its a compilation of numerous sh files. Please no credit to me.

**tacotime82** · 18 March 2017, 17:21

Originally posted by followmsi View Post

After installation . check your system partition for the twrp folder ..
And you will see the install-recovery-2.sh.

"Failed to mount '/internal_sd' (invalid argument)"
We can not mount internal-sd if there is no internal-sd anymore.
The twrp is for old lollipop too ..
And dual images .. Etc.

After what installation Im confused.

In order to manually get TWRP installed I extracted the twrprecoverty.img from inside Update.ZIP_TWRP_RK3229_v161122-4.zip/system/twrp/ and manually pushed it to the box and preformed the dd commands listed above via adb witht the system booted into android.

So there is no install-recovery-2.sh

Once in the TWRP recovery

I attempted to flash either of the zips SuperSU-v2.79-201612051815-forced-system-mode.zip or Update.ZIP_TWRP_RK3229_v161122-4.zip
And it never flashed due to the "Failed to mount '/internal_sd' (invalid argument)" error.

Thanks for all of your help and hard work.

**followmsi** · 18 March 2017, 18:19

Originally posted by tacotime82

After what installation Im confused.

In order to manually get TWRP installed I extracted the twrprecoverty.img from inside Update.ZIP_TWRP_RK3229_v161122-4.zip/system/twrp/ and manually pushed it to the box and preformed the dd commands listed above via adb witht the system booted into android.

So there is no install-recovery-2.sh

Once in the TWRP recovery

I attempted to flash either of the zips SuperSU-v2.79-201612051815-forced-system-mode.zip or Update.ZIP_TWRP_RK3229_v161122-4.zip
And it never flashed due to the "Failed to mount '/internal_sd' (invalid argument)" error.

Thanks for all of your help and hard work.

It's in the etc folder... Install-recovery.sh

"Failed to mount '/internal_sd' (invalid argument)" error.
Explained a few times .. it's no error message for you.
Do you have internal-sd in your ROM at all ?

Pls see the TWRP output exactly .. and check system disk for the files.

All the needed files are in your system.img .. now make "dd" and your are done.

Cheers

**tacotime82** · 18 March 2017, 21:48

Originally posted by followmsi View Post

It's in the etc folder... Install-recovery.sh

"Failed to mount '/internal_sd' (invalid argument)" error.
Explained a few times .. it's no error message for you.
Do you have internal-sd in your ROM at all ?

Pls see the TWRP output exactly .. and check system disk for the files.

All the needed files are in your system.img .. now make "dd" and your are done.

Cheers

Oh I see what you are saying. I will give that a shot.

**followmsi** · 18 March 2017, 22:04

Originally posted by tacotime82 View Post

Oh I see what you are saying. I will give that a shot.

Cool .. I hope you will manage it now.

And as I compiled the new TWRP 3.1.0 version for RK3368 (64Bit) a few hours agon .. I made a second compilation for RK3229 (32Bit)

TWRP_RK3229_3.1.0-0_170318.img -> to be installed via flashify .. etc.

Update.ZIP_TWRP_RK3229_3.1.0-0_170318.zip -> to be installed via TWRP.

Download: https://drive.google.com/drive/folde...3JQa1hmSEJOLVk

As well I have removed the internal_sd from fstab .. no more "error" messages

Pls test and enjoy

**tacotime82** · 19 March 2017, 01:12

Originally posted by followmsi View Post

If you keep everything like it is .. and just install Update.ZIP_TWRP_RK3229_v161122-4.zip and SuperSu-forced-system-mode.zip it will work.
Once installed via TWRP, make directly a "dd" of your complete system.img .. from recovery via adb - like you did.

example:

Code:

dd if=/dev/block/mmcblk0p12 of=/sdcard/Download/new.system.img

Then you have a pre-rooted and TWRP included system.img which will work and boot

Note for later use. According to recovery log copied durring test correct dd command

Code:

dd if=/dev/block/mmcblk0p14 of=/sdcard/Download/new.system.img

Announcement

Announcement

TRWP. 3229 Devices Followmsi.

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On