Database Develop

How can I upgrade to the latest 2.2?

My story is sort of a strange one.
I originally unlocked my N1 and installed a 2.1 custom rom on it. Then Paul released his 1 ZIP to flash upgrade to F50. I got that and all hints of my custom rom seem to have disappeared. However I'm not sure if I will get OTA updates now, or if I can simply flash the new ZIP to give me the latest froyo because of this custom ROM that I can't remember its name.
I would go back to stock roms and everything but I don't want to lose all my data and apps, plus I don't know how!

So your saying you flashed the froyo update and your Rom is gone?
If that's what you meant... than that is what is supposed to happen.... you lose root when you flash that update.... but Cyanogen made a quick fix for that
Sent from my Nexus One using XDA App

ROM Manager

I'm recently rooted with the paid version of rom manager but I can't get the rom list to update. Does anyone know if the Captivete version is still being supported?
Sent from my SAMSUNG-SGH-I897 using XDA App

Very few (if any) roms use rom manager at the moment due to differing cwm recoveries.
Sent from my GT-I9000 using Tapatalk

+1 for cappy you cannot find roms through the rom update in the rom manager. very limited.

So do we just hunt and peck thru the dev forum or is there a different repository?
Sent from my SAMSUNG-SGH-I897 using XDA App

Sanctus Peregrinus said:
So do we just hunt and peck thru the dev forum or is there a different repository?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
each dev team has the different way to handle its rom, some have their own websites, others may upload the rom into some public sharing servers.
you have to go to the dev threads to search for what you want.

Sanctus Peregrinus said:
So do we just hunt and peck thru the dev forum or is there a different repository?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
In the dev forum search for [ROM] and most of them will all be there.
Sent from my GT-I9000 using Tapatalk

So, as a developer, you have to upload your rom to the CWM repository, or add a link to the cwm repository to the rom?

AdamOutler said:
So, as a developer, you have to upload your rom to the CWM repository, or add a link to the cwm repository to the rom?
Click to expand...
Click to collapse
That is the just but with the captivate, because our roms use custom recoveries and lag fixes, putting roms onto tom manager is not a viable option

O.K. I really want to understand this. I thought rom manager and clockwork mod recovery were two different functions built into one piece of software. Why is rom management dependent on the specific recovery method you use?
Sent from my SAMSUNG-SGH-I897 using XDA App

Rom manager is for the most part a user interface for clock work recovery. To be honest I have stopped using rom manager all together. I just keep the update.zip for clockwork recovery on my sd.
Most if not all roms are now using custom recoveries that understand ext 4 which standard clockwork does not. So if you are on a custom rom, rom manager no longer communicates with the recovery on the rom and is itself for the most part useless
Other phones do not require the lag fix that sgs phones do. We use the lag fix to change the filing from rfs (laggy) to ext 4 (smooth). Rom manager/clockwork recovery do not account for our particular devices. so because of the special circumstances of samsung's decision to use rfs filing, we use custom recovery and lag fixes, which makes our roms not compatible with rom manager
I think.... ;p

mcord11758 said:
Rom manager is for the most part a user interface for clock work recovery. To be honest I have stopped using rom manager all together. I just keep the update.zip for clockwork recovery on my sd.
Most if not all roms are now using custom recoveries that understand ext 4 which standard clockwork does not. So if you are on a custom rom, rom manager no longer communicates with the recovery on the rom and is itself for the most part useless
Other phones do not require the lag fix that sgs phones do. We use the lag fix to change the filing from rfs (laggy) to ext 4 (smooth). Rom manager/clockwork recovery do not account for our particular devices. so because of the special circumstances of samsung's decision to use rfs filing, we use custom recovery and lag fixes, which makes our roms not compatible with rom manager
I think.... ;p
Click to expand...
Click to collapse
Well, thank you. This was a nice little informative post on the pros/cons of Rom Manager. I was one of the people that (as a noob) bought this app right off jump assuming by the description that I could actually recover with a backup created with it. Assuming that it made a (ROM) when in fact it does not. I however am also one of the unfortunate that have a JH7 1006-1012 that can't just recover like most. Mine is the dreaded 3 button and follow this long tutorial and download 8 sets of files, use odin ( a specific version) and if I'm lucky, (which I was) I could get back to stock. I have since put behind me the thought of STAYING on stock and am now getting flash happy (like it's crack or something I just can't wait till I run across that happy norm that makes me feel like I need to stay put for a while because of comfort, speed and agility.
+1 thanks to you.

Purchased pro as well for the same reason.

So the "backup" I created with "rom manager" will not restore me to my virgin settings, except for being rooted of course? Is that backup good for anything?

If you flash stock but want to restore your settings and apps, or if you play around on stock and mess something up then restore is useful. If you are on a 2.2 rom and try to restore your stock backup you will run into issues, you could disable lag fix, flash stock kernel and modem then restore, but flashing stock is much easier

Thanks mcord. I see you helping us noobs all over the Q&A section so cheers to you! And a press on your thanks button.

mcord11758 said:
If you flash stock but want to restore your settings and apps, or if you play around on stock and mess something up then restore is useful. If you are on a 2.2 rom and try to restore your stock backup you will run into issues, you could disable lag fix, flash stock kernel and modem then restore, but flashing stock is much easier
Click to expand...
Click to collapse
mcord, I have a Canadian Version of the Captivate i896. I am running stock 2.2 Froyo and wanted to flash a ROM but had some questions so I am being careful. I also thought that ClockworkMod would allow me to Backup my current ROM and Restore it if required. Are you saying that this does not work with Froyo?
1. Since no one has created a stock i896 ROM that does not have the AT&T logo how can I backup my Stock ROM?
2. If I flash a custom recovery load a ROM and then want to Load back Stock Froyo from Rogers (Here in Canada) can I do this simply by using any i896 Eclair ROM? Will Kies be ok with a custom recovery?

I bought ROM Manager too, and then found out I didn't need it to either back up or to flash. Kind of a waste, but oh well.
Flashing straight with CWM and backup/restore with TiBu works great.

Need help from Root Froyo user

Hey all so I currently have an unlocked bootloader, rooted Nexus One still running the Stock Froyo 2.2.2. and I decided to finally upgrade to the OTA Gingerbread update but have a problem.
The OTA update restarts my phone with a triangle with an "!" inside it and an Android next to it, so I decided to try a manual update as described here.
Everything went well until the installation itself, during the install I kept getting some sort of error stating Twitter.apk in the system directory could not be authenticated.
So here's the problem, with Titanium Backup I made the stupid mistake of uninstalling it and not backing it up when I first rooted a while ago. I thought I could just reinstall it from the market but I get the same error. The only solution I can think of is if someone running a Nexus One Stock Froyo could possibly send me the Titanium Backup files of Twitter, hopefully this would make it work, otherwise I don't think I could ever update.

Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App

danger-rat said:
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Thanks for the response, but I'm having trouble figuring some of this stuff, after spending some time with the search option here in XDA:
1. I don't the difference between custom recovery and flashing an image.
2. I can't find a simple stock Gingerbread image (thought its called ROM?) Details in posts tend to be vague for people that are learning this stuff, like me.
3. Many people have written to use Amron_ra 2.2.1 but I don't know the specifics of each ROM are (ex. if its Froyo based, Gingerbread based, etc.)
4. Would using ROM Manager be a good method to use any ROM or is it limited?
I'm essentially looking for an effective method to upgrading to a clean Gingerbread, since doing it the normal way won't work on my phone (as stated in my first post).

1 - Recovery, bootloader, and 'ROM' are two different partitions on you phone. Once you break security on one, you can use it to break the security on the other. In your case, the security on your bootloader is broken (unlocked), so you can use it to install new software on the other partitions.
2 - See bullet 4 on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1005591
3 - For recovery you have 2 choices, Amon Ra or Clockwork, If you go with Clockwork, I recommend you stay away from 3.x versions. Unless the ROM you want to install says otherwise, either of these recoveries will work.
4 - ROM Manger will work. It's an easy way to achieve results, but unless you know what you are doing, it's also an easy way to screw things up.
I suggest you take it a step at at a time, and really understand what you are doing. Reading the wiki is always a good start, then ask specific questions...
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png

Thanks Danger, I made the jump to Cyanogen 7, RC-4 via ROM Manager and couldn't be happier! Only problem is the known audio bug for Nexus One (person on other end of a call hears a lot of static sometimes, and have to recall them). The forced apps2sd is by far my most favourite feature, especially since the N1 internal space is pretty horrible, I've moved most of my apps2sd and haven't had any problems thus far.
Thanks for recommending CM7, I just wish their website listed the full features for newbies like me.

Thanks danger-rat http://www.nexusoneforum.net/forum/...lick-doesnt-work-gingerbread-2.html#post93952
I downgraded my gingerbread to froyo
Was pulling my hair out with a lame guide in the general section

Congrats!!
Sent from my Nexus One using XDA Premium App

some help with updating my old sprint tab

Ive got an old sprint tab sitting around that id like to breathe some life into. Im fairly certain i rooted it back in the day because ive got superuser, but its running the stock Dj29 froyo software. The su binary is out of date though and it fails to update when I try within the app. I don't think I've got a custom recovery flashed, at least if it is its a version of the Samsung one. I never really did much with the tab because i never had the time to figure out what roms worked on which variant, but now I'd like to get ICS up and running, if not jb. Are there any aosp ports out there for the sprint tab? Thanks!

Both cm9 and aokp are aosp ics.
Sent from my GT-I9300 using xda app-developers app

Yes, but can they be flashed to the sprint tab. At least initially I know cm couldn't be, has that changed?

yes they can.
Look for the p1c build, that is for cdma device.
The usual flashing process involve installing CWM recovery and I think you need CWM 5.X.
I am not familiar with the process because I have a GSM one.

[Q] Downgrade from CM10 to CM7

Friends
I have few questions about i897
1. Is there any way to downgrade from CM10 to CM7 other than flashing stock and rooting?
2. If this is only the way, how can i find the bootloader version. I am now running slimbeen and i am purchased it from ebay with custom rom. Bootloader screen is at&t logo and world phone. I don't know is it 2.2 or 2.3
3. Back button is little laggy. I found a solution in xda about updating touch driver using secret code *#*#2663#*#*. But this code is not working in my captivate. Is this due to custom rom?
4. During taking photos temperature of cell increases and battery drains quickly. Is it normel?
Thanks
Sent from my MB525 using Tapatalk 2

If you want to go down to gingerbread just to use touch firmware update
Then you should not do it, this can brick your touch firmware and you may not be able to use your mobile without adb
And for downgrading purpose
Backup your sdcard (as it can get formatted in the process)
Then flash a cm7 rom
Without completing the installation it will reboot
Boot into recovery again and flash cm7 again
This time you will have working cm

dheeraj (dhlalit11) said:
If you want to go down to gingerbread just to use touch firmware update
Then you should not do it, this can brick your touch firmware and you may not be able to use your mobile with adb
This time you will have working cm
Click to expand...
Click to collapse
But users said that it is working for them. Not find this information. Thanks
Sent from my SGH-I897 using Tapatalk 2

Well do it and if something like that happens then share it with all of us, so no one else will do it