Related
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve
Wiping and backup problems have been fixed in CWM3 > 3.0.0.5. If you had trouble before, try again with ROM Manager. Try to flash the recovery at least twice before giving up, or use an alternate method below.
Ensure that "wipe recovery" option in ROM Manager settings is checked. There is no good reason to not have this checked. It should probably be the default. This will not affect your backups.
3.0.0.8 has fixed the SLCD problems. If you get the black screen with white bars, upgrade to 3.0.0.8.
Koush's official answer as to why you can't flash old .zip files with 3x.
Why you should upgrade to CWM 3 series from 2 series
CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME
ROM Manager won't work with 2 series anymore
support for journaling filesystems. Your data is safer.
pretty orange color
power down from recovery
better partitioning support
may be required for Cyanogenmod in the future. It is not required for the inc as of now.
Why you should not upgrade to CWM3 series
Fear of messing with recovery is not a good excuse
You want to install ROMs from ROM developers that use 2 year old technology and have refused to upgrade their zipping mechanisms (put pressure on them to change their installation scripts)
You like old ROMs that haven't been updated in ages
You are one of the few that the new recoveries don't work on. Ask and someone can probably help you get through this.
WHERE TO GET OLD VERSIONS OF CLOCKWORKMOD:
http://mirror1.kanged.net/recoveries/ - contains img files for all old versions
*http://dougpiston.com/?page_id=85 - contains PB31IMG for flashing through HBOOT, including 2.5.12 and 3.0.0.8. This is the easiest way to manually update recovery.
HOW TO INSTALL IMG FILES
***YOU SHOULD INSTALL THROUGH ROM MANGER IF AT ALL POSSIBLE. TRY TWICE IF IT DOESN'T WORK ON THE FIRST TRY***
Rename the image file you're interested in to recovery.img
OPTION1: ADB
Code:
C:\YOUR_ADB_DIR\>adb shell
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION2: Android Terminal from phone
Copy the recovery.img to the root of your sd card.
Code:
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION3: Use PB31IMG.zip
Download specific recoveries from dougpiston.com
If it is not available elsewhere, oll your own PB31IMG.zip
This is not as hard as you think. Download any recovery PB31IMG.zip, such as the one attached to this thread. Replace the recovery.img in the zip file with the one of the desired CWM recovery. Rename to PB31IMG.zip. Place in root of your SDCARD. Reboot into HBOOT. Install.
What to do if you have trouble with CWM3
Check partitions for errors
Try installing through ROM Manager, or installing through one of the alternate methods listed above
make sure wipe recovery is checked in ROM Manager settings.
make sure you have the latest version of ROM Manager. Check in the market.
How to manually wipe recovery partition.
The utility is present in CM7 builds. I cannot vouch for other ROMs. This can also be done easily through fastboot mechanisms, but afaik fastboot is not available for the incredible because there are not leaked engineering HBOOTs.
This should never need to be done except in extreme circumstances.
Code:
$su
$/system/bin/erase_image recovery
How to get into recovery manually w/out ROM Manager
Shut down your phone. Hold down volume down. Press power, keeping volume down held. This is HBOOT. Scroll down to recovery and push the power button again.
HTC Incredible Amend vs. Edify: How to get old ROMs working with CWMv3
Amend and Edify are scripting languages used to write the installation routines for .zip files, including ROMs. Amend is quite old, from the cupcake days, and as such does not have features necessary for modern ROMs. To simplify development, Koush removed amend support with the advent of CWMv3. He had announced that he was going to do this for months. Nonetheless, some older ROMs that are not actively developed anymore may be desirable, and many of these do not use the more modern edify scripting. There is a thread here on how to easily convert amend scripts to edify using amend2edify: http://forum.xda-developers.com/showthread.php?t=903598.
Other sources for help
IRC
#cyanogenmod or #koush - it is recommended you try the solutions noted in this thread first. Self initiative is important, but seek help if you need it.
Who are the people behind CWM:
koush is the primary developer, slayher and CUViper help adapt it to the incredible, I'm sure many others.
How to build Clockworkmod yourself:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
EDIT 2/27/11: This thread used to contain info regarding a custom build of CWM3006. It is still attached to this thread, but koush has upgraded CWM to 3008 which contains the 3006 fixes and more.
Click to expand...
Click to collapse
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
BrettApple said:
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
Click to expand...
Click to collapse
It is really odd, as I can install this version and backup/restore fine, then switch back to 3.0.0.5 and backup locks up consistently.
Its true re: the wiping bugs. It seems there's a lot more noise about the 3 series CWM than the 2 series, although I wonder if its just a lot more people are installing it and not quite understanding how cwm/hboot/cm7 interact. Hard to tease it apart.
I'm talking to koush and trying to get him to recompile it and make it official, regardless.
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
meazz1 said:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
Click to expand...
Click to collapse
Thats quite odd. Try reflashing a working recovery and then back to this one?
What ROM/Radio/Phone (inc slcd or amoled)?
You can also extract the recovery.img out of the zip file and flash it with adb or flash_image.
Let me know please, I'll pull it down if there's consistent problems.
dont pull it booted on my device and ROM.... i'll do some extensive testing and report back
Sounds like this is for AMOLED only
Side note, I looked at an SLCD Incredible today. Noticeable difference in screens. I will say that AMOLED is much brighter and produces better color than SLCD, but SLCD wins hands down in crispness.
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
right now with 3.0.0.5 if you flash via rom manager without a full wipe... chances are... you'll end up wiping and reinstalling because of fc issues
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
lllboredlll said:
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
Click to expand...
Click to collapse
1) I believe if a recovery doesn't show up in the clockworkmod available recoveries, it will not show the proper ROM Manager version. Flash 2.5.0.5 and you'll see the same effect.
2) Looking into this now.
3) That's good to hear! Thank you for testing this! This, coincidentally, is primarily how I use CWM as RM has not been stable/consistent for me in ages.
lllboredlll said:
ok
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
Click to expand...
Click to collapse
I hear what you're saying.
To get the hooks in place, install 3.0.0.5 first via ROM manager, then go into hboot and install this 3.0.0.6. ROM Manager still thinks you have 3005 and backup/etc. works.
I don't mean this to be production quality, but it should help bridge the gap until koush gets a new version out.
shoman24v said:
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
Click to expand...
Click to collapse
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more ***
No problem. RM still shows 3.0.0.5, but that's not a big deal. I still see the latest nightlies available from RM.
And, like I said, I never flash within RM.
Nor do I recommend that.
tdiman said:
EDIT 2/26/11: This information, as hoped, has been deprecated by the release of CWM 3.0.0.7. You should use that one, because CUViper and koush found more bugs re: the communication between ROM Manager and CWM, as well as the fixes noted below.
Click to expand...
Click to collapse
Just in case someone comes along late to the party, please note the above information added to the OP.
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
jdmba said:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no. thats not correct - i have restored a bunch without issues.
I updated to 3.0.0.5 a few weeks ago when it came out. All seems to work fine for me except I can't restore to a previous version to flash other Roms (well at least from Rom Manager). Many of the other Roms that are out right now are not Edify.
Sorry if this is the wrong thread to post this in.
I've googled changing the Roms to edify myself, but I'm kind of lazy and switching recoveries seemed like it would be the easier route.
I think koush has been trying to gently encourage app developers for months to change over.
If you search this forum you'll find older versions of cwm.
The version number is reporting fine for me..... and i Love the new look of the recovery. I'm missing the fast scrolling from the previous builds, other then that I love it
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
thelunchboxosu said:
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
Click to expand...
Click to collapse
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
I just replaced my Captivate with a refurb from AT&T. FWIW... the guys at the warranty replacement center were very nice and knowledgeable. I have everything backed up with TiBu, moved my pictures off and all that.
My old phone had existz KB1 kernal and of course voodoo file system. Should I put this phone in the same state before I copy pictures back and restore apps? I'm wondering because voodoo as I understand it converts the file system from RFS to whatever voodoo is. That would mean my backups have been converted too.
Also, exixtz kernal is KB1 and this phone came as KB2. Any problem reapplying that kernal which I was very happy with?
I did all this stuff so long ago I've forgotten all the little stuff!
No, shouldn't be a problem. The only difference in KB1AND KB2 is the kernel and modem. But, you have to root first. Here is what I'd do.
Root
Odin flash a kernel with CWM(I used a speedmod kernel)
Flash the kernel of choice from recovery
Restore your backup.
Converting to ext4is up to you. Your back up is not dependent on using rfs or ext4.
Thank you sir! Where in north GA? cold today isn't it.
Dalton area. And yes it is.
Bad start... it won't root
I've Super one click in the past but no go now... just waits for device
helps to put it in debugging mode
dumb question... I've never restored a tibu back up... I have the backup on my pc... where do I put it. Also tibu is complaining that I won't be able to restore due to "allow third party app" not being checked in applications but there is no where to check that?
Need Superoneclick to enable non market/3Rd party apps.
Put the folder labeled Titanium Backup on your internal SDcard. Open TiBu, menu/batch/restore missing apps.
I'm mostly posting these things now in case someone else is in the same boat I am and has to go through this.
Superoneclick worked. I was a little surprised I needed it as my old phone had this enabled from ATT.
Restored most everything although TiBu died 4 times. The only thing that did not restore right was Beautiful Widgets. Fought that. Still not completely right as I can't find the same widget I had for style... FWIW.. I had 93 apps... took over an hour. I now understand the paid version if I was a heavy ROM flasher.
I enabled 3e recovery with no sig required via Truesselo's method. It worked great.
Bluetooth re-paired without requiring a password... I thought that was odd.
Had to re-enter my wireless password. Expected that.
Still evaluating whether or not to reapply Plumb Bob's GPS fix.
Still haven't updated the kernal. A reply above recommended SpeedMod but that looks like an i9000 kernal.
All in all dinked around about 4 hours with it... much of it trying to remember what the heck to do and how to do it.
CWR won't work now... What to do
I've rooted and restored. Along the way I also ran Truesello's (sp?) 3e signature fix as I had done that before with no problems.
Today I was going to flash something and it booted into recovery 3e but it os blue, I thought it was orange before.
I selected reinstall packages and I get this error
E: Can't open /mnt/internal_sd/update.zip Installation aborted.
I'm just trying to get to where I can select the zip file I want to use. I know I've done it the past.
help please.
Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.
mrhaley30705 said:
Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.
Click to expand...
Click to collapse
Thanks for your replay... I was thinking I hope mrhaley replies... he seems to know his stuff! I have plumbbob's fix on the phone and was going to flash that. it is named PlumbBob-1.0-CWM-USA.zip. It is not giving me the secondary menus to get there. I don't have an update.zip on the phone. I seem to recall it was for rooting.
Like I said, the only other thing I've done is to run the fix to allow non-signed files.
When I flashed the fix and the kernal last time I was able to navigate and select them.
The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.
mrhaley30705 said:
The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.
Click to expand...
Click to collapse
Well whaddya know... I have a folder on my pc in my Android folder called CW and in it is an update.zip file and directions. Bread crumbs... gotta love'm.
Took your advice and installed it through ROM manager. Aaaand we have PlumbBob... 7/7 and 16 ft accuracy.
Still wondering about flashing the KB1 kernal over KB2 though... the phone is sluggish. I probably will in a bit though.
I just bought a Motorola Milestone from a friend with android 2.2.2 fryo already installed and running at 800mhz.
i was just wondering since this isnt exactly the latest rom, how easy is it to install a new rom (are they all ready to go, no weird stuff to install after?) and to go back to the current rom just in case.
it also already has been rooted.
it is very easy. does the phone already have an open recovery installed on it?
dont know really.. i have ROM Manager installed, believe this also contains backup thingy like NANdroid?
Well if you have clockwork recovery already installed just put the custom rom file in your sd card and boot in to recovery then wipe, install zip from sd, pick the rom, wait for it to finish then reboot.
since you're asking for a good rom, and for the relative howto, these are my 2c:
1) you should really put in your sdcard a good recovery, if you don't know what version you have at the moment. Download the zip and put it in your sdcard.
http://code.google.com/p/minimod/downloads/detail?name=Minimod%20V0.06.zip
MAKE A FULL NANDROID BACKUP before flashing roms, to get back easily
2) to me, CyanogenMod 7 is the best rom for daily use, since you have a sort of equilibrium between features and performance. I prefere original kabaldan rom, but you could also try OH NO! version. In general, all you have to do is put the zip file you want to flash in sdcard/OpenRecovery/updates, and reboot by holding camera button. You'll get either OpenRecovery menu (wher you'll find "apply update" functions) or standard recovery screen (a warning triangle).
If you get the triangle you have to press volume up and camera button together, and "apply update"; you'll get the aformentioned OpenRecovery menu.
If you want to try CyanogenMod 7, look at this thread: http://forum.xda-developers.com/showthread.php?t=941346 (first post)
KEEP IN MIND that you'll have to put both the rom zip and the gapps zip in the updates fode of your sdcard (that is, these links: https://github.com/downloads/nadlabak/android/update-cm-7.1.2-Milestone-KANG-signed.zip and http://www.multiupload.com/NQAPSYPKIW)
2bis) you should give a look at the milestone development forum; you'll find info about almost every good rom you can use
Scoutme thnx for your reply! yes i was looking at cm7 so i am going to try that. So if i backup and the new rom sucks, i can just go back to the previous one using the backup. Just wanted to know, current rom is actualy really nice and fast, so dont know if cm7 is going to make it slower. Just gonna give it a try then^^
Sent from my Milestone using XDA App
just updated with your link, works perfectly! phone seems fast enough, but does anyone know if its still clocked at 800mhz or is it al back to stock? anyone using this also clocked their phone becouse of getting slower? fyi it was already clocked when i got it