[REQ] Reboot into custom recovery (bootmenu) - Defy Android Development

Hi, i am MIUI Spain ROM coocker from http://miuis.es and i want to know how to ( which commands) reboot directly into custom recovery in miui or cm7 with bootmenu, i want to know it to implement it in our OTA updater( which reboots into stock recovery by default).
thanks.

I think you should ask Epsylon3, he's working on this stuff.
Sent from my MB525 using XDA App

bihariel said:
Hi, i am MIUI Spain ROM coocker from http://miuis.es and i want to know how to ( which commands) reboot directly into custom recovery in miui or cm7 with bootmenu, i want to know it to implement it in our OTA updater( which reboots into stock recovery by default).
thanks.
Click to expand...
Click to collapse
i think you just have to play a bit with "/system/bootmenu/config/default_bootmode.conf"
maybe it's possible to create a new folder for cwm init
all sources are available to see

Yeah i think it must be possible. Obviously it is possible to auto boot the boot menu every time so just need something to automatically load the CWM after this...

ephumuris said:
Yeah i think it must be possible. Obviously it is possible to auto boot the boot menu every time so just need something to automatically load the CWM after this...
Click to expand...
Click to collapse
that´s the point, but how to load automaticlly the cwm.

The first Nandroid for Defy was possible through any special restart-commands(I don't know which).
Maybe the developer can change the bootmenu so it checks for this so you don't have to change the bootmode.

v0.9.5 have now this feature...
need to write "recovery" in bootmenu/config/bootmode.conf
will be in next nightly
manually selected bootmode (in bootmenu) will stay in default_bootmode.conf (for next reboot)

Epsylon3 said:
v0.9.4 have now this feature...
need to write "recovery" in bootmenu/config/default_bootmode.conf
will be in next nightly
hmm no... will make a new 0.9.5 which use a new file "bootmode.conf" to keep old selected bootmode in default_bootmode.conf
Click to expand...
Click to collapse
Thanks man, i wait for it. just to clarify , i use an ota updater and i want it to flash automaticlly the patches.

available in cm7-110708-1933-NIGHTLY-Jordan.zip and newer builds
need to write "recovery" in bootmenu/config/bootmode.conf
NOT in default_bootmode.conf

Epsylon3 said:
available in cm7-110708-1933-NIGHTLY-Jordan.zip and newer builds
need to write "recovery" in bootmenu/config/bootmode.conf
NOT in default_bootmode.conf
Click to expand...
Click to collapse
ok thanks, but i tried to port it to miui, and not boots, after the blue led it reboots.

keep your 2nd-init binary, this file is dependent of the kernel version
in nightly builds i make a backup of it since i dont upgrade kernel.... unlike miui which force kernel "downgrade" to 343-11

Epsylon3 said:
keep your 2nd-init binary, this file is dependent of the kernel version
in nightly builds i make a backup of it since i dont upgrade kernel.... unlike miui which force kernel "downgrade" to 343-11
Click to expand...
Click to collapse
well i managed to port it and got my updater work but when it goes flashing.
the recovery log says this:
Starting recovery on Fri Jul 8 20:44:27 2011
can't open /dev/tty0: No such device or address
framebuffer: fd 4 (480 x 854)
ClockworkMod Recovery v4.0.0.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk1p15 (null)
2 /cache ext3 /dev/block/mmcblk1p24 (null)
3 /data ext3 /dev/block/mmcblk1p25 (null)
4 /system ext3 /dev/block/mmcblk1p21 (null)
5 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
6 /sd-ext /dev/block/mmcblk0 /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Got arguments from /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery_stable" "--update_package=/sdcard/download/signed_Swype-ultima-version.zip" "boot-recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.usb_mode=normal
ro.bootmode=reboot
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x0000
ro.hardware=jordan_umts
ro.revision=0
Finding update package...
I:Update location: /sdcard/download/signed_Swype-ultima-version.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
but the zip is signed, so what happens, why it says signature failed, when the zip is signed?

signatures (md5) are in META INF folder

Epsylon3 said:
signatures (md5) are in META INF folder
Click to expand...
Click to collapse
yes i know and the zip is signed and has three files in that folder:
CERT.RSA
CERT.SF
MANIFEST.MF

i dunno, never tried that . . check with google apps zip file...

Epsylon3 said:
i dunno, never tried that . . check with google apps zip file...
Click to expand...
Click to collapse
also ggaps not working.
the problem is E:signature verification failed
how can i disable the verificacion signature on config files?

hmm maybe sdcard is not automatically mounted in this case...
try to check with adb feature in advanced menu...

Epsylon3 said:
hmm maybe sdcard is not automatically mounted in this case...
try to check with adb feature in advanced menu...
Click to expand...
Click to collapse
thanks, but what i want is to get the updater to flash automaticlly, without entering in bootmenu.

bihariel said:
thanks, but what i want is to get the updater to flash automaticlly, without entering in bootmenu.
Click to expand...
Click to collapse
yes i know .... and so you cant check ? This feature was implemented yesterday in bootmenu... I cant test all the features... (of recovery this time)

Epsylon3 said:
yes i know .... and so you cant check ? This feature was implemented yesterday in bootmenu... I cant test all the features... (of recovery this time)
Click to expand...
Click to collapse
check what?
what i want is like in rommanager, you chose aplly patch and the phone reboots automaticlly to recovery ( thanks to your bootmenu 0.9.4 i can do it now) but it fails on flashing the signed zip, it gives signature check fail.

Related

Modified RC30 - full version

I've uploaded a new version (v1.2) of the modified RC30 update.
http://rapidshare.com/files/165227766/update_TC4-RC30_full_xda-dev_v1.2.zip
http://android-dls.com/forum/index.php?f=24&t=189&rb_v=viewtopic(see forum post for link to actual file)
You must have the modified recovery image installed before trying to install this.
Install as per usual - copy to sd card, rename to update.zip, reboot, enter recovery mode and hit alt+s.
(here's a guide on how to install in Italian - thanks Deedend!)
The primary new features in this version are
- adb shell now works in recovery mode
- a real su (instead of the setuid copy of sh in the last version)
- lots of new goodies in /system/xbin and /system/modules
Other things that have changed from v1.1
- This version has a kernel compiled by Saurik, with more core stuff "turned on", to support more modules (Specifically, /dev/mem and /dev/kmem are available now)
- new features in init
- support for mounting to loop devices
- move flag for mount
- mknod that can wait for a device
- chdir, chroot, usleep, include, trigger​- Changed the init.rc so that it will include /system/init.rc and /data/init.rc, so you can easily add new startup stuff, without having to rebuild/reflash boot.img
- Changed the boot-up recovery flash to look for a file at /data/recovery.img instead of /system/recovery.img, and also to delete recovery.img after a successful flash
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
- changed the fingerprint back to the official RC30 fingerprint (don't want to let google know you're using a modified build)
- using a newer version of busybox
- moved busybox from /system/bin to /system/xbin
Note: A big thanks to Saurik (the "debian on Android" guy ) for all the changes to init and the kernel, as well as the modules in /system/modules. He also tweaked and recompiled a newer version of busybox. He recently posted his own update that I shamelessly stole this stuff from (with his permission )
It also includes the changes that were made in v1.0 and v1.1. namely
- set ro.secure=0, ro.debugable=1, and persist.service.adb.enable=1 in /default.prop, to enable adb to run as root
- Added the ability to mount to a loop in init
- Mount /system/xbin/xbin.cramfs into /system/xbin in init.rc
- Looks for a recovery image to flash at /data/recovery.img instead of /system/recovery.img, and deletes the recovery image after a successful flash
- added back in the telnetd command from RC29
-----
For those who have installed the stock RC30 update: no, you cannot install this update. You must have a modified recovery image installed to apply the update, and you have to have root access to install a modified recovery image. You can't get root access in stock RC30, so you can't install a modified recovery image, and so you can't install this update.
-----
im gonna try this on my stock rc28... let u know tha good tha bad n tha ugly
JesusFreke said:
.... You should be able to apply it no matter what RC you are on.....
Click to expand...
Click to collapse
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
pramods said:
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
Click to expand...
Click to collapse
No. If you're running stock RC30, and don't have my recovery image installed, you're out of luck, until another root exploit is found.
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ? And So i dont mess up how do i install the modified recovery image correctly ?
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
usmc2k said:
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ?
Click to expand...
Click to collapse
Yes. It is identical to the stock RC30, except for the specific modifications I mentioned.
tritron777 said:
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
Click to expand...
Click to collapse
You have to have the modified recovery tool on your phone, which has the test keys.
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Do I still have to install the modified recovery image or is it included in ur version ?
usmc2k said:
Do I still have to install the modified recovery image or is it included in ur version ?
Click to expand...
Click to collapse
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
JesusFreke said:
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
Click to expand...
Click to collapse
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Thanks so much! It worked perfectly
humble said:
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Click to expand...
Click to collapse
Glad I could be of service . If you want to donate, I would be happily surprised, and much appreciative.
usmc2k said:
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Click to expand...
Click to collapse
Yep . Assuming you have the modified recovery image installed already. If you don't, it will just say something to the effect that it couldn't validate the signature.
JesusFreke said:
Glad I could be of service . If you want to donate, I would by happily surprised, and much appreciative.
Click to expand...
Click to collapse
enjoy my friend, and your welcome
looks like telnetd command didn't survive
jriley60 said:
looks like telnetd command didn't survive
Click to expand...
Click to collapse
Why do you say that?
Code:
# ls /system/bin/t*
ls /system/bin/t*
/system/bin/telnetd
/system/bin/toolbox
/system/bin/top
weird i can't terminal in from the phone anymore.
jriley60 said:
weird i can't terminal in from the phone anymore.
Click to expand...
Click to collapse
You can't run telnetd just by typing it in on the keyboard anymore. You have to open a terminal (terminal emulator, pterminal, or with adb shell), and get root access if needed (su), and then type "telnetd &" (the & at the end tells it to run in the background)

[mod][tool]dual boot for zte blade/modify-tool

Hello guys. This my dual booting project for our amazing ZTE BLADE!
What is this?
>This mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of NAND.
FOR ADVANCED USERS ONLY!!!
I WILL NOT BE RESPONSIBLE FOR ANY BRICKED DEVICES, DAMAGED SDCARDS ETC.
DO IT AT YOUR OWN RISK!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more ROMS like CM10, Paranoidandroid etc.
Downloads:
Cyanogenmod9(KonstaKang)
Boot.img - Download
Updater-script - Download
Cyanogenmod10
Boot.img - Download
Updater-script - Download
Gapps::
Jelly Bean Gapps Updater-script - Download
Tool:
Modify-Boot - Download
Now no need to wait for me to mod your boot.img.Mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
SNAP.iT for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
SCROLL DOWN to 2nd POST FOR THE WHOLE GUIDE...
GUIDE
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
GUIDE FOR THE TOOL
Extract the downloaded zip file extract to any concinient directory.Here I will explain the guide as a cygwin user.
Extract the zip to directory say c:\
The extracted folder will look like 'Modify-boot".Now open the terminal or cygwin bash and mount the directory by typing
cd c:\modify-boot
Click to expand...
Click to collapse
Now drop your boot.img in the WORKING_313 folder and execute the script by typing
./modify-boot.txt
Click to expand...
Click to collapse
It will mod your boot.img for dual booting.Output boot.img will be in the WORKING_313 folder as boot.img.
MODDING THE ROM FOR DUAL BOOTING
Open the ROM.zip.
Get the modded boot.img from the tool and replace with the original one.
Now download the attached updater-script from 1st post and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
ADAPTING A ROM TO INSTALL IN THE SD CARD
If you want to mod your own rom other than the posted here,then you have to mod the updater-script in the rom
For that open your rom zip go to /META-INF/com/google/android and open the updater script
Now replace every line looking like following as;
From
mount("yaffs2", "MTD", "system", "/system");
Click to expand...
Click to collapse
TO
run_program("/sbin/mount", "dev/block/mmcblk0p3", "/system");
Click to expand...
Click to collapse
and this one
From
format("yaffs2", "MTD", "system", "0");
Click to expand...
Click to collapse
TO
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p3");
Click to expand...
Click to collapse
and add the following line next to the line written above
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p2");
Click to expand...
Click to collapse
Save the file and zip up the rom.Your rom is ready to install to SD CARD!!!!
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
[email protected] said:
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
MODDING THE CM9 ROM FOR DUAL BOOTING
Open the konstakang.zip (currently only supported rom, will add more soon).
Download modded boot.img from here extract it and rename the .img file to boot.img.
Delete the boot.img from the cm9 rom and put the downloaded one.
Now download the attached updater-script (remove .txt) or from here (for unregistered users)and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the cm9 rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
Click to expand...
Click to collapse
hi, thank u ....... the link for 'boot.img' is not working. Pls fix it
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
karthiknr said:
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
+1
We've been waiting on this ever since karthik and wbaws discussion made it sound impossible
Just reported as a news tip for the portal
Thanks!!
New update coming for tool soon!!!
Its a great achievement .. future updates will be easy to go on for basic user. Btw thanks man. .
Sent from my Blade using Tapatalk 2
I've found that making four partitions and installing /data to mmcblk0p4 and /system to mmcblk0p3 helps with certain roms that have S2E configured.
I'm also trying to get it to boot two mounted loop filesystems instead, i installed SSRLS7 and GB-Gapps as per your instructions in the OP (just changed the partitions for installation and the updater-script and init.rc so that it would work) did a dd of the entire partitions to files on the sdcard and edited the init.rc like this:
Code:
on fs
# mount mtd partitions
chmod 777 /sbin/busybox
symlink /sbin/busybox /sbin/losetup
mount vfat /dev/block/mmcblk0p1 /mnt/sdcard
losetup /dev/block/loop0 /mnt/sdcard/multiboot/snow/system.img
losetup /dev/block/loop1 /mnt/sdcard/multiboot/snow/data.img
mount ext2 /dev/block/loop0 /system
mount ext2 /dev/block/loop1 /data
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/block/loop0 /system ro remount
I also copied busybox to /sbin in the ramdisk before letting the process finish and make bootsd.img
It doesn't work though and i have no idea why not. I've mounted the system.img and data.img files on the phone via the terminal to test if the procedure works and it does mount them just fine.
If anyone has any clue why this doesn't work then please tell me.
Dual boot on ideos x6
[email protected] said:
hello guys. This my dual booting project for our amazing zte blade!
What is this?
>this mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of nand.
For advanced users only!!!
I will not be responsible for any bricked devices, damaged sdcards etc.
Do it at your own risk!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more roms like cm10, paranoidandroid etc.
Downloads:
cyanogenmod9(konstakang)
boot.img - download
updater-script - download
cyanogenmod10
boot.img - download
updater-script - download
gapps::
Jelly bean gapps updater-script - download
tool:
Modify-boot - download
now no need to wait for me to mod your boot.img.mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
Snap.it for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
Scroll down to 2nd post for the whole guide...
Click to expand...
Click to collapse
dear friends is it possible on huawei ideos x6?
Plz reply
vimi93 said:
dear friends is it possible on huawei ideos x6?
Plz reply
Click to expand...
Click to collapse
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
QuantumFoam said:
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
Click to expand...
Click to collapse
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
I stand corrected.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Oh and btw, [email protected], check the xda portal. You're on the front page.
Congratulations
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
Will try it out on my LG P500 then!
thanks
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
thank you for the reply

Recovering from /data mount issues

Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.

TWRP Error executing updater binary in zip

Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Prymston said:
Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Click to expand...
Click to collapse
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.
_that said:
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.
Click to expand...
Click to collapse
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.​
Prymston said:
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:
Click to expand...
Click to collapse
I don't know if Junior members are allowed to attach files to posts. If not, upload it to some paste site and post the link (you'll need to remove things like "http://" to be allowed to post it).
lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug.
Click to expand...
Click to collapse
Unlikely - if the recovery could not run update binaries at all, someone would have noticed. Why should restarting recovery change anything? What exactly is the bug?
lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.​
Click to expand...
Click to collapse
I tried that didn't work
Prymston said:
I tried that didn't work
Click to expand...
Click to collapse
Make sure to use the following option: TWRP > Wipe > Format Data > Yes
can't post log? probably to much text?
where can i post the log? I can't post it here.
i posted the recovery.log on google drive
Prymston said:
i posted the recovery.log on google drive
Click to expand...
Click to collapse
The script expects the device name to be "falcon":
Code:
script aborted: assert failed: getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.cm.device") == "falcon"
But your TWRP version calls it "xt1032":
Code:
ro.product.name=XT1032
ro.build.product=xt1032
ro.cm.device=xt1032
Workaround: replace "falcon" with "xt1032" in updater-script inside the zip file.
New Log.
Prymston said:
New Log.
Click to expand...
Click to collapse
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.
_that said:
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.
Click to expand...
Click to collapse
but i get a black screen when booting sailfish os, somethings not right.
Prymston said:
but i get a black screen when booting sailfish os, somethings not right.
Click to expand...
Click to collapse
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread
k-kuchen said:
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread
Click to expand...
Click to collapse
It worked! Thank you

[Newbie] Cannot flash [cm-12.1-20151022-NIGHTLY-taoshan.zip]

Hello Guys,
This is my first post in xda-developers. I have tried to read and understood the forum rules and will try to follow them.
I have wiped out my system partition and have installed ThunderZap ROM with TWRP recovery. With TWRP I am trying to install cm-12.1-20151022-NIGHTLY-taoshan.zip, I got the following errors:
updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing '/external_sd/cm-12.1.20151022-NIGHTLY-taoshan.zip'...
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E: Error executing updater binary in zip '/external_sd/cm-12.1-20151022-NIGHTLY-taoshan.zip'
Error flashing zip 'external_sd/cm-12.1-20151022-NIGHTLY-taoshan.zip'
Updating partition details...
...done
I guess this error is because I wiped out /system partition, the installer is not able to read ro.product.device correctly, so I removed the assert() that checks for the device type in META-INF\com\google\android\updater-script. This time when I recompress the cm-12.1-20151022-NIGHTLY-taoshan folder contents to cm-12.1-20151022-NIGHTLY-taoshan.zip, and try to install using TWRP installer, it throws up an error like this:
Installing '/external_sd/cm-12.1.-20151022-NIGHTLY-taoshan.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/cm-12.1-20151022-NIGHTLY-taoshan.1.zip'
Updating partition details...
...done
Any help on what could be going wrong? Is there any settings that I need to follow when compressing folder contents to a zip file?
Advance Thanks,
teejbee
you are on twrp recovery? (i guess the old one 2.8.4 ? )
go to Advanced -> Terminal command -> select
there enter:
setprop ro.product.device taoshan
setprop ro.build.product taoshan
then try to flash again
SdtBarbarossa said:
you are on twrp recovery? (i guess the old one 2.8.4 ? )
go to Advanced -> Terminal command -> select
there enter:
setprop ro.product.device taoshan
setprop ro.build.product taoshan
then try to flash again
Click to expand...
Click to collapse
Thank you! It worked. I am able to flash the original unmodified cm-12.1-20151022-NIGHTLY-taoshan.zip.
Regards,
teejbee
I have a question though. I installed playstore from here http://forum.xda-developers.com/showthread.php?t=1996995
I tried with version 5.10.30 and 5.9.12, it seems to open up and close immediately.
Is there anything I am missing for getting playstore? I am new to CM.
Thanks,
teejbee
teejbee said:
I have a question though. I installed playstore from here http://forum.xda-developers.com/showthread.php?t=1996995
I tried with version 5.10.30 and 5.9.12, it seems to open up and close immediately.
Is there anything I am missing for getting playstore? I am new to CM.
Thanks,
teejbee
Click to expand...
Click to collapse
yea you need to flash it manually in recovery....
http://opengapps.org/
arm -> 5.1 -> pico is what you need to select and then download and flash it
SdtBarbarossa said:
yea you need to flash it manually in recovery....
arm -> 5.1 -> pico is what you need to select and then download and flash it
Click to expand...
Click to collapse
Thanks a lot SdtBarbarossa. My problem with flashing cm-12.1-20151022-NIGHTLY-taoshan is solved now.
Feel delighted to have entered CM arena ?
No problem and Welcome

Categories

Resources