Related
Well yea this should probably be posted somewhere else since is not only captivate related but anyways here it goes :
1st _ I set up all my things then before I stared theming did a nandroid backup , (using rom manager ) so when I decided to revert it only restored my system , not the rest , what did I miss ?
2nd this is related to metamorph , I noticed I had to apply morphs twice for them to apply and sometimes phone would reboot and only half was morphed .. I know I know classic metamorph behavior ..
my previous phone was a Motorola Milestone not only the nandroid back up method was 'more detailed ' but we had a 'metamorph script' using the file called 'zip' inside mm's apk we could run this from inside the recovery witch basically eliminated all reboot problems or other problems associated to theming a file 'in use' ot also eliminated the need for xml file , anyways if any dev can have alook at that 'open recovery' its how it called on the milestone with its built in script ...
here is the link :
http://www.multiupload.com/KHQCHFRT74
and here is the dev's site :
http://groupoften.wordpress.com/
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
dynamite1985 said:
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
Click to expand...
Click to collapse
Is that meant to work for the milestone? I dont see milestone listed on supported devices.
Is this the kitchen you are referring to?
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
dynamite1985 said:
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
Click to expand...
Click to collapse
Sorry buddy. I ain't a developer. Try sending a PM to Luca or Kabaldan or Feeyo ( on cronosproject ) and see if they can help.
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
kabaldan said:
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
Click to expand...
Click to collapse
so I'm a little confused...
it seems to me that I should be compiling the kernal with the 2nd-init attack, which confuses me because of the BL issue. or is the stock boot.img used with a customized system.img?
i've tried the latter part, and gotten the noted error.
Introduction
Okay, so there are lots of good boot animations out there but you can only choose one? Not good enough I say!
So, here I provide a script that will allow you to have multiple boot animations that are randomly selected each time you boot you phone!
This script was originally provided by Nighthound here many moons ago but I've since adapted it to my Nexus One ROM (Kang-o-rama) and now for the LG Star.
This version should be compatible with *all* custom ROM's LG P990, P999 as well as other manufactures and ROM's with init.d support.Installation
It's pretty simple to install and very little configuration is required. Simply download the attached .zip file, install it from recovery and you're all set!
Download zip file below
Install zip from SD Card in recovery
Copy any boot animation .zip you want to use to /data/local/bootanimations/
Give each boot animation .zip file a unique name!
Reboot and enjoy
Hit 'Thanks' below
The 'bootanimations' directory will be created for you the first time you boot after applying this update zip and then you can download any suitable boot animation you want at any time and just place it in /data/local/bootanimations/ (make sure it is not called 'bootanimation.zip' to avoid conflicts). Easy as pie.Animation Authors
To help our user community I have two suggestions:
Please let users know in your thread of this script; and,
Put a note in about unique file names so users don't get confused
Have fun kids and don't run with scissors, be safe...
haha nice! I'll check it out in a few! Thanks for the effort tho!
edit:
Ok installed it and installed some boot animations i like and it works like a charm thanks!
Thank you! Like custom bootanimations, so this is something I can use!
ARGHHHH, what files does this replace as after installing this my phone just reboots just after the lock screen shows.
Although it does show me MANY random bootscreen now.
i've placed over 10 bootanims, everything is working as is should be
thnx m8
stevvie said:
ARGHHHH, what files does this replace as after installing this my phone just reboots just after the lock screen shows.
Although it does show me MANY random bootscreen now.
Click to expand...
Click to collapse
It just adds one file called 10bootanimations to /system/etc/init.d/ - you can of course remove this if you like.
It won't actually show *any* random boot animations until you add them so I'm not sure I've understood your problem correctly.
I'm trying to using this on my LG G2x running CM7 and nothing happens ... I've copied a few bootanimations to data/local/bootanimations ... and nothing at all
I've confirmed that the file got flashed to system/etc/init.d ... is there a way i can confirm if it is actually running etc?
Another thing of importance perhaps, the first time i rebooted after flashing the attached zip through recovery, it didn't create the folder at data/local/bootanimations like the script says it should ...
any thoughts?
Nice little tool, thx.
ridicool said:
I'm trying to using this on my LG G2x running CM7 and nothing happens ... I've copied a few bootanimations to data/local/bootanimations ... and nothing at all
I've confirmed that the file got flashed to system/etc/init.d ... is there a way i can confirm if it is actually running etc?
Another thing of importance perhaps, the first time i rebooted after flashing the attached zip through recovery, it didn't create the folder at data/local/bootanimations like the script says it should ...
any thoughts?
Click to expand...
Click to collapse
I'm not sure, is the CM7 processing init.d? Logcat at boot will tell you, the script should launch very early in the boot process and will write to the main log.
djmcnz said:
I'm not sure, is the CM7 processing init.d? Logcat at boot will tell you, the script should launch very early in the boot process and will write to the main log.
Click to expand...
Click to collapse
I think you're right because on the logcat, there is no mention of randombootanimations ... no one over at cyanogenmod answered when i asked if it was a bug that init.d wasn't being processed ...
anywyas, i'll keep this and keep giving it a shot and eventually it will work
This is a guide that shows you how to dual boot multiple android ROMs, and it's possible that these ROMs have different android versions
I'll be using boot manager application in this guide. It's not my app, I didn't develop it and I didn't help in developing it in any way.
The application doesn't touch you internal memory at all. It just makes .img files for the system, data, cashe and boot. It also makes a .android_secure folder.
So any change made will be in the SDcard not in the Internal memory.
That's enough talking, now here are the steps for installing a ROM and booting to it. But before you do anything, make a Nandroid backup (just in case if something goes wrong)
1- Open market (play store) and download Boot manager (lite or pro, but I will be using the lite version in this guide)
2- Open the app. It will make the first time configuration in which it will download about 3~4 MBs.
3- [IMPORTANT !!] Setup your phone ROM. This creates a boot image file for your current ROM so you can boot back again to your original ROM.
4- After that, swipe to go to the first ROM slot. Press install zip button, choose your ROM's zip file location, then check the three boxes (system, data & cashe). Then press okay, then choose which file system you will be using.
Now it's creating files for your ROM inside /SDcard/BootManager/rom1.
You can see the progress in the notification dropdown menu. Try not to use your phone while installing because it will be very slow and laggy.
5- Now it's time to install gapps or any other mod you want to install. Do the same steps as the ROM installation but this time don't check any box. If your ROM doesn't include gapps then you MUST install it as boot manager needs to check your license.
6- Now you can boot to the installed ROM. JUST press boot ROM
The booting process will probably take more time than usual. That's normal don't worry about it.
OK now you're on a SDcard ROM and you want to go back to your phone (original) ROM. Just open boot manager, swipe to phone ROM then press boot ROM. It's that simple
Some problems I had:
When I wanted to go back to my phone ROM, it doesn't boot, it just open the recovery and it doesn't want to reboot properly.
Solution:
Make an advanced restore for the system from the recovery then boot. If it didn't work then make another advanced restore for boot. That's the only solution I have found till now.
Tips and Tricks:
1- If the performance is slow, overclock the device.
2- Use SDcard booster, it's found on the play store.
3- Also use swapper, also found on play store.
4- You can also edit some details, as the ROM and kernel name and screenshots.
5- If you were using the lite version you WILL find the paid one in the SDcard ROMs. But don't be happy as it won't open. Just uninstall it and then install the lite version again from the play store.
6- If you are like me, in a country in which billing in android market is disabled or you just don't want to pay for the pro version, do the following:
Although the lite version has only one rom slot but it creates 5 folders rom1, rom2,.... etc
And it only creates the files in the rom1 folder
Let's say for example you are running CM7 as your daily driver and you want rom1 to be LeWaOS and Rom2 to be CM9 KANG.
It's quite simple, first install CM9 normally, it will be installed to Rom1 folder. Then copy every file in that folder to rom2 folder and delete the contents of .android_secure folder in rom1, then install LeWaOS normally.
If you want to boot into LeWaOS u can boot normally using boot manager. If you want cm9 then copy the files inside Rom2 folder back to Rom1 then boot normally through boot manager
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last time I tried ROM manager, it broke my "phone" ROM, so I had to reflash
nejc121 said:
Last time I tried ROM manager, it broke my "phone" ROM, so I had to reflash
Click to expand...
Click to collapse
Me too, but it happened to me in an older version. The current one works fine for me except the part when I go back to my phone ROM.
Sent from my still alive, ICS capable HTC Wildfire.
I haven't used it for ages, I bought it months ago but imo its simpler, the rom runs a little smoother, its less buggy and doesn't take up as much room on your sd card just to do a nandroid of every rom, then just switch them that way. Unless you'd rather have the novelty factor of using an App to do it.
A few things I noticed was it wouldn't work on cm7 no matter what I did, even with support from the developer (that may be fixed now though) on a sense based rom it worked first time everytime so if anyone has a problem with it not writing on the images switch your main rom to a sense based one.
It changes the boot path to direct it to the sd card so if you get stuck on the splash screen simply booting into recovery and advanced restoring the boot image should put things right again, as far as I know it doesn't touch the system partition so you shouldn't need to restore that. (saves a few minutes)
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
I haven't used it for ages, I bought it months ago but imo its simpler, the rom runs a little smoother, its less buggy and doesn't take up as much room on your sd card just to do a nandroid of every rom, then just switch them that way. Unless you'd rather have the novelty factor of using an App to do it.
A few things I noticed was it wouldn't work on cm7 no matter what I did, even with support from the developer (that may be fixed now though) on a sense based rom it worked first time everytime so if anyone has a problem with it not writing on the images switch your main rom to a sense based one.
It changes the boot path to direct it to the sd card so if you get stuck on the splash screen simply booting into recovery and advanced restoring the boot image should put things right again, as far as I know it doesn't touch the system partition so you shouldn't need to restore that. (saves a few minutes)
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I already know that it doesn't touch the system partition and I tried restoring boot only but it didn't reboot. I had to restore system also. It's not a logical solution but it works for me
And sometimes restoring the system only works too
My mobile must be always different than other's mobiles I don't know why but it does
Sent from my still alive, ICS capable HTC Wildfire.
If you are like me, in a country in which billing in android market is disabled or you just don't want to pay for the pro version, do the following:
Although the lite version has only one rom slot but it creates 5 folders rom1, rom2,.... etc
And it only creates the files in the rom1 folder
Let's say for example you are running CM7 as your daily driver and you want rom1 to be LeWaOS and Rom2 to be CM9 KANG.
It's quite simple, first install CM9 normally, it will be installed to Rom1 folder. Then copy every file in that folder to rom2 folder and delete the contents of .android_secure folder in rom1, then install LeWaOS normally.
If you want to boot into LeWaOS u can boot normally using boot manager. If you want cm9 then copy the files inside Rom2 folder back to Rom1 then boot normally through boot manager
lo2ay said:
If you are like me, in a country in which billing in android market is disabled or you just don't want to pay for the pro version, do the following:
Although the lite version has only one rom slot but it creates 5 folders rom1, rom2,.... etc
And it only creates the files in the rom1 folder
Let's say for example you are running CM7 as your daily driver and you want rom1 to be LeWaOS and Rom2 to be CM9 KANG.
It's quite simple, first install CM9 normally, it will be installed to Rom1 folder. Then copy every file in that folder to rom2 folder and delete the contents of .android_secure folder in rom1, then install LeWaOS normally.
If you want to boot into LeWaOS u can boot normally using boot manager. If you want cm9 then copy the files inside Rom2 folder back to Rom1 then boot normally through boot manager
Click to expand...
Click to collapse
Thanks for the guide...it is working fine...no issues in switching between Roms..
Scratch was right..my phone rom is Rempuzzle and Sd card Rom is Lewa..Since Rempuzzle is a sense Rom ..it didnt give me any sort of pain...
Those who wants to try take the base rom as a Sense and then try experimenting...
Bye bye good nite...
Shiv Prajapati said:
Thanks for the guide...it is working fine...no issues in switching between Roms..
Scratch was right..my phone rom is Rempuzzle and Sd card Rom is Lewa..Since Rempuzzle is a sense Rom ..it didnt give me any sort of pain...
Those who wants to try take the base rom as a Sense and then try experimenting...
Bye bye good nite...
Click to expand...
Click to collapse
I'm on cm7 and it works fine except when I want to go back to the phone Rom. I have to make an advanced restore for boot and system first
Sent from my still alive, ICS capable HTC Wildfire.
So if it doesn't touch the system, i suppose there is no problem for people with custom mtd partitions? (Due to boot a rom, installing bravo-boot.zip is required)
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
LucidSomnia said:
So if it doesn't touch the system, i suppose there is no problem for people with custom mtd partitions? (Due to boot a rom, installing bravo-boot.zip is required)
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It creates a new system.img 250mb on the sd card, not sure if you can physically change that but your original mtd should be fine.
Why don't you test it out?
i didn't use mtd because i had to use sense as a base just to get the app to work, as previously mentioned i have no need for this app now, nandroids work just fine.
Sent from my HTC Wildfire using xda premium
LucidSomnia said:
So if it doesn't touch the system, i suppose there is no problem for people with custom mtd partitions? (Due to boot a rom, installing bravo-boot.zip is required)
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I'm using custom MTD partitions and can confirm that there are no problems with using this.
Primary ROM is CM7.2 and secondary is CM9, only issue is that when going back to primary, you need to do advanced restore of system.
I must say the following.
A few days ago I encountered another problem while returning back to the phone rom, in my case it's CM7. Some of my apps got deleted. I don't know what caused or why did it happen. They were about 4 or 5 apps. They weren't uninstalled completely as the data remained but the app itself got deleted.
Sent from my CM7 powered Egyptian HTC Wildfire.
my phone refuses to boot in the sdrom.. i have tried both cm7 and sense rom as base... i have tried installing cm7, cm9, and sense rom on sd rom slot.. i am using lite version... logcat attached...
saadislam said:
my phone refuses to boot in the sdrom.. i have tried both cm7 and sense rom as base... i have tried installing cm7, cm9, and sense rom on sd rom slot.. i am using lite version... logcat attached...
Click to expand...
Click to collapse
having the same problem.having Rempuzzle as a phone ROM and tried the nexus cm7.2 ROM as sd ROM.but when I press boot to ROM it only gives access to root but then nothing but when I reboot manually it was locked into fastboot.had to recover my ROM from nandroid.
Welcome to the end of your life, hail the oceanborn
FGOD said:
having the same problem.having Rempuzzle as a phone ROM and tried the nexus cm7.2 ROM as sd ROM.but when I press boot to ROM it only gives access to root but then nothing but when I reboot manually it was locked into fastboot.had to recover my ROM from nandroid.
Welcome to the end of your life, hail the oceanborn
Click to expand...
Click to collapse
Facing the same problem. Any working solution for this?
ak0r said:
Facing the same problem. Any working solution for this?
Click to expand...
Click to collapse
Guess not as nobody replies...
Welcome to the end of your life, hail the oceanborn
Hello!
I've downloaded the latest version of CyanogenMod 9 from android(dot)doshaska(dot)net/cm9
Because my phone is a bit damaged, I had to change the `init.mapphone_umts.rc` script in `/system/etc/2ndboot/ramdisk`
Here's my version (some things commented, some added): pastebin(dot)com/NZv307H9
About that "damage": some day (a few months ago), my phone just stopped working (bootloop); IIRC - it has had installed nadlabak's CM7.
After a few days, I've bring it back to life, but still sometimes (but rarely) weird things were happening: eg.I coudn't listen to the music, couldn't talk or had to restart it, because it just hanged.
Two days ago I thought to install a new version of Cyanogenmod into it.
CM10 didn't work at all (without modifications it was just hanging on Cyanogenmod's loading animation, and if I changed the `init.mapphone_umts.rc` (eg.just added a comment), it didn't start).
So I tried CM9; after changing the `init.mapphone(...)` script few times and manually running `mediaserver` using `adb` from my computer, it finally ran and opened the Android's launcher. Almost perfect.
I said `manually running mediaserver`, because it couldn't start automatically (`logcat` just displayed "Waiting for service media.audio_policy..." forever) and when I tried to add it into the `init.mapphone(...)` script, it didn't worked (there still were the "Waiting for service..." messages).
So, summing this long post:
- audio is not working (both: my music from SD card and those internal sounds in Android, like dialpad's sounds).
- `mediaserver` have to be run manually from `adb`
I've been trying to fix this for 2 days, but the only thing I did is just that the Android almost-successfully ran.
Here I also add a `AOL_main.ap.bin` log from that success run: pastebin(dot)com/bkFQ9GHg
BTW: I have a nandroid backup from that old Android version (before I upgraded it into CM9), and there the sound works (but eg.Google Play does not), so I have a double mess in my head :/
BTW 2: I know it's a bit difficult to help me (as you eg.cannot check some things by yourself and I write things a bit unclearly (I'm from Poland)), so if you need any logs or something, let me know and I'll upload it.
Ask around on the #milestone-modding irc channel. Maybe nadlabak and the others could help.
Ok, but how could I log there?
(I'm not good at IRC-things )
The easiest way is via THIS web-client.
Just type #milestone-modding to the Channels.
Ok, thanks
You should be more patient and stay logged to irc channel a bit longer while waiting for an answer .
The primary cause of your issue seems to be that the content of your phone's pds (or at least a part of it) has been deleted.
Did you intentionally deleted some files from /pds (or /config , which is just a symlink to /pds) in the past?
Do you have a back up of those files?
(Some of them - like e.g. /pds/bp_nvm/File_PDS_IMEI - are per phone specific [and signed] and can't be restored using the files from other devices.)