Database Info

[RECOVERY] CWM based recovery v5.5.0.4 + repacked Touch CWM v5.8.1.8

ClockworkMod Recovery for the Transformer TF101​
NEW: Repack of Koush's touch clockworkmod recovery v5.8.1.8 to address the reboot to recovery issue.
This recovery is not mine and I take no credit for it. I only made a small change to the official recovery found here
and repacked it into a flashable zip.
Here is a diff of the hacky but working fix.
Code:
diff -Naur org/init.rc new/init.rc
--- org/init.rc 2012-04-02 21:18:24.875745175 +0100
+++ new/init.rc 2012-04-02 20:58:55.855745201 +0100
@@ -31,6 +31,8 @@
service ueventd /sbin/ueventd
critical
[COLOR="Green"]+service clearmisc /sbin/clear-misc.sh
+[/COLOR]
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
diff -Naur org/sbin/clear-misc.sh new/sbin/clear-misc.sh
--- org/sbin/clear-misc.sh 1970-01-01 01:00:00.000000000 +0100
+++ new/sbin/clear-misc.sh 2012-04-02 20:58:55.855745201 +0100
@@ -0,0 +1,4 @@
[COLOR="Green"]+#!/sbin/sh
+# This clears the boot flag from misc which forces
+# this device to continuously boot into recovery
+/sbin/dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13[/COLOR]
Even though these recoveries have been tested by me, I won't be responsible for any loss of data or any damages done by using it.
IF YOU ARE NEW HERE PLEASE READ THE NEXT LINE VERY CAREFULLY!
See here if you are having trouble with a recovery loop from another version of recovery...
Did you get that? Just in case please read it again before posting about not seeing recovery being updated!
Download
Touch Recovery v5.8.1.8 (repacked from official with the fix above)
MD5: 0b7f3c5986847e37c1dffcb53a9b79af
ClockworkMod Recovery v5.5.0.4 roach-tf101-r2
MD5: a352abf783746eb29a0f98159ca3c439
Changelog
v5.5.0.4 roach-tf101-r2
-Standard 5.5.0.4 recovery
-Installs from the Internal sdcard
-Tar backups (Not compatible with backups from version 3.2.0.1 and below)
-Power off option re-added as I find this useful
v3.2.0.1 roach-tf101-r1
- Fixed Dock keys (Left shift and Caps Lock were reversed)
- Added advanced backup from solarnz
- Tweaked mounts to improve performance
v3.1.0.1 (R3-240511-1908)
- Initial release for Asus Transformer
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method
Mod Edit:
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credit: http://forum.xda-developers.com/showthread.php?t=1093818
Older versions
v3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1

Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that

gnufabio said:
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
Click to expand...
Click to collapse
I'm already on the case, the first post was just a taster of things to come.

Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer

hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards

Working towards rom manager support too?
Sent from my Transformer TF101 using XDA Premium App

does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol

brookfield said:
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
Click to expand...
Click to collapse
It's not currently backed up by CWM because the transformer has no /boot partition. There is however another way to back this data up so you will see this in a future update.

006fazer said:
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Click to expand...
Click to collapse
I had the wrong link. fixed now.

Warboy said:
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
Click to expand...
Click to collapse
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
The ability to Install updated from the internal sdcard will be in the next version.

i download the good file, but upate don't work !

Roach, how did you compile it?

try this http://www.mediafire.com/?o4e36tmkd2xqb11
Roach made a small mistake making the update.zip. You simply have to rename /kernel folder to /recovery

Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App

love you roach!
Sent from my Transformer TF101 using XDA Premium App

david279 said:
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I uploaded the wrong file lol, fixed now and MD5 updated. Apologies for the inconvenience

gnufabio said:
Roach, how did you compile it?
Click to expand...
Click to collapse
I used ubuntu.

Awesome nice to see Clockwork Recovery being updated. Maybe after you're done working on this one, you could port TeamWin Recovery Project over too for fun or something I used to use Clockwork on my phone but then made the switch to TWRP for a new feel.
Source for TWRP: https://github.com/TeamWin/Team-Win-Recovery-Project/
TWRP Image: http://forum.xda-developers.com/showpost.php?p=16130864&postcount=263
Overall, feels cleaner.
Aside from that suggestion rant, this version looks nice and looking forward to your additional updates for Clockwork Recovery. Hoping for ROM Manager support in the future.

Roach2010 said:
I used ubuntu.
Click to expand...
Click to collapse
I meant: did you used make or android's mm?

gnufabio said:
I meant: did you used make or android's mm?
Click to expand...
Click to collapse
Oh, Sorry. I used make. You will need to setup a full build environment if you want to compile recovery.

[Release]FeaMod Recovery 1.4 - based on CWM Recovery v. 5.5.0.4.

I've ported the CWM Recovery v. 5.0.2.7 to the Samsung Galaxy I9001 device.
Download it here and follow the instructions to install it. I will post any changes or updates again in this very first post.
Disclaimer: Flashing software onto your device might void your guarantee and may brick your phone. Use the attached software on your own risk. I am not responsible for any bricked device due to this software. You've been warned.
Credits and huge thanks go to:
Koush - for writing the original ClockworkMod Recovery
Ilarrain- for patching graphics.c for the Galaxy Ace device
YardE - providing init.d support to the custom kernel
Riversource - for providing scripts which make the handling of smd files super easy
All the users on this forum who have tested my former versions and helped to debug it - you're great
Are there any differences to "stock" CWM recovery which I can see?
Yes, there are. I've removed additional "No"'s in some functions. I've also changed the background logo and the name of the recovery (though "CWM Recovery" is still there due to make proper credits and copyright thing things). And of course there is the custom kernel included!
How to install/update
If you already have a FeaModRecovery version on your device it's simple:
Download one of the update.zip packages (starting with version 1.3) and copy it to one of your sdcards. Reboot into recovery and install the package (install zip from sdcard -> choose zip from ...).
If you're still on stock recovery or another one follow the the step-by-step instructions on the bottom of the post.
What about the version numbers?
The first number represents major updates (for example update to CWM 6 thus FeaMod v. 2)
The second number represents minor updates. For example if CWM goes up to 5.0.2.8 or I change something on my version.
The third number on some versions represents the kernel since it's a custom one and included in the whole package. So if only the last number changes, I have made "only" changes to the kernel.
Downloads
SMD files to flash via Odin
download FeaMod v1.1: http://www.mediafire.com/?oxxn0676fikkdaw
download FeaMod v1.2: http://www.mediafire.com/?u9996yn6i7rc92z
Hint:
For those who experience boot loops. Before you flash a new version copy the content of your external sdcard onto your pc and format it afterwards. This should help. After you've successfully flashed and rebooted into your system you can copy the files back on your external sdcard.
zip files OC/UV kernel to flash via FeaMod Recovery
WARNING:
Applying the FeaMod Recovery with the FeaCore_OC/UV kernel is dangerous and may brick your phone. In any case it will drain your battery faster when running on 1.8 GHz all the time. Only install it when you know what you are doing! Otherwise install a package without a OC/UV supporting kernel.
FeaMod Recovery 1.3.1 with FeaCore Phoenix OC stable release: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
FeaMod Recovery 1.4 with FeaCore Phoenix OC stable release: http://www.mediafire.com/?jqfbvxflev1jcoz
zip files without OC/UV kernel to flash via FeaMod Recovery
FeaMod Recovery 1.3.1 with FeaCore Phoenix nonOC stable release: http://mediafire.com/?5unogie5i58x85r
FeaMod Recovery 1.4 with FeaCore Phoenix nonOC stable release:http://www.mediafire.com/?ben9s5a8bz1d3gc
if you wanna change your bootanimation, copy your downloaded bootanimation.zip to /system/media/sanim.zip (yes you have to rename it to sanim.zip). Change the modus to 644 (rw-r--r--).
How to change the bootanimation:
Copy the bootanimation.zip to your sdcard and start adb shell:
Code:
mount -o rw,remount /system
cd sdcard
dd if=bootanimation.zip of=/system/media/sanim.zip
chmod 644 /system/media/sanim.zip
Changelog:
FeaMod v.1.1:
+ Performing a factory reset aka wipe data now doesn't delete the external sdcard anymore.
+ Performing a backup with no changes in the mount menu will automatically backup .android_secure as well.
+ The external sd card will no longer be "backuped" unless you manually mount the sd-ext in the mount menu.
FeaMod v.1.1.1:
+Kernel changes: initd support - implemented by YardE. BFQ I/O Scheduler implemented by me
FeaModRecovery v.1.2:
-Included the rest of the changes made by Koush
-You can now select wheter you wanna make the backup onto internal or external sdcard
-I've decided to let go the backup of the external sdcard (save .android_secure of course). Because it can destroy your internal sdcard when not properly handled and backing up the external sdcard on the external sdcard doesn't make any sense at all.
FeaModRecovery v.1.3:
- fixed a bug which led to a md5 mismatch when recovering only single partitions (advanced recovery).
- reimplement the reboot into recovery option. This option now makes sense again (see next point).
- I provide you from now on with update.zip packages to update FMR from within an already installed FMR.
FeaModRecovery v.1.4:
- https://github.com/CyanogenMod/android_bootable_recovery/commits/ics/
Kernel (FeaCore_1.0 and FeaCore_1.0_OC/UV):
- update to jhash3 (for better reliability on data connections)
- implemented BrainFuck Scheduler as main scheduler (CFS is gone for the moment)
- implemented interactive governor (ondemand is still default and already very aggressive)
- implemented BFQ I/O
- init.d support (thx to YardE)
Kernel FeaCore Phoenix (OC and nonOC):
-jhash (battery drain is too high with jhash3)
-CFS as CPU scheduler
-SmartassV2 as new governor (ondemand is default)
-CFQ, BFQ, SIO and Deadline as I/O schedulers (SIO is default)
-supports Boot animation
-custom Boot sound
-cleancache patches
-I8150 GPU libraries
How to use
Start the FeaMod Recovery by pressing your Power Button and the Volume Up button simultaneously. Hold both keys until the Samsung Logo appears. Release both keys after additional 2-3 seconds and wait. The system now boots into FeaMod Recovery.
Navigate in the menu: Volume Up/Volume Down buttons
Select item: Menu Button
Return to start screen: Return button
Additional hints
Old versions (all versions until v.1.1.1): To backup your external-sd too, you need to mount the sd-ext partition in FeaMod Recovery:
Select mounts and storage -> mount /sd-ext.
Warning:
Don't backup your external sdcard if its content is larger than the space on your internal sdcard left!!!
If not manually mounted only your apps on the sd-ext will be saved.
In case the system won't recognize your external sdcard: Copy the content of your external sdcard to your PC and format it within your ROM. Copy the files back onto the newly formatted external sdcard. Thx to Igor_999 for stumbling across that problem
Sources on github:
https://github.com/manveru0/FeaMod-Recovery
Have fun with it!
Do it step by step ;-)
For Odin related things, look also at the attached image.
Important: You have to install busybox under /system/xbin/ in order to get the init scripts working.
Get "Busybox Installer" from the market. That version let you choose the location to install it.
1. If you don't have at least XXKP4, download it from samsungmobile (you need to register, but it's worth it)
Browse through the forum and go to our devices, there you'll find the ROMs. If your comfortable with your ROM
go to step 3.
2. Download Odin 4.43 from here and flash the files. If you have a one package file, download AriesVE.ops from this post and select that one in Odin
under OPS file. If you downloaded XXKP4 select the bootloader.tar as the BOOT file, the MODEM file as the phone file, the PDA file as the PDA file and the CSC file as the CSC file. Flash it and wait until your phone has rebooted back into the system.
3. Download FeaMod Recovery v.1.2.
4. Open Odin again and select the AriesVE.ops as the OPS file. Tick the one package option under OPTION. The select the FeaMod file as the One Package file. Flash it! After 10 to 15 secs your device will reboot into your system.
6. Copy the Universal Adrenaline v.13 zip file (download it from here: http://forum.xda-developers.com/showthread.php?t=1236779) to your internal or external sdcard.
5. Shut your device down and reboot into FeaMod Recovery v.1.2. by holding the Volume up and Power Button simultaneously until the Samsung Logo appears, hold it for 2,3 seconds longer and release both buttons. Welcome to FeaMod zone :-D
6. Make a full backup either to your external or internal sdcard (look at the options you got) just to be sure.
7. Go to mount and storage -> mount /system
8. Go to advanced and select fix permissions.
9. Go to install zip from sdcard and select your fresh copy of adrenaline shot v. 13.
10. Reboot into system.
you got it! You now have FeaMod Recovery v.1.2. with the latest kernel from YardE and me which supports init.d and has BFQ as the default I/O scheduler. And you should have the applied adrenaline shot by now. Test it either with a terminal (you should have the /system/etc/init.d folder) or by the quadrant benchmark (you should get at least 2500 points). In case there are any questions left, ask for.

Nice. I just flashed it and its backing up right now. It seems to work like a charm. Thanks!

it's looks like this right??

hi. sorry i don't get it. what is the function for this? is it to backup my current ROM?

OK, I had a bad day today, but this made my day!
Thank you sooo MUCH!
So, now... Custom ROMs much more easily?

budakmaran said:
it's looks like this right??
Click to expand...
Click to collapse
Yes, thats correct!

AWESOME
I've said it before and i'm saying it again You are awesome!!! Thnx a lot.
And also a big thank you to netchip without whom i dont think we could have had this
I'm soooo happy! now cyanogen mod to look forward tooo

Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001

Blumdum said:
Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001
Click to expand...
Click to collapse
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext

sweeeeeeet ill try this later looking forward to cyanogen mod now we have working cwm

manveru0 said:
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext
Click to expand...
Click to collapse
ok the ext-sdcard seems to work after i formatted the card
just have to copy back the files

Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.

traedre said:
Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.
Click to expand...
Click to collapse
you are welcome. Thank you, good to hear

Am I right that there is init.d support included?
Sent from my GT-I9001 using XDA App

Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.

Works like a CHARM! LOVing it!

Very nice work! There is one problem. Members from the site 4pda.ru actively using CWM. Only for Skype both cameras are becoming as rear, front camera disappears. The guys were asked to write about this issue. It is strange that this is not who did not notice. Itself is not using Skype. Check it out please.

quest221 said:
Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.
Click to expand...
Click to collapse
Yep, that's perfectly okay because I have uploaded a new file with a fixed bug yesterday evening. See also the first post

manveru du bist ein konig
thanks for one package
i will test it today
btw what for a cpu government was there setted up before?

problem this cwm in skype. 2 back camera, no working front camera, only back... fix it please.
sorry my english...

[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

[Solved] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?

Hi all,
I want to install Andromadus ROM Build 13 on my DS and currently have stock 2.3.3 installed.
As this will be my first custom ROM and also I couldn't find any how-to to install Andromadus on an HTC Desire S so, I am posting it here.
I have 4EXT touch recovery, S-OFF'ed and the HBoot is downgraded to 0.98.2000 (PG8810000).
So, where do I start? I am making backups using 4EXT recovery and downloading "flinnycm101_saga_13.zip" & "gapps-jb-20121212-signed.zip" from http://andromadus.flinny.org/?q=node/24
but as posted on the same page..I have a doubt of whether to flash the MDDI kernel too? Is that required to be flashed on an HTC Desire S ?
Any full length how-to's will be appreciated.

General guide to flash any rom can be found here
No need to flash kernel. Just flash the rom and gapps.
You might also want to use Titanium Backup to backup any apps from your stock rom and restore to the new rom.

oddoneout said:
General guide to flash any rom can be found here
No need to flash kernel. Just flash the rom and gapps.
You might also want to use Titanium Backup to backup any apps from your stock rom and restore to the new rom.
Click to expand...
Click to collapse
So, Can I use 4ext's recovery app to boot into recovery mode >> then format System
>> Format Data
>>Format Cache
>> then Format Boot
>> Wipe Data/Factory reset (1st option in wipe/format menu)
>> Wipe Dalvik Cache
>> n then finally install zip (ROM) from sd card and flash the rom..
>> then flash then gapps zip?
Also, isn't 4ext's backup option backs up my apps, app's data and the contacts too? :| um..what about the draft message(s) ? will that be backed up too using 4ext recov.?
But I guess I won't be able to restore them on an individual basis when I am done flashing the new ROM? As 4ext's created backup can only restore the full backed-up data which includes the old ROM itself!
Update: backing up apps+data using Titanium backup pro..so that will backup my contacts+ sms+draft sms too..right?
Any advice?

Guys..I did the following:
went to 4ext's recovery app in recovery mode
>> then formated System
>> Formated Data
>> wiped* Cache (as there was no option for: "format" cache)
>> then Formated Boot
>> Wiped Data/Factory reset (1st option in wipe/format menu)
>> Wiped Dalvik Cache
>> n then finally installed zip (ROM) from sd card and flashed the rom..
>> then flashed then gapps zip
Now after 1st reboot from recovery..I am stuck at white background saying HTC..its been quite a few mins around 3-4mins
Shall I re-flash the ROM ?
Please help :s

sky770 said:
Guys..I did the following:
went to 4ext's recovery app in recovery mode
>> then formated System
>> Formated Data
>> wiped* Cache (as there was no option for: "format" cache)
>> then Formated Boot
>> Wiped Data/Factory reset (1st option in wipe/format menu)
>> Wiped Dalvik Cache
>> n then finally installed zip (ROM) from sd card and flashed the rom..
>> then flashed then gapps zip
Now after 1st reboot from recovery..I am stuck at white background saying HTC..its been quite a few mins around 3-4mins
Shall I re-flash the ROM ?
Please help :s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1943524 read this!!!

acultr said:
http://forum.xda-developers.com/showthread.php?t=1943524 read this!!!
Click to expand...
Click to collapse
h ****..I just pulled it out :'(
well..it again got stuck into the same boot screen..
funny thing is I din't even pressed the power button it straightaway booted up? :s
ok...wrote the command "adb reboot recovery"
I am back into the 4ext recovery menu
now what's next?

sky770 said:
h ****..I just pulled it out :'(
well..it again got stuck into the same boot screen..
funny thing is I din't even pressed the power button it straightaway booted up? :s
ok...wrote the command "adb reboot recovery"
I am back into the 4ext recovery menu
now what's next?
Click to expand...
Click to collapse
read the previous post

acultr said:
read the previous post
Click to expand...
Click to collapse
Is there a way I can determine which screen do I have..now that I have already flashed my device and cannot access es explorer and stuff?
I do have access to 4ext recovery and adb console :|
Is it possible to navigate to / or /sys using adb console?
Also, suppose even if I do have the MDDI type of screen and I flash the MDDI kernel img but will that mean that I won't be able to adjust screen brightness and stuff?

Just flashed the MDDI kernel..waiting for reboot proc to complete...
I hope this doesn't fail this time.. :|

Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
As a suggestion, flash the mddi panel if it boots then you can be fairly certain your on the right path. At the moment there is no brightness control for mddi panel but there are some alternatives in the thread i directed you to
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom

jugg1es said:
As a suggestion, flash the mddi panel if it boots then you can be fairly certain your on the right path. At the moment there is no brightness control for mddi panel but there are some alternatives in the thread i directed you to
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
Click to expand...
Click to collapse
now its been ~2-3mins still stuck on the HTC screen :| (even after flashing the MDDI kernel)
Do I have to re-clear/wipe the cache..after flashing the ROM? or re-flash the ROM itself? (as I have read in some posts that it usually works after clearing the dalvik/cache and/or reflashing the same ROM again)
Can you provide me with the command I can use on adb console to find out the brand of my screen's manufacturer ?
Update:
I had flashed the ROM and then flashed the google apps pkg and then after a reboot now again flashed the MDDI kernel.
Is it the correct sequence to install the MDDI kernel?

Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(

I have shifted my issue to this thread: http://forum.xda-developers.com/showthread.php?p=37933379

Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
sky770 said:
Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(
Click to expand...
Click to collapse
Best thing to do is not panic, you can still access recovery. What i would do in this situation is start again from the beginning with fresh downloads checking you have correct gapps package for the rom(check md5 of all files) using 4ext format all except sd card and reflash new downloads. Reboot into recovery using adb, try not to pull the battery unless you really have to then if you do wait a couple of seconds before replacing it
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom

jugg1es said:
Best thing to do is not panic, you can still access recovery. What i would do in this situation is start again from the beginning with fresh downloads checking you have correct gapps package for the rom(check md5 of all files) using 4ext format all except sd card and reflash new downlosd
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom
Click to expand...
Click to collapse
Thanks for replying..
um..can you please..follow with me in this thread here: http://forum.xda-developers.com/showthread.php?t=2146151
Thanks a lot :|
PS: Sorry..I am all on fire..as this is the only phone I have :| (except my sucko Nokia )

sky770 said:
Need help guys..its been more than 5 mins since I am stuck on the screen..what should I do now?
Pull out the battery..to give it a hard reset?
Please help :'(
Click to expand...
Click to collapse
go to recovery restore your prev. ROM and check the panel
Step 1. Find out which screen panel your device has:
1) Download and install Android Terminal Emulator from Google Play Market
2) Open the application and type in these commands:
(WARNING: to use these commands - you must be rooted with either Superuser or SuperSU AND have BusyBox installed on your phone)
su
dmesg|grep -i panel
If the app shows you any text with word "sony" in it - then your device has a screen panel made by Sony (obviously). If that's the case - you can just close this thread at once and don't worry that your device might freeze at "HTC Quietly Brilliant" screen after flashing a ROM. Otherwise, proceed forward.
OR
1) Open up a file manager that has an ability of browsing any partition above the default SD-card directory and can access the system partition
You can use either ES File Manager or Root Explorer
2) Navigate to /sys/android_display
If there is a file called "sony ****** wvga" - then you have a Sony panel. Otherwise - you device has a panel by Hitachi.
Step 2. Download a MDDI kernel developed by Andromadus:
For Android 4.0.x & 4.1.x, use this link --> http://goo.im/devs/Super/andromadus/...kernel_82n.zip
For Android 4.2.x, use this link --> http://andromadus.flinny.org/sites/a...212.zip&nid=16
Step 3. Flash the MDDI kernel:
If you are S-OFF --> just flash the .zip file with the kernel after flashing the ROM and GAPPS package through "install zip from sdcard"
If you are S-ON --> use the following instruction:
Thanks for Fatal1ty 18 RUS:good:

Re: [Q] How to start Flashing Andromadus ROM (Build 13) Android 4.2 on HTC Desire S?
sky770 said:
Thanks for replying..
um..can you please..follow with me in this thread here: http://forum.xda-developers.com/showthread.php?t=2146151
Thanks a lot :|
PS: Sorry..I am all on fire..as this is the only phone I have :| (except my sucko Nokia )
Click to expand...
Click to collapse
Stop opening fresh threads, people tend to ignore you More if you constantly open threads. I had a couple of panicky moments when i first did mine. Just take a deep breath and start again
”As you get older three things happen. The first is your memory goes, and I can’t remember the other two.” - Norman Wisdom

The MD5 was not same ! The MDDI kernel I flashed it did not had the same MD5 as I the one I redownloaded..
And now..I cannot reboot into recovery by using adb.. :'(
I tried "adb reboot recovery" command
And it gave me an error saying: error: device not found
How can I reset the adb?
PS: sorry MODs but I wanted to present my problem clearly so had to open a thread with a clear description.

sky770 said:
The MD5 was not same ! The MDDI kernel I flashed it did not had the same MD5 as I the one I redownloaded..
And now..I cannot reboot into recovery by using adb.. :'(
I tried "adb reboot recovery" command
And it gave me an error saying: error: device not found
How can I reset the adb?
PS: sorry MODs but I wanted to present my problem clearly so had to open a thread with a clear description.
Click to expand...
Click to collapse
command:adb devices

acultr said:
command:adb devices
Click to expand...
Click to collapse
prints:
List of Devices attached
it is showing nothing :'(

[ROM][PORT][CM7.2] Radiance Final

Screenshots dont do it justice still....​
Thread Navigator : #1 - Features,installation guide,downloads.
#2 - Changelog
#3 - Buglist
#4 - Screenshots​
Features - #Storages
Faster storages
Auto cache clean n every boot
Very low internal memory utilization
#Silent features
Gapps included
NO battery loss when screen off
Full cm7 theme support
100% bug free
Trans-Layer UI(With lots of transparency)
Removes useless system sounds
Changed UI sounds
Built in wallpapers
Super SU
Low memory footprint
Status bar soft buttons-Enable in CyanogenMod Settings-Tablet Tweaks
And lots more...Explore yourself​
Installation Guide
1.Download the rom given below.
2.Place it in the root of your sd card.
3.Go to CWM and under mounts and storage,format system,data and cache.
4.Go back and wipe data and cache.
5.Again go to mounts and storage and mount system,data,cache and sd card.
6.Flash the rom
7.Wipe data and reboot.​
Downloads - (Radiance Final) : https://www.mediafire.com/?c14288sy1xyeh5e​
Original Thread : http://forum.xda-developers.com/showthread.php?t=2392302​

Changelog - #1 - Initial Build

Buglist - Same as RC1 by percy.

Wow..... please provide the link asap.
Sent from my highly pimped Galaxy Pocket.
1. Love doesn't need any reason.
2. Wanna speed up 3G (not 4G LTE)?
Here it is:
http://forum.xda-developers.com/showthread.php?t=2586876
3. My blog

Screenshots :

Looks cool thumbup.... One more successful port by aniket.... links plz

Could you guys wait for 30 mins more? Got a network error!

Link added to #1 post.!!

Flash percy kernel before flash Rom??????? i am noob ^^

hoops04 said:
Flash percy kernel before flash Rom??????? i am noob ^^
Click to expand...
Click to collapse
Yes.
Sent from my highly pimped Galaxy Pocket.
1. Love doesn't need any reason.
2. Wanna speed up 3G (not 4G LTE)?
Here it is:
http://forum.xda-developers.com/showthread.php?t=2586876
3. My blog

hoops04 said:
Flash percy kernel before flash Rom??????? i am noob ^^
Click to expand...
Click to collapse
No need.I already included percy's kernel in the zip file.

Root error
Sent from my GT-S5360 using Tapatalk 2

aniket.lamba said:
No need.I already included percy's kernel in the zip file.
Click to expand...
Click to collapse
dont include the kernel in cm roms
why?
because you have to flash the kernel seperately
why?
because you need to reboot to recovery after flashing the kernel and format system data cache to convert it to ext before flashing the rom
This means if you are flash it from stock without being on ext first the rom will not boot

If I am on a cm rom and if I flash this rom funcion?
Sorry for my bad english.

vivimilan said:
If I am on a cm rom and if I flash this rom funcion?
Sorry for my bad english.
Click to expand...
Click to collapse
yes if you format system data cache and mount system data cache first befire flashing zip
and since you are already using cm7 I presume you are already using a cm kernel with an ext system partition

Please.....can you fix a2dp ? Realy need it and realy want to move to cm7
Sent from my Transformer Prime TF201 using xda premium

marcussmith2626 said:
dont include the kernel in cm roms
why?
because you have to flash the kernel seperately
why?
because you need to reboot to recovery after flashing the kernel and format system data cache to convert it to ext before flashing the rom
This means if you are flash it from stock without being on ext first the rom will not boot
Click to expand...
Click to collapse
Sorry about that.Actually including a kernel in the zip is way more convenient than flashing it separately.Next time I won't include the kernel in the zip.

aniket.lamba said:
Sorry about that.Actually including a kernel in the zip is way more convenient than flashing it separately.Next time I won't include the kernel in the zip.
Click to expand...
Click to collapse
you can include kernel but you would have to change the instructions
it would be
goto cwm
mount system data cache
flash rom zip
reboot to recovery
format system data cache
mount system data cache
flash rom zip again
restart
in theroy that would work
but some people might like the choice between kernels eg percys or black reactor so if they wanted a different kernel they would either have to replace the boot.img in the zip or flash a different kernel after flashing your rom zip for the 2nd time in above instructions

nice port will try and give report asap

non transperent would be nice....