Database Info

[GUIDE] How to install Apex 9.x coming from CM7

These instructions should work from almost any ROM when flashing Apex 9.x, but I felt specific instructions were needed for CM7. If coming from something other than CM7, you should make sure that your filesystems are RFS before messing around with Odin.
Here is the thread for Apex: http://forum.xda-developers.com/showthread.php?t=952588
Thanks : Watsa, DesignGears, Atinm, Cezar', Shortfuse, and anyone else.
Files you need:
--Apex_9.1_JVR.zip - http://apexromcaptivate.weebly.com/apex-9x---jvr.html
--Apex Flasher.zip - http://apexromcaptivate.weebly.com/installation-instructions2.html
--I897UCJF6-final-OCD-REV0.zip - http://forum.xda-developers.com/showthread.php?t=731989
--efs-backup.tar.gz(Optional) - this should have been created either strait out of the box, or sometime before you started flashing custom ROMs. If you've gotten this far flashing ROMs and your IMEI isn't screwed up, then you should still backup- http://forum.xda-developers.com/showthread.php?t=859914
--I897UCKF1-bootloaders.zip - http://forum.xda-developers.com/showthread.php?t=1129821
--SuperOneClickv2.1.1-ShortFuse.zip - http://forum.xda-developers.com/showthread.php?t=803682
1. Starting with CM7nightly84 (on official 2.2 boot-loaders acquired from Kies Mini (pre-CM7 install)), I used DG's OCD Odin JF6 (NOT the 3-button-fix version) to get back to stock. CLOSE the OCD window after stock flash is done. I then placed Apex_9.1_JVR.zip on my internal sd card.
2. Then, I rooted 2.1 with Super One Click and restored my /EFS folder from the backup file using ADB. After restoring /EFS, I immediately reboot in download mode and reflash to stock again using the same Odin OCD (make sure you close the one you used to flash in step one and open a new instance of it and unplug and replugin usb between every flash or you might end up a saaad panda). This makes it as close to an "Out of Box" state as possible. I'm sure this step can be skipped if a backup isn't available. This is just something I always do between flashes.
3. I downloaded Cezar's KF1 boot-loaders OCD and followed the instructions provided in the thread about how to flash them. This had me end up with KF1 boot-loaders on an otherwise completely stock, unrooted, JF6. The KF1 boot-loaders should not affect 2.1 or 2.2 normal functioning.
4. Then, I extracted the Apex pre-flash package (Apex Flasher.zip) and followed the instructions as if the boot-loaders were already flashed. This got me on Dark Core 3 - JVR_C. Watsa confirms that the KF1 boot-loaders in the Apex Flasher.zip are the same as Cezar's that are in the forum listed above. The only reason I didn't use them is because flashed them on my own.
5. Ater all that is done, reboot to the white AT&T screen. I would recommend a battery pull or recovery key combo (vol+, vol-, & power) as soon as you see it because the DC3 kernel will try to apply Voodoo ext conversions with stock 2.1 still on there. Upon arrival at the recovery screen, chose the option to install zip and find Apex_9.1_JVR.zip .
All done. When it reboots, you'll hear that beautiful robotic voice of the lady converting your partitions. Sounds almost dirty, doesn't it?
If you don't hear anything, reboot into recovery and enable the options under the "voodoo" menu.

reserved...

Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4

Thegodfather156 said:
Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4
Click to expand...
Click to collapse
I setup this guide for anyone who wanted to use the KF1 boot-loaders specifically. Starting at CM7 nightly #78, emmc is now supported on gingerbread boot-loaders for the captivate. This means that after loading these you shouldn't have to change boot-loaders again if you wanted to go back to CM7 or switch to a new ROM. All of the I9000 based GB ROMs I have seen have reported no issues using KF1 booties. Some devs even recommend them to ensure hardware compatibility. They seem to work great with Froyo as well.

Cant get any ICS rom to work.

I recently got a Captivate and wanted to put Cyanogenmod on it as it's what I used on my HTC Aria before this.
So the first few times I did it I managed to delete my IMEI but I got HellyBean to run just fine, but couldn't use it due to the IMEI messup.
So I managed to get back to stock and set about trying it again, but it seems like what ever I do I can't get anything to work properly.
So I'm starting from a Stock 2.1, the first thing I did was use the SuperOneClickRoot which worked fine.
The next part is what I think I just can't get right, installing ClockworkMod.
First I tried using this http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide but it didn't work, I now realize that is for 2.3, not 2.1.
So I googled around, found a CWM for 2.1, renamed it to update.zip and flashed it. That worked fine and I can use CWM from then.
After that I set about finally getting CyanogenMod on it.
I tried this guide first http://www.androidauthority.com/captivate-sgh-i897-cyanogenmod-10-jelly-bean-android-4-1-103899/ but it would just leave me stuck at the ATT screen.
I also tried HellyBean, but that has deleted my IMEI every time I've tried flashing that.
So what am I doing wrong here? What is considered the best guide to use?
This has just become so frustrating, it's so much more difficult than when I first got my Aria and flashed that to CM7, I just cant figure out what I'm doing wrong.

Then use this guide:
http://forum.xda-developers.com/showthread.php?t=1350266
Make sure you download the ROM and put it on the SD card first and THEN flash the kernel because once you flash the kernel the OS won't load anymore.
Also you installed Helly Bean so you must have GB bootloaders? In any case, flash GB to ensure you have the right bootloaders. Follow the guide. Install ROM. There is a reason the guides start from 2.3, BECAUSE YOU NEED 2.3.

Right, it just makes more sense to start on GB. You need those bootloaders, plus all guides assume you have it now. And you can skip rooting.
Sent from a jelly bean

Lifecycle of ROM's posted here - Alpha, Beta, offcial?

Hello,
I have a general noob question on the custom [ROM] threads.
Do custom ROM's posted go though an alpha, beta, official release stages? I see some [ROM] threads marked with an alpha or beta... while some others are not.
thanks!

U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull

demonoid phenomenom said:
U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?

gcretro said:
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?
Click to expand...
Click to collapse
There is no such thing as release grade. Everything should be considered at least developmental in some form or fashion.
The terms of alpha and beta do not mean what most people think they do in here.
Even the ones marked alpha and beta can still be daily drivers, just take a look at the first post of each ROM you are thinking about and see if the bugs will "bug" you like for instance any of the CM based ROMs here have issues with camera and video and few other small bugs.
Any ROM based off of "stock" will have less/no bugs and therefore not marked as beta or alpha, since they are not compiled.
It all depends on your personal needs as to what you are comfortable with and if you can deal with certain things not working right out of the box, or that you might have to make a work around for.

I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind

alteredlikeness said:
I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind
Click to expand...
Click to collapse
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks

gcretro said:
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks
Click to expand...
Click to collapse
First, you need to get ICS on your phone if you want to flash Numa. You must be on 4.0.4 firmware to flash any of the ICS and/or JB based ROMs. The choice is yours on how to get there... please search thoroughly, as it has been covered an insane amount of times.
But, to try and answer your questions:
-Yes, the pre-requisites are that you need to be rooted, and have a custom recovery installed on your phone.. and an sdcard. You can do it on your rooted GB phone, but you cannot restore a GB backup while you are on ICS (for the only way to have the option to return to GB from ICS, you need to look here and here - but some will say there's no reason to go back to GB.. maybe nostalgia )
-A backup will backup your current system, data, and sometimes cache - and it will usually make a new folder, named by date, with a few .tar files inside of a "clockworkmod" folder on your sdcard. And yes, those are what you restore (when restoring, you choose the backup by date/folder name).
-No, you can not restore a GB backup from Numa (see above comments.. again) - also see here for a note on compatibly between different custom recovery options (might be easiest/safest to use BMM, I think you can flash all ROMs with that now..)

So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
3. Then follow the install instructions under the Numa Rom thread.
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
Thx

gcretro said:
So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
If you uninstalled any stock apps, the installation of the update will probably fail, and you will either need to fix your system by replacing everything (very carefully).. or just FXZ back to stock GB<--post is a bit out-dated. [Yes, if you ota to final ICS, you can not return to GB ever. It doesn't matter what the ROM you flash is based on, they basically only change your /system partition (and data) - the problem is the new bootloader in final ICS.
Make a full backup of your stock ICS if you want to go back to it (see below - probably best to use BMM to backup)
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
You could use that, or BootMenu Manager (I heard that it works to flash roms now - it used to not - and I personally have not tested it recently.. so, not sure - and we also have Safestrap, but not sure of the status on that - still a wip, I think). Either way, you will loose it once you flash Numa... you will need to reinstall it to flash a different rom or make a backup (I recommend using BMM to make a backup since it's compatible with the CM10-based recovery, and since it is easy to uninstall)
3. Then follow the install instructions under the Numa Rom thread.
Yup.. maybe a bit outdated also, but wipe data/factory reset, dalvik-cache maybe, then install zip..
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
You can put any ICS/JB rom available for our phone, if you wish - or restore the backup you made of stock ICS before installing Numa
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
There are other ways to get from dialer to contacts in ICS (underneath the favorites tab, scroll down.. or is that only jb?)
Thx
No prob. Good luck.
Click to expand...
Click to collapse
See in-line..

[Help] No Service

After flashing a couple of ROMs today/attempting to, I am no longer recieving any service from my carrier.
Here is what I did:
I started off on Slim Bean 4.1.2 with working recipetion.
1. Attempt to flash Vahalla Black FB Edition. (Failed) It just wouldn't flash and TWRP said I had no OS installed.
2. Attempt to flash TFQ Vahalla Final Mod (Failed) Same problem.
3. Attempt to flash the Antrox Kernel linked in the TFQ Vahalla Final Mod.
4. Used Hemidall Back To Stock
5.Flashed Team Acid AOKP Milestone. (Worked) However, there is no recipetion now.
Any help would be appreciated thanks!

go to setting, about phone, or something and see waht it says for baseband. that will tell if a modem flashed properly or not.

Flash back to stock and stay there till you understand that your not following directions.
You have lost your imei.
And its very simple fix,and if you would follow instructions ....you wouldn't mess it up.
What I always do is after you format system ....remount system....
It should look like this.....unmount/system.
So long as it says that you will be fine.
Oh and btw...you can not flash back from ics or jb to gb without first flashing back to stock with a one click.

Shortbus-Driver said:
Flash back to stock and stay there till you understand that your not following directions.
You have lost your imei.
And its very simple fix,and if you would follow instructions ....you wouldn't mess it up.
What I always do is after you format system ....remount system....
It should look like this.....unmount/system.
So long as it says that you will be fine.
Oh and btw...you can not flash back from ics or jb to gb without first flashing back to stock with a one click.
Click to expand...
Click to collapse
Thanks I think I've solved the problem.

Good deal!...
I remember that feeling of "oh crap"
Lol

Shortbus-Driver said:
Good deal!...
I remember that feeling of "oh crap"
Lol
Click to expand...
Click to collapse
Service is working fine however, my goal was to go back to GingerBread but after I use the one-click back to stock, I am forced into a recovery mode that is unable to mount /system /cache /data and I can not flash anything except AOKP Milestone 6 which then works fine.

I don't know what's goin wrong for you.....I have only ever used Odin to flash back to stock
Gremlin remover one click and have never had an issue.

[Q] Custom ROM always bricking

Hi there, I have been trying for countless hours to make a custom ROM work on my P920 with no results, always some issues. I've managed to brick my phone in different ways a billion times now, then spent billion hours unbricking it and in the end I'm always back to where I started. I would really love some help please.
My phone is P920.
The android version I'm running is: 2.3.5
Kernel version: 2.6.35.7+
Software version: V21E
Rooting method: megatron
Now I would like a ROM that uses Android 4 and that can still use the 3D features such as 3D camera, the ROM calledthe Darkroom International would be an example I imagine.
While that's one of the ROMs that I would want, I've tried many, and always encountering issues, let me clarify.
First of all my device has to be rooted and since SuperOneClick doesn't work for me as it gets stuck on step 7, I use megatron which works well. I even double check if my phone is rooted with the Root Checker from the Android store. Now according to the guides I've read I need a custom recovery system, so I install Clockworkmod. I then place the ROM on the SD card, in the recovery menu I delete cache, that other cache, format it, format system, data, everything those guides tell me to. Afterwards, I install the ROM by selecting the zip and then I reboot. I've tried like 3 different ROMs, jellybem, cyanogenmod and some other. Yes I know none of them support 3D features - I didn't know at the time. Anyway, the issue was always the same, right after the LG logo there would be a screen with some weird colors showing the display of what happened before the phone crashed. Before it crashed? Yes, the phone would actually boot into the ROM but only for a few minutes, crashing afterwards. The next time I would boot, it would show that weird screen with those fancy colors with what happened just before it crashed. So I followed some steps and I got back to the original 2.3.5 ROM, everything back to normal.
I tried doing some more research and I came across the Darkroom Intentional ROM which had a bit different instructions. It asked me to install TWRP recovery with a bootloader, so I did, successfully, then did all the clean cache etc, installed ROM, bam, wouldn't boot at all. Oh boy have I had issues here, I couldn't even get it back to the default 2.3.5 stock ROM because my phone wasn't even recognized in the device manager. So I did some more research, found a solution, managed to flash back to 2.3.5 stock and I'm back to square one.
Now, could someone please help and explain to me what exactly have I done wrong and how I can make it right? I've spent countless hours now trying to install a custom ROM with no success. Sorry about the long read. If you need me to supply some more information please let me know. Thank you.

First of all if u want to use an ICS ROM then u need to update to ICS FIRST u can't flash it directly from 2.3.5 u can use xbsalls thread to update......
Next if cm based Roms are crashing then u need to flash bootloaders which means u should use os_hacking tool to flash ICS bootladers if u wanna update
Or flash GB bootloaders
So first update if u want
Root
Flash bootloaders
Flash recovery
Flash Roms
Sent from my Nexus 4 using xda app-developers app