Database Info

[Update Jul 18]Collection of ROMS compatible with TW HTC branded Magic (PVT32A)

I must thank pioneers nk02, Fatal1ty2787, daldroid , and of course haykuro for their great roms;
Amon_RA for his great recovery.img and detailed instructions on repacking and signing update.zip;
and our new force redglasses for his efforts to finetune these roms for us.
The following are roms modded for TW HTC Magic (PVT 32 A, CPLD-12, Boot with Hami)
Be sure to use them for ONLY TEST purposes.
For your reference, the current build of my magic is as follows:
------
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
------
## 請自負風險，刷機可能使你的magic便磚塊或喪失保固，如果之前沒有刷過別的rom，請勿從此篇開始##
## 新手請先閱讀本版之前的文章，瞭解程序後再刷##
## 成功服用以下ROM的網友，無論好壞也請po一下是否成功、並協助刷機遇到問題的人，這樣更多人能夠受惠 ##
Download Amon_RA's recovery image if you need it
v1.0H http://www.4shared.com/file/115091119/89a57dac/recovery-RAv1.html by Amon_RA
v1.1H http://rapidshare.com/files/251894590/recovery-RAv1.1H.img nandroid restore is included by Amon_RA
********Hero ROM for Magic modded for TW users (based on Fatal1ty2787's releases)********
07/18 myhero-08 by redglasses
http://www.4shared.com/file/118776501/c759bba3/myhero-008.html...Change log on page 22
07/15 myhero-07 by redglasses
http://www.4shared.com/file/118054720/4c20968a/myhero-007.html...Change log on page 19
07/08 myhero-06 (based on Fatal1ty2787's 1.4) released by redglasses
http://www.4shared.com/file/116533960/30b75973/myhero-006.html
Feature: zh_HK included, optional root access, and etc... Change log on page 14
07/07 myhero-05 (based on myhero02 and Fatality2787's 1.3) by redglasses
http://www.4shared.com/file/116341177/77ab5baf/myhero-005.html
Feature: Chinese input, Chinese UI, other languages removed...Change log on page 12
07/06 Camera fix on page 11.
07/04 v1.2[CUI] Chinese Input + Chinese User Interface by redglasses
http://www.4shared.com/file/11594679...yhero-002.html
http://www.sendspace.com/file/1mgprx
07/02 v1.2[C] embedded with lib files needed to run HTC_CIME by richyyun
http://www.4shared.com/file/115470968/23ed1157/v12-cime-signed.html
This version (v1.2[c]) of rom is suitable for users who need to input Chinese on magic using methods other than handwriting.
After flashing this rom, be sure to install HTC_CIME.apk manually.
All the Chinese input methods, including Zhuyin and Pinyin, work on this rom!! Hooray!!
However, all the ringtones, except Innovation.mp3, have been removed to squeeze out some space for these lib files.
You have to push your favorite ringtone by yourself.
Here is a backup of the original ringtones and alarms http://www.supremekickz.com/android/audio.rar
07/02 v1.2 http://www.4shared.com/file/115417767/ab5becd5/Fatal1ty_Hero-Full_v12-modded-for-32A-CPLD12.html rooted as default by richyyun
06/30 v1.1 http://www.4shared.com/file/115116254/f7c5da91/Fatal1ty_Hero-Full_v11-modded-for-TW-signed.html
06/30 v1 --- no longer needed
1. rename the downloaded file to update.zip and place it in /sdcard
2. fastboot boot recovery-RAv1.img --> wipe, backup, and apply the update
3. install HTC_CIME if necessary
http://www.4shared.com/file/111084919/7947d185/HTC_CIME.html
********Hero Pure Black for 32A (based on jerpelea's pure black rom-04)********
07/14 hero-pure-black-04 by richyyun (for non-Chinese users)
http://www.4shared.com/file/117980221/9b591630/hero-pure-black04-32A-by-richyyun.html
07/14 hero-pure-black-04[C] by richyyun
http://www.4shared.com/file/117990058/9320c58d/hero-pure-black04C-32A-by-richyyun.html
The [C] version has camera.apk replaced, chinese input (CIME) preinstalled, and ...Screenshots on page 18
07/15 hero-pure-black-04[CUI] by redglasses
http://www.4shared.com/file/117534734/7b937728/mypureblack.html
********7/6 Hami Rooting (Rooting OEM TW Cupcake ROM)***********
Running modded Hero and ION roms on Magic is cool, but some compromises must be made, such as manual input of APN, injection of libs,...
For those already satisfied with the oem rom (TW HTC ROM with Hami boot logo), I have created a new boot.img.
This boot.img is rooted and sets the max cpu freq at 528Mhz. After flashing it, you can also get a root access at adb shell.
You can further push a modded version of su into the system to gain root access at terminal app.
Before you begin, please make sure:
(1) Your magic is running TW OEM ROM (Cupcake 1.5) with Hami boot logo
(2) SPL has been flashed
Steps are:
1. Download this package created by richyyun first. http://www.4shared.com/file/116302268/1b7cc008/richyyun-hami-rooting.html
2. Inside the zip are two files, including boot-hami-rooted-max528.img and su
3. In fastboot mode, test run the new rooted boot.img **Very important**
=> fastboot boot boot-hami-rooted-max528.img
4. If it successfully boots, you can begin to flash it
=> fastboot flash boot boot-hami-rooted-max528.img
5. Reboot and you'll get # in adb shell
6. Push modded su into the system
=> adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#exit
=> adb push su /system/bin/su
=> adb shell
# cd /system/bin
# chmod 6755 su
# sync
# reboot
********7/4 New BOOT.IMG for Hero********************************
The frequency of the CPU inside magic is self-adjusted according to real-time processing demand.
However, there is a parameter in rom defining the range (max and min) of cpu frequency adjustment.
In OEM roms, the max freq is set at only 384Mhz.
In the following two versions of boot.img, the cpu freq range is redefined.
[max=528Mhz] http://www.4shared.com/file/115500341/1cec4112/boot-cpu-max528.html by richyyun
[min=max=528Mhz] http://www.4shared.com/file/115939851/44c86a93/boot-cpu-always528.html by richyyun
Note that when min=max=528Mhz, you battery doubtedly drains slightly faster!
For the moment, if you are already satisfied with the current rom and don't want to flash new roms so soon, you can flash this boot.img alone to make some changes to your magic!
1. on your pc, you can test run the new boot image first
fastboot boot boot-cpu-freq-fixed-for-32A-12.img <=be sure to test it first!
2. if it works, then make it permanent
fastboot flash boot boot-cpu-freq-fixed-for-32A-12.img
********ION for TW MAGIC users (based on nk02's first release of ION rom)********
07/04 ION-V2[C] http://www.4shared.com/file/115896084/56906abb/nk02-v2c-r1-signed.html
HTC_CIME and libs it requires are built in. Manual injection of libs is NO LONGER NEEDED! ##刷完馬上就可以輸入中文##
Lite, smooth, and rooted. Screenshots are shown in page 9
06/27 FULL rev1 http://www.4shared.com/file/114847653/9f8c5587/nk02-4-full-for-TW-rev1.html recommended
06/27 LITE http://www.4shared.com/file/1150789...Hero-Full_v1-Rogers-signed-modded_for_TW.html
1. wlan.ko and libpdfviewer.so have been pushed into the rom
2. original magic ringtones are copied into this rom (i like "Innovation.ogg"), so G1 and G2 ringtones are all put together.
All the files needed to make this possible are included in the file packge...
--- steps in grey color are no longer needed in rev1 of update.zip
1. adb push update.zip /sdcard/update.zip
2. fastboot boot recovery-RAv1.img
3. Run nandroid to backup your entire phone ***very important***
4. wipe the system
5. apply the update
after successfully booted,
6. on your pc, run "adb remount"
7. run "adb push wlan.ko /system/lib/modules/wlan.ko" to make wifi work
8. navigate to setting on your phone to activate installation of unknown sources
9. run "adb push HTC_CIME.pak to /sdcard/HTC_CIME.pak" to transfer chinese input plugin to sdcard
10. run HTC_CIME using ASTRO which has been bundled with the rom.
---
you can also flash recovery-RAv1.img to make it permanent (not a must)
11. in fastboot mode, run "fastboot flash recovery recovery-RAv1.img"
---
**********daldroid's rom (rooted and very lite)**************************
see this post http://forum.xda-developers.com/showthread.php?t=523680
----- links --------
Recovery:
http://www.megaupload.com/?d=JYPX30HN
Rooted (adb shell) Original HTC ROM for Magic:
http://www.megaupload.com/?d=65MNJXYS
**************Instructions on restoring your magic**********************
Copy the image files backed up by Nandroid from sdcard to your pc.
Or you can use mine (Chunghua Telecom with a Hami boot logo)
http://www.4shared.com/file/115081359/d32d4576/TW_MAGIC_original_rom.html
1. enter fastboot mode by pressing back+power
2. fastboot erase system -w
3. fastboot erase boot
4. fastboot flash system system.img
5. fastboot flash userdata data.img
6. fastboot flash boot boot.img
7. fastboot reboot

great.... awaiting the v1.1

Thanks for your ROM, is this one compatible to HK HTC Magic?
The HK version info:
PVT32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12

onenew said:
Thanks for your ROM, is this one compatible to HK HTC Magic?
The HK version info:
PVT32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
Click to expand...
Click to collapse
I think you need to flash the SPL first....
Search a thread started by Amon_RA
There is a collection of SPLs
With a modified SPL, you think you can successfully flash any of these roms, with no guarantee

So great. But when I run clock, it has stopped unexpectedly. Hoping next ver. will fix it

rickykan said:
So great. But when I run clock, it has stopped unexpectedly. Hoping next ver. will fix it
Click to expand...
Click to collapse
Have you flashed SPL?
http://forum.xda-developers.com/showthread.php?t=529019

hi, would like to know does it have microsoft exchange?

many thanks ar.....i love it....it have exchange ar

i like how i get no credit for discovering root on these devices, and making any of this possible

The version of Fatal1ty's ROM that you've modded works _perfectly_ on Rogers HTC magics! This is awesome!

haykuro said:
i like how i get no credit for discovering root on these devices, and making any of this possible
Click to expand...
Click to collapse
Sorry for missing your name...
With no doubt, you deserve most of the credits!!
You're the pioneer and father of magic rooting...

--duplicate post--

the ROM works excellently,and didn't find any bugs.
nice ROM

Nice Rom.
But I do not understand how to install HTC_CIME.
Should I install it in fastboot or.........? I need some suggestion, thanks.

Awesome work - updated my blog to use this rom instead of the first one skittleguy posted.
http://radixgadgets.blogspot.com - has a step by step guide and quick video of my HTC Magic running this rom.
Haykuro - forgive us bloggers and posters - we are but men standing on the shoulders of giants like yourselves! You've done awesome work and we all appreciate it!!!
One odd thing I've noticed with these new roms - the LED light for charging doesn't display anymore - no more orange (indicating charge) or green (indicating full charge) anymore - though it still indicates onscreen.
I suspect the hero devices use a different method for their led notifications and this is why.

ralin said:
Nice Rom.
But I do not understand how to install HTC_CIME.
Should I install it in fastboot or.........? I need some suggestion, thanks.
Click to expand...
Click to collapse
place HTC_CIME in sdcard
or run this command
"adb push HTC_CIME.apk /sdcard/HTC_CIME.apk" to push it to the sdcard
Then on your magic (hero, haha), use ASTRO (a file explorer) to execute HTC_CIME

hmm....I renamed HTC_CIME.zip to HTC_CIME.apk, but I can not execute it as .apk file.

richyyun. You're the man. Many Thanks for your exellent work.
BTW, I have some questions.
When I tried to root my device (Hami Boot Logo) I typed these commands
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd system/bin
cat sh > su
after this command
cat sh > su
it says
write: No space left on device
what should I do?
Thanks

ralin said:
hmm....I renamed HTC_CIME.zip to HTC_CIME.apk, but I can not execute it as .apk file.
Click to expand...
Click to collapse
you should unpack HTC_CIME.zip and you'll see HTC_CIME.apk

sukniyom said:
richyyun. You're the man. Many Thanks for your exellent work.
BTW, I have some questions.
When I tried to root my device (Hami Boot Logo) I typed these commands
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd system/bin
cat sh > su
after this command
cat sh > su
it says
write: No space left on device
what should I do?
Thanks
Click to expand...
Click to collapse
The solution is to remove the original su first before cat sh > su
-->
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd system/bin
rm su
cat sh > su
chmod 4577 su
sync
reboot
---
run terminal to test if you get #

[UTIL] [NEW] switchrom.sh V1.1 - One step bookmark, store and restore your ROMs

Changelog:
1.1 - Allow delete/restore without a name. Choose from the list.
1.0 - Use nandroid to make it one step process.
Currently, nandroid backups do not contain the a2sd app folders. It has been painful to say the least to jump between ROMs.
This script does two things:
1. Store and tag a ROM's nandroid backup and its apps data. You can provide any name for tagging while storing.
2. Restore a tagged ROM's app data and its latest nandroid backup.
The nice side effect of this is that you have complete environments you have created nicely bookmarked with easy to understand names and version numbers, ready to be restored easily.
Requirements:
1. Two partitions in order: fat32, ext2/3
2. cyanogen's recovery image 1.4. 1.3.1 will not work with V1.0.
3. Attached script called switchrom.txt downloaded and stored in folder /system/sd/ and renamed as switchrom.sh
Usage:
1. Boot into recovery using Home + End buttons together.
2. To bookmark and tag current ROM,
Go into console with Alt+X (or do adb shell from PC)
mount /system/sd
sh /system/sd/switchrom.sh -s <name>
e.g.
I am backing up soulife-1.2.3 with
sh /system/sd/switchrom.sh -s soulife-1.2.3
3. To restore a ROM,
Go into console with Alt+X (or do 'adb shell' from PC)
mount /system/sd
sh /system/sd/switchrom.sh -r
It will give you a list of available ROMs to restore and you can choose the one you want to restore using the corresponding number.
e.g.
I am restoring soulife-roger-new-3.9.1-latest with
Code:
sh /system/sd/switchrom.sh -r
1. JACMyTouchSkiV2-mod
2. JACxROM-1.3r3
3. cm-3.9.7-best-setup
4. drizzy-hero-2.8-best
5. soulife-ion-1.2.3-mod
6. soulife-roger-new-3.9.1-latest
Choose a ROM (type in the number and press enter)...6
Restoring ROM soulife-roger-new-3.9.1-latest, proceed? (y/n) y
Cleaning up /system/sd ...
Restoring soulife-roger-new-3.9.1-latest app data in /system/sd ...
Restoring nandroid backup...
Done restoring the ROM soulife-roger-new-3.9.1-latest.
Note that no extra steps are necessary. No wipe! No nandroid restore!
Note that options have changed since last version. Make sure to read the help with '-h' or '--help' option. Compression (-c option) is supported for both the apps partition and the nandroid but the way it is done in nandroid is dumb and takes like 17 minutes, so I would not recommend it at this time but you can definitely try it. I will post patches for nandroid script to fix that.
Code:
# sh /system/sd/switchrom.sh -h
Usage: /system/sd/switchrom.sh OPTIONS <rom_name>
Options are:
-h --help
-c --compress, only used with -s
-d --delete
-l --list
-r --restore
-s --store
-v --version
Always specify options as separate words
e.g. -c -r instead of -cr. Its required!
Don't use blanks or special characetrs in rom_name.
Compress will take longer but image will be smaller.
<rom_name> is optional with -r and -d. Choose from a list.
NOTES:
Note that this is not storing the whole backup of your EXT2/3 partition. This is just storing app* and dalv* folders needed to restore the ROM behavior, apps and settings only. If you wipe your EXT2/3 partition with a formatter or manually with 'rm -rf /system/sd/*', you will loose everything on that partition and won't get it back from this backup. This backup will only restore app* and dalv* folder.
It was reported that certain versions of 'adb' hangs in the sub-shell created and it doesn't pass through the commands that are typed. Make sure to upgrade the SDK to 1.5r3.

Awesome work, I'll try this out on my next rom switch. Can't ever have too many scripts I say.

added to my collection of scripts

This may sound like a silly question but please forgive me as I have not yet flashed the haykuro spl.
Once you've flashed the new spl, instead of flashing the update.zip of the cyanogen rom, can't you use nandroid restore? Or will that restore the previous spl as well (in my case HARD SPL)?
I ask because I would like to try the spl, but I'm so comfortable with my rom and settings that I would hate to wipe just to try Hero which is still in development. Call me crazy, but I like stable and finished builds. But I am curious and with a lot of time on my hands but not so much that I'm willing to lose everything just to try something that I'm not going to keep.
With this script, it would make it so much easier and would allow us to switch roms on the fly... but would it work from Hero builds and non-Hero builds?

I don't think I know enough about the SPL image contents to comment on this. But as far as I know SPL is not touched by nandroid restore. I upgraded the radio and SPL (haykuro) first, and then went with updating my ROM. I will never flash radio and SPL unless and until I really need to.
This script is just taking the pain out of switching between ROMs (whether Hero or Cyano or official) and nicely organizes your ROM backups. So, to answer your question:
would it work from Hero builds and non-Hero builds?
Click to expand...
Click to collapse
Yes. It would! I have switched between drizzy's Hero ROM and JACMyTouchSki (my favorite) many times using this. The restore is perfect!

Binary100100 said:
Once you've flashed the new spl, instead of flashing the update.zip of the cyanogen rom, can't you use nandroid restore? Or will that restore the previous spl as well (in my case HARD SPL)?
Click to expand...
Click to collapse
Considering the most amount of bricks come from radio/spl updates, I dont think this script would integrate backing up and restoring them. Same reason why rom's themselves dont include the latest radio/spl in the update.zip when it is required by the rom.

rondey- said:
Considering the most amount of bricks come from radio/spl updates, I dont think this script would integrate backing up and restoring them. Same reason why rom's themselves dont include the latest radio/spl in the update.zip when it is required by the rom.
Click to expand...
Click to collapse
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?

Binary100100 said:
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?
Click to expand...
Click to collapse
Make sure you use labels which don't have whitespace or other special characters in the name like use Cyan-3.9 instead of "Cyan 3.9". I don't think script likes it much at this time. I need to fix that.

Binary100100 said:
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?
Click to expand...
Click to collapse
The only difference between this and a "typical" nandroid restore should just be that it copies your ext2/3/4 partition for the app data. It wasnt listed anywhere that it would backup/restore your spl/radio.
Prior to flashing the haykuro spl I made a nandroid backup of the cyanogen rom I was using. I tested a hero rom and restored a nandroid backup of the cyanogen rom I was running and the new radio/spl were in place.

I think you need to dump all of mtd6ro and extract radio/spl by hand if you need to. Nandroid doesn't touch either of them.

rondey- said:
Prior to flashing the haykuro spl I made a nandroid backup of the cyanogen rom I was using. I tested a hero rom and restored a nandroid backup of the cyanogen rom I was running and the new radio/spl were in place.
Click to expand...
Click to collapse
Sweet! This was the exact answer that I was hoping and searching for for hours. Thank you very much. I've been getting guesses and theories this whole time and I knew someone out there just had to have personal experience with it. Thank you.

WOW amazing script!! just downloaded and used it
works very well!! can't wait to see what else you can do with it.

the perfect addition to a world that includes xda devs. nice work!

This may a dumb question, but why is it necessary to do this if your app data is still sitting on your ext partition, isnt it going to look for apps there anyway if you have apps2sd setup automatically like in a CM rom?
Cheers

The current version of nandroid lets you switch
Between backups, but not all options are yet connected to the UI.
devsk said:
Currently,
A. nandroid backups do not contain the a2sd app folders.
B. nandroid backups are not tagged but instead are time stamp based, so if you forget you backed up your most stable ROM with all the setup done and apps installed at 11:01pm on Friday, you will have tough time getting it back.
It has been painful to say the least to jump between ROMs.
This script does two things:
1. Store and tag a ROM's nandroid backup and its apps data. You can provide any name for tagging while storing.
2. Restore a tagged ROM's app data and make its nandroid backup the latest so that the recovery console can restore from it.
The nice side effect of this is that you have complete environments you have created nicely bookmarked with easy to understand names and version numbers, ready to be restored easily. Eventually, this should be part of the nandroid in recovery image itself.
Requirements:
cyanogen's recovery image 1.3.1
attached script (only txt extension is allowed) downloaded to /sdcard/switchrom.sh
Usage:
1. Boot into recovery using Home + End buttons together.
2. To bookmark and tag current ROM,
Do a nandroid backup first
Go into console with Alt+X (or do adb shell from PC)
mount /sdcard
sh /sdcard/switchrom.sh store <name>
e.g.
I am backing up soulife-1.2.3 with
sh /sdcard/switchrom.sh store soulife-1.2.3
3. To restore a ROM,
Go into console with Alt+X (or do 'adb shell' from PC)
mount /sdcard
sh /sdcard/switchrom.sh restore <name>
e.g.
I am restoring soulife-1.2.3 with
sh /sdcard/switchrom.sh restore soulife-1.2.3
Go back to recovery screen (by typing 'recovery' on the shell prompt if you are on console)
Alt+w to wipe
Do a nandroid restore from latest backup
I have tested this script with cyanogen 3.9, soulife 1.2.3, drizzy's hero and JACMyTouchSki.
Click to expand...
Click to collapse

I must be missing something...
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
I usually keep my phone backed up using backup for root users. So I just restore all my text messages and settings from the SD card and that is it.
I guess that is more typing, but to me each individual command it simpler.

mookie3three said:
This may a dumb question, but why is it necessary to do this if your app data is still sitting on your ext partition, isnt it going to look for apps there anyway if you have apps2sd setup automatically like in a CM rom?
Cheers
Click to expand...
Click to collapse
Apps data is not portable between ROMs. You need to clean it up otherwise expect random FCs.

ccunningham83 said:
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
Click to expand...
Click to collapse
And lose all that you did with your current ROM. I think you did not get the point of this script.... This is for people who have setup their phone well with a ROM and don't want to lose its goodness but still want to test other ROMs and possibly have a couple of them on their phone which they can switch to & from.

ccunningham83 said:
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
I usually keep my phone backed up using backup for root users. So I just restore all my text messages and settings from the SD card and that is it.
I guess that is more typing, but to me each individual command it simpler.
Click to expand...
Click to collapse
The thing you are missing is that many apps do not have an option to export their settings, nor do they store them in an easily accessible place. Even if you manage to pull their settings off /data/data/ folders, you still have problems with restoring them. First off, you have to worry about their Linux permissions since they don't get preserved on the Fat32 partition. Second, simply pushing back the setting folders won't work for apps that use SQLlite database to store account info, so you're stuck with re-entering everything manually.
Take K9 Mail for example. I have 4 accounts (both IMAP and POP3) that I have to set up every time I wipe my phone or reformat the Ext partition. Same with progress on most games. A tar of the entire Ext partition combined with a Nandroid image resolves most of these issues.

I get an error during backup.
I take a nandroid backup, enter recovery terminal, type in "mount /sdcard" enter "sh /sdcard/switchrom.sh store lastramjet" type in yes at the confirmation prompt and the script starts it's magic.
However, after the "moving nandroid (or something)" I get an error saying "Cannot umount /sdcard device/resource in use/busy". After that I get a successfully bookmarked the backup message.
Not sure if this matters, but just wanted to let you know

[UTIL] sdparted v0.6 - easy sdcard partitioning, upgrading to ext3/4

this script automates the process of partitioning a sdcard on your android device. it should work fine for all sizes/types of sdcards, but since i can't test all sizes/types of sdcards, we'll have to see.
if you are running into problems with the script, post the log file(located at /data/sdparted.log) when asking for help.
big ups to cyanogen (parted and upgrade_fs) and Denkai (upgrading to ext4).
i welcome all comments, questions & suggestions, related to the script. this is NOT a general q&a.
read the ENTIRE post BEFORE asking questions, please.
to manually partition your sdcard see my other thread.
DISCLAIMER: i take no responsibility for what happens to you, your phone, sdcard, data, sanity, etc if you use this script. remember to backup your sdcard to your pc before you begin. this script has the potential to COMPLETELY WIPE your sdcard!
##########################
shameless promotion:
sdparted can also be found in amon_ra's recovery and natalic's android toolkit.​
##########################
features:
-automated partition of sdcard using parted
-upgrading to ext3/ext4
-downgrading to ext2
-interactive mode
-supports units (M and G)
-supports floating point partition sizes (ie. .5G=512M)
-automatic logging to /data/sdparted.log​
##########################
requirements:
android phone with proper utilities(cm-recovery-1.4, amon_ra's recovery)
sdcard <--class 6 recommended(adata makes good ones...they max out the g1 hw in terms of speed)
adb
fingies​
##########################
Code:
sdparted v0.6 created by 51dusty
if you use this script in your work, please give some credit. thanks.
requirements: cm-recovery-v1.4
usage: sdparted [options]
options:
--fatsize|-fs SIZE[MG] set the size of the fat32 partition to <SIZE>.
default=total sdcard size - (ext + swap)
--extsize|-es SIZE[MG] set the size of the ext partition to <SIZE>.
default=512M
--swapsize|-ss SIZE[MG] set the size of the swap partition to <SIZE>.
if set to 0, no swap partition will be created.
default=32M
--extfs|-efs TYPE set the filesystem of ext partition to <TYPE>.
valid types=ext2, ext3, ext4
default=ext2
--upgradefs|-ufs TYPE upgrades existing ext partition to <TYPE>.
this operation will NOT wipe your sdcard and
cannot be used with any partition creation options.
valid types=ext3, ext4
--downgradefs|-dfs TYPE downgrades existing ext partition to <TYPE>.
this operation will NOT wipe your sdcard and
cannot be used with any partition creation options.
valid types=ext2
--interactive|-i interactive mode
--help|-h display this help
--printonly|-po display sdcard information
--silent|-s do not prompt user, not even initial warning.
examples:
sdparted creates swap=32M ext2=512M fat32=remaining free space
sdparted -efs ext4 creates swap=32M ext4=512M fat32=remaining free space
sdparted -fs 1.5G -efs ext3 creates swap=32M ext3=512M fat32=1536M
sdparted -es 256M -ss 0 creates no swap ext2=256M fat32=remaining free space
sdparted -ufs ext4 upgrades ext partition to ext4
##########################
need to backup your ext partition?
the following commands will backup/restore your ext partition to/from a folder named sdbackup in your current directory. these must be run while phone is booted, not recovery.
to backup your ext partition: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd
##########################
to run from computer:
1. download sdparted.txt below to computer
2. connect g1 via usb
3. boot into cm-recovery-v1.4, goto console(alt-x)
4. at your windows cmd prompt type: adb push /path-to/sdparted.txt /sbin/sdparted
5. then type: adb shell chmod 755 /sbin/sdparted
6. to run type adb shell and hit enter.
7. you can now run script (ie. sdparted -efs ext4).​
to run w/o computer:
1. download sdparted.txt below to root of sdcard. (get downloadcrutch if needed*thnx lycoln)
2. boot into cm-recovery-v1.4, goto console(alt-x)
3. at # prompt type: mount /sdcard
4. then, mv /sdcard/sdparted.txt /sbin/sdparted
5. then, chmod 755 /sbin/sdparted
6. you can now run script (ie. sdparted -efs ext4).​
you CANNOT run this script from terminal app.
##########################
if the script crashes or you receive an error:
immediately pull the log to your computer(using adb pull /data/sdparted.log sdparted.log), b/c the log will not be there after a reboot. send me the log when reporting errors, please.
##########################
changelog:
changes in v0.6
*new feature=interactive mode
*tweak user abort function for those with itchy fingers
changes in v0.5.3
*remove initial warning(kinda pointless if there is another before you wipe)
*clean partition table handling code
*general code cleanup/consolidation in anticipation of new features
changes in v0.5.2
*handling of "partition 1 may not be aligned to cylinder boundaries", fixing "sh: -gt: argument expected" and related phenomena (ie. sdparted trying to partition using negative numbers ) reported by midtoad
changes in v0.5.1
*slight change to logging(so slight it only gets a .1), fixing "/sbin/sdparted: line 5: .//sbin/sdparted: not found"
changes in v0.5
*new feature=floating point partition sizes
*new feature=downgrade ext filesystem (ext3->ext2 ONLY, for now)
*fix some crappy programming
changes in v0.4
*unmount all partitions before operations, fixing "Error: Partition(s) on /dev/block/mmcblk0 are being used".
*remove some useless code
changes in v0.3
*new feature=logging
*new feature=units
*new feature=print card info
changes in v0.2
*add cm-r-v1.4 check to prevent running in 1.3.1
##########################
todo items:
-downgradefs support for ext4
##########################

Excellent!
One of the easiest things Ive done in a while. Worked great!

great.
i'm new to android, so i have a question.
I'm guessing when you go to settings and eject SD card, it only unmounts the FAT32 partition, right?
So does that mean the only safe way to eject the card is shutting down?
great job!

SyXbiT said:
great.
i'm new to android, so i have a question.
I'm guessing when you go to settings and eject SD card, it only unmounts the FAT32 partition, right?
So does that mean the only safe way to eject the card is shutting down?
great job!
Click to expand...
Click to collapse
That depends which ROM you are running and how it's set up. CyanogenMod for example, will automatically use the Ext partition for Apps-to-SD if it finds one. Ejecting a card while the phone is using it as part of its internal memory would be a Bad Thing™.
If you are running the stock firmware, it would be safe to remove the card after ejecting it in settings.

Could anyone at their convenience post directions for using this with console,
and where to place text attached? Funny, I've done this the manual way but don't know the simple things.
Thanks in advance for your work and patience. =)

Figured this one out!

Can you tell me how exactly to run this script? I ran this in recovery and i get sdparted not found.

sacredsoul said:
Can you tell me how exactly to run this script? I ran this in recovery and i get sdparted not found.
Click to expand...
Click to collapse
where did you place the file? did you run chmod?

excellent! Great job dusty

sacredsoul, Make sure you have the latest Cyanogen's Recovery Image, which I used 1.4. I got the same error using 1.31. I then updated to 1.4 and it worked perfectly. great Post 51dusty.

i am tryin to do this...hw do i get in recovery mode and wat exactly im i typin?..i hav a 4gig

Just wanted to chime in and say this script worked beautifully for me on a 16gb card.
Thanks!

I don't get it, am I mounting first, placing the file on the SD, then rebooting into recovery? The instructions make it sound as if I can just boot into console and pull it off my machine. Many people might find that confusing.

ctheory83 said:
I don't get it, am I mounting first, placing the file on the SD, then rebooting into recovery?
Click to expand...
Click to collapse
...i don't say to mount anything.
ctheory83 said:
The instructions make it sound as if I can just boot into console and pull it off my machine.
Click to expand...
Click to collapse
actually, you can...but you push instead.
51dusty said:
to install from computer, download, boot into cm-recovery-v1.4, goto console, and adb push /path-to/sdparted.txt /sbin/sdparted, then adb shell chmod 755 /sbin/sdparted. you can now run the script from adb(in recovery) or from g1 recovery console.
Click to expand...
Click to collapse
i will edit post to make installation less "confusing"...done.

Hey dusty i been struggling with this for like a week now and finally decided to post! so i got the adb thing running on my pc, windows 32-bit and it finds my device when i put the command "adb devices", so that far im fine but then your instructions tell us to boot the phone into recovery console and the type "adb shell" the result comes up "no adb found", at this point i have tried it with my phone plugged into the pc and unplugged without mounting it from the G1... please help what am i doing wrong im really confused! thanks!

The script is great i finally figured it out how to work this thing, but i just a bit of an issue now, when i keep installing apps my internal storage is also getting reduced a bit, i have installed about 100mb of apps and my internal storage reduced to 67 from 70mb, i have already cleared cache, using the app to move it to sd card, and also turned my phone off and took out the battery and rebooted, but its standing at 67mb... does this possibly have anything to do with protected apps??? please help!!

adb not found
hi,
it says adb not found, what am i doing wrong ?.

so my problem is that im not quite sure on what you mean by the path in the following command
adb push /path-to/sdparted.txt /sbin/sdparted
i know that you mean where ever the file is located but, for instance i just put mine in the c drive, so it should be adb push /c drive/sdparted.txt /sbin/sdparted
what is the correct way that should look?
edit: ok so i found my problem, i tried to install it from the adb shell, that was wrong, and this is the string in windows cmd i used for sdparted located just on the c drive
"adb push %cd%\sdparted.txt /sbin/sdparted" it then says the speed it was written, etc. does that mean it is correctly installed? from here, im not too sure how to go about setting up my partitions, again im very new to this.

you can now run the script from adb(in recovery) or from g1 recovery console.
Click to expand...
Click to collapse
Everything went okay, only the last stap with running from adb i dont understand.
What command is that ?

CoopZor said:
Everything went okay, only the last stap with running from adb i dont understand.
What command is that ?
Click to expand...
Click to collapse
i have edited first post to clarify how to run.
to run, from adb:
1. boot into cm-recovery-v1.4, goto console(alt-x)
2. at windows prompt, type adb shell and hit enter.
3. once connected via adb, you can now run script (ie. sdparted -efs ext4).
Click to expand...
Click to collapse

How to: Use 3.03.751.4's system.img without updating the hboot nor radio

So, I wanted to test HTC sense, but didn't want to brick my phone, use non official images nor change the SLP. There was a problem thou, the latest rom released in Taiwan has a big (153Mb) system.img, which is bigger than the 92Mb that the older SPL assign for the system partition, making it impossible to put the new system files in your phone without the new SPL. BUT!!! you can tell the kernel how to "partition" the NAND. Here is how to do it:
DISCLAIMER:
- This could brick your phone. Don't try it if u don't know what u're doing!!!! I hate seeing bricked phones.
- The steps come from my memory and my PC's history, so think before typing anything.
- This was done in a PVT 32A.
1. BACKUP WITH NANDROID!!!!
2. Get a working kernel. I compiled the "android-msm-2.6.27" with the 2.17.401.2_HTC_CH config. But lots of hardware didn't work, it was ok for me, I was just trying to see/feel, multitouch and the Sense UI.
3. Generate a boot.img from the kernel from point 1. and the 3.03.751.4's ramdisk:
This is for PVT 32A: (I think u only need to remove the base for 32B)
Code:
mkbootimg --base 0x19200000 --cmdline "no_console_suspend=1 mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata) " --kernel zImage --ramdisk boot.img-ramdisk.gz -o boot_bigmtd.img
4. Copy the system.img and boot_bigmtd.img to the sdcard.
5. Run fastboot to erase system, cache and userdata. ej: (I'm sure there are better ways to create yaffs file systems, mkfs.yaffs? , but I tried fastboot it worked and I didn't care)
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
6. Boot RA's recovery, or any other recovery that lets u unyaffs an image. You have to set the new SLP "partition" sizes, ej:
Code:
fastboot -c " mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata) " boot recovery-RA-magic-v1.2.3H.img
7. Mount system and sdcard. ej
Code:
$ adb shell mount /system
$ adb shell mount /sdcard
8. flash the boot image and unyaffs the system image.
Code:
$ adb shell
# flash_image boot /sdcard/[path to the boot_bigmtd.img]/boot_bigmtd.img
# cd /system
# unyaffs /sdcard/[path to the system.img]/system.img
# cd /
# sync
# umount /sdcard
# umount /system
9. Reboot! Give the phone some time to boot, mine did. but YMMV. I saw something weird during the boot, before the 3rd splash (the one loaded from system), the phone displayed residual garbage from what was displayed right before the previous shut down.
Drawbacks:
- Fastboot theoretically (not tested yet) could wrack your system, as it still thinks that the system size is 92Mb.
- You have to be careful not to destroy the data of any of the modified partitions, by writing into it without the good MTD table
- U still have to get all the hardware working. I didn't try, but easy to do, get the 3.03.751.4's kernel config, that should take care of most of the things.
For more info, see:
http://forum.xda-developers.com/showthread.php?t=542688
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

great article. I got 2 questions.
1. why did you build a new boot.img but not use the one comes with update?
2. after set the new SLP "partition" sizes, can I still restore with nandroid?
thank you.

Hi snakejoe,
I haven't tried it, but you can update the radio and a new (1.76.2007) Engineering spl, see:
http://forum.xda-developers.com/showthread.php?t=589722
Ps:
1. I don't remember why I tried a different kernel, but I guess that the shipped one should have worked unless the radio needed that kernel.
2. I didn't try to restore backup with nandroid, but it should work, as long as you load the rescue with the “right” partition sizes.

[Q]How to flash broadcom?

Hi,
i installed Shadow Hawk, but Wifi doesn´t work. It´s because of the Hyperion Kernel. I just don´t know how to "replace the broadcom module inside /system/etc/lib/modules". Because i used HTCDev(il) to unlock, i flash boot.img with fastboot. But how do i replace the broadcom module?
Please help!

Given your handset is S-OFF, either,
- Hard way :
Use android SDK adb to mount system RW and push module file :
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
adb pull c:\bcm4329.ko /system/lib/modules/bcm4329.ko
- Easy way :
Just use ES file explorer, enable root R/W mode and copy/paste bcm4329.ko into /system/lib/modules
And then reboot.

dmfr said:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
adb pull c:\bcm4329.ko /system/lib/modules/bcm4329.ko
And then reboot.
Click to expand...
Click to collapse
If you use adb, those are not the commands. Should be:
adb remount
adb push :\bcm4329.ko /system/lib/modules/bcm4329.ko
In your first line you were trying to mount a yaffs2 filesystem, when it's probably a ext4 one. The "remount" option will work regardless of the fs.
Ths second line is fairly obvious, you want to push the file to the rom, not pull it from there.
Also, if you S-ON and flashed the rom, the broadcom module was flashed, it's just boot.img that gets left out. This means that when you manualy flash boot.img with fastboot, you don't need to update anything else.
So: Check in system settings if you actually flashed the kernel. It must say "Hyperion V2.XXX", or whatever version was included. If it is, wifi must work, if not, you messed something up on the fastboot flash procedure.
Cheers

will try later, thank you.
ICS Quattro Rom worked including Wifi..
update:
working now.
"Please follow these steps in the same order (I'm shouting) :
1. Boot into recovery
2. Format System (not wipe option but format option !!!)
3. Format Data
4. Format Cache then Format Boot
5. Wipe Data/Factory reset (1st option in wipe/format menu)
6. Wipe Dalvik Cache
Next if you have some wiping utility like Full Wipe 1.5 Ext4 for Saga.zip...run that by selecting install zip from sd card and installing the zip...
7. Now install zip from sd card and flash the rom
8. If any kernel flash it as well
9. Now reboot (Note don't flash any tweaks like transparent notification except gapps if required)
10. Now setup your phone
11. Reboot into recovery
12. Now go into advanced fix permissions and then any tweaks you want (Note whether mentioned or not always wipe Dalvik Cache before installing tweak zip)
13. Voila everything would work perfect 100%.... "
did follow these instructions.
flashed boot.img
having a fast and stable rom now hopefully. ICS wasnt stable enough. especially browser.