Database Develop

[Q] FRF91 change kernel

Hi,
I've been searching the forums for this, but haven't found any real answer, so I thought I'd open a new thread .
I've successfully rooted my stock N1. However I'm wondering, with my newly acquired root rights, would it be possible to flash a custom kernel on it without needing to use a custom ROM.
The reason I'm asking this is that I would like to use iptables for use with a transparant proxy. It seems that the stock kernel does not support this
Of course if anyone has a different approach for the proxy, feel free to let me know as well .
Thanks!

I was able to flash just the cyanogen kernel onto my FRF91.
Sent from my Nexus One using XDA App

instructions?
Ok that is great news... did you encounter problems afterwards with any of the core components? what about some instructions on how to do this (or a link )
Thanks!

I haven't seen any problems with the stock components on the phone.
I can't find the thread I got this from to save my life! I don't know where you are in the process so here's the entire list of what I did:
Unlocked the bootloader using the fastbooot oem unlock command.
Flash Amon-Ra recovery for N1.
Reboot straight into recovery, Back up Stock ROM.
Flash Modaco's superboot for FRF91 from recovery
Flash Cyanogen's N1 Addons (which contains the kernel).
If you google update-nexusone-FRF91-cm-addons-signed.zip you'll see a bunch of downloads for the kernel update. The MD5 sum on the file I have is: 7cf8074d3685681728043f367e6b35fd
It goes without saying, but backup your phone before flashing...

Thanks
I actually rooted without unlocking the bootloader, and would prefer to keep it that way since I get to keep my warranty
I'll try this today, thanks a lot!

Tried it, failed
No worries though, just 'upgraded' to CM6 RC2

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

[Q] How to Re-Root a *Half* Rooted Captivate

I seem to have a recurring problem with my root on the FireFly 2.8 rom, though it may have been present on Serendipity and I never noticed.
My problem is this: Before I flashed FireFly, I used Odin to revert to stock 2.1, master cleared, and then rooted using the One Click Galaxy S root, which worked fine. I was able to flash the rom using CWM and Titanium Backup as well as other apps that require root said they had proper permissions.
At some point, I do not know where, I lost my root. Now, when I try to use Titanium Backup or Firefly fixes, the app tells me Root access FAILED.
I have superuser as well as the current busybox. Can anyone help me with possibly telling me how to enable my root or how to reroot if necessary?
I have tried z4root but it never does anything anymore.
And when I try to use the One Click Root again I can not click "reinstall packages" because I am taken to CWM instead of regular recovery.
Any help would be appreciated, thank you.

You probably converted system to ext4. Go back into Recovery and go to the features of whatever kernel u are using and reapply root.
Sent from my Captivate running Continuum 4.0 with Onix 2.0.5.

I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.

#1 in CWM "reinstall packages" is the 2nd option down! called "apply update.zip" (kinda makes sense doesnt it?)
#2 if you have CWM you can root without one click root.
boot to CWM recovery> Clockwork Features > root + install superuser
adv

Edit: Nevermind, looks like someone already solved your problem while I was typing my BS out.

skrallbro said:
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
Click to expand...
Click to collapse
You don't normally have to....

I has this same problem with FireFly 2.8. I never had that issue with older versions of FF. But, as mentioned, if you reapply root in CWM, it works again.
I love the FF themes, and stability, but I may go back to FF 2.6. FF 2.7 had charging death for me, and FF 2.8 I have issues with keep the lights on. That's how I found my root issue. Now, with the root fixed, keep the lights on seems to disable itself after a while. Definately after every reboot it turns back off. I never had this issue before with cog, perception, or any of the earlier FFs.
Sent from my SAMSUNG-SGH-I897 using XDA App

Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.

Elisha said:
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Click to expand...
Click to collapse
All the FireFly versions I have used have the lagfix optional, and applied through CWM, but 2.8 is the first one that applying the lagfix affected the root of the ROM. I also didn't have this issue with Cognition or Perception, both of which apply the lagfix on first boot.
So the kernel is the issue, not the ROM? A different kernel may fix this?
Sent from my SAMSUNG-SGH-I897 using XDA App

quarlow said:
So the kernel is the issue, not the ROM? A different kernel may fix this?
Click to expand...
Click to collapse
Yes and no. losing root from converting system to ext4 or back to rfs, can happen with any kernel, and for the charge death that was the onix kernel in those versions. The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.

i have never lost root converting my system
but i havent converted it in over a month. Just leave it EXT4 when i upgrade/change roms.
havent had any problems not converting it so i dont bother. (except going to stock)
but when i used to convert back and fourth every flash out of fear... NEVER LOST ROOT

I've only lost root converting on Continuum but never on FireFly or Apex so not sure if it is kernel or rom.
Sent from my GT-I9000

studacris said:
The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
Click to expand...
Click to collapse
Yes FF 2.8 has bln options in CWM. I have issues with bln active or disabled (in FF 2.8). I have not tried managing the bln with the app from the market, would that make a difference (vs managing bln in CWM)?
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] I think I messed up the ROM

Ok, I think being a NOOB, I have messed up. Slightly or catestrophically I'm not sure...
So, I decided to install he Overcome system. I forgot to do the bootloader patch, or rather, I couldn't work out how (and I did look fir instructions) so I just skipped it. I realised after I had wiped and formatted that it was a simple application installed from the Android desktop. The TO install went well and I started installing apps. I thought, OH I better do that patch. As soon as I did, I got a kaleidoscope of colours on reboot and also when I selected Settings.
I used odin to flash the overcome tar and that saw kaleidoscope dissappear when selecting settings, but still appears upon reboot. I thought my next step would be to do the nowipe but I cannot access the tab from my PC using Kies or Explorer although the TAB does show the USB Kies screen, and the PC does recognise it as a USB conected device, but is not accessible by WE in Mass Storage mode.
What do I need to do to fix this?

Boot loader patch only for froyo.
Overcome is GB so it wont work.
You messed up, so start from scratch.
Restock to Stock Safe v5 using odin.
Sent from my GT-P1000 using XDA

Ok, did that and all I got was the 'GALAXY TAB' and SAMSUNG logos indefinitely. Reflashed the CWM and that got me back to the CWM command list. I then reran the 'Overcome_7_Series_v4.0.0_Wipe.zip' from there and after that installed, rebooted and back to the brick screen again.
Where to now?
Perhaps I have used one of gthe wrong bin's or placed something in the incorrect 'Files [Download]' section? PDA, Bootloader etc.
I will learn but for the moment, I am somewhat confused about the terms ROM, Bootloader, Kernel, PDA, Stock, Restock etc and I have no idea what CSC is.
Is there a thread I can read that explains what each one is and what part of this OverCome Installation is replacing/upgrading/installing?
------------------------------
Well, looks like I missed a file, so it was obviously just going nowhere after boot. Once I did that, it was all good. Instructions on the Overcome site are a bit hard to follow. Needs to be reformatted into a wiki I reckon.

Glad you got it solved.
I think overcome guide is very easy to follow step by step apart fr the broken image.
But phloke has made a cached copy for all to see.
http://forum.xda-developers.com/showthread.php?p=20974872
Sent from my GT-P1000 using XDA

Apart from a few minor niceties in the graphics and some improvments in Google maps, I am yet to see what the fuss is about in moving from 2.2 to Overcome. I guess time will tell. I mainly use this TAB for NAV and web and in my work vehicle.
Does the new OC OS give my TAB USBOTG or HDMIoMHL or anything like that, or are these hardware limitations (which I suspect is the case).?
The Overcome TWEAK link goes nowhere, so I don't know what else I can play with to make my experience better.
Is there any real advantage in going to ICS?
One day I may use it for business emails and perhaps invoicing, but I think a larger, say 10" TAB, would be better suited for that anyways.

I am not entirely sure about what I am saying here (didnt research enough), but here is the advantages over 2.2
- froyo may have protected bootloader issue
- overcome uses ext4 compared to rfs. I think ext4 is faster
- overcome kernel has fairly new CwM recovery. Great for flashing new stuff
- froyo cant run flash
- stock kernel doesnt support vpn
- stock kernel doesnt support overclocking and dont have addition schedulers and governers
Anyway, I think overcome is a good stepping stone your next custom rom.
Many custom roms instruction includes flashing overcome first.
I am now using Acudroids with Red Pill kernel.
Excelent battery life and super stable.
Sent from my GT-P1000 using XDA

priyana said:
I am not entirely sure about what I am saying here (didnt research enough), but here is the advantages over 2.2
- froyo may have protected bootloader issue
- overcome uses ext4 compared to rfs. I think ext4 is faster
- overcome kernel has fairly new CwM recovery. Great for flashing new stuff
- froyo cant run flash
- stock kernel doesnt support vpn
- stock kernel doesnt support overclocking and dont have addition schedulers and governers
Anyway, I think overcome is a good stepping stone your next custom rom.
Many custom roms instruction includes flashing overcome first.
I am now using Acudroids with Red Pill kernel.
Excelent battery life and super stable.
Click to expand...
Click to collapse
Sounds like it was worth it.
Speaking of next custom ROM, what advantages would I get for going to Honeycomb or ICS? I read bits of another thread saying that certain hardware was not yet supported in ICS such as GPS, Camera and Blutooth.
Is this also the case with Honeycombe and have these issues been solved?

Honeycomb is a half thought effort by Google.
Just forget it and move to ICS.
Both TE4M CM9 and AOKP are ICS and they are in tablet mode.
I don't know what is the advantage, I guess if you like your Tab to work as tablet and like the latest OS, then go for it.
If I am not mistaken, only back camera has issue. The rest should be ok.