Database Develop

[Q] Phone only boots into CWM and can't get it to boot the ROM.

I can't get my phone to boot into the ROM, it only boots into CWM every time. Even if I restore my Nandroid backup I have it still won't boot into anything but CWM. .
Any ideas?

_Logie said:
I can't get my phone to boot into the ROM, it only boots into CWM every time. Even if I restore my Nandroid backup I have it still won't boot into anything but CWM. .
Any ideas?
Click to expand...
Click to collapse
what rom are you trying to flash?

I was on MIUI Mintberry but then I tried flashing DMORE3.3 and it just messed up. Was not paying attention to what I was doing, stupidly enough.
But I wouldn't mind just getting back into my MIUI MB ROM and then I'll actually flash DMORE properly this time.

_Logie said:
I was on MIUI Mintberry but then I tried flashing DMORE3.3 and it just messed up. Was not paying attention to what I was doing, stupidly enough.
But I wouldn't mind just getting back into my MIUI MB ROM and then I'll actually flash DMORE properly this time.
Click to expand...
Click to collapse
Well i would do a clean install from gingerbread...here is a kit containing ez odin, ezbase GB, and an instruction txt if you want it...and always good to keep handy!
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip

Legend mate. Really appreciate it .

_Logie said:
Legend mate. Really appreciate it .
Click to expand...
Click to collapse
No probs, any problems or unsure of anything just let me know

All working good. Thanks again!
Btw what ROM is that? It's pretty nice.

_Logie said:
All working good. Thanks again!
Btw what ROM is that? It's pretty nice.
Click to expand...
Click to collapse
It was made by Nitr8, just a stripped down GB based on his insanity ROM

Very nice ROM! So, there's no chance I could now just restore to my MIUI Nandroid backup?

_Logie said:
Very nice ROM! So, there's no chance I could now just restore to my MIUI Nandroid backup?
Click to expand...
Click to collapse
I really couldn't tell you, not familiar with miui, but you can always try,

I have the same issue here. I was running CM9 nightly and everything was working great for weeks. Then my android core process crashed and I decided to reboot the phone, but it got stuck and kept boot looping, i.e. not even making it to the CM9 boot animation and not allowing me to get a logcat.
I used ODIN to flash FixRecovery.tar.md5 and that allowed me to get into CWM recovery. I then cleared Dalvik cache, re-flashed CM9, rebooted but the phone always boots into CWM and never gets to the ROM. I even tried flashing Semaphore kernel in ODIN and re-flashed CM9 several times but to no avail.
My phone just keeps booting into CWM! Is there something I can do to fix this without having to restore to Gingerbread and lose all of my settings and data?

You can go back to the Original Firmware: https://www.fixmystuff.in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom.46/
Then you may root: https://www.fixmystuff.in/FMS_Forum...-i9000-rooting-gt-i9000-2-3-3-india-ddjv9.47/

I had same problem with a galaxy s plus. I've installed the teamwin recovery and with that i flashed the broodrom. After that i got in a bootloop/recoveryloop.. The fix for that was just flashing the bootloader with odin So there was no need to reflash whole rom

aaronegger said:
I had same problem with a galaxy s plus. I've installed the teamwin recovery and with that i flashed the broodrom. After that i got in a bootloop/recoveryloop.. The fix for that was just flashing the bootloader with odin So there was no need to reflash whole rom
Click to expand...
Click to collapse
how do i find a bootloader? i think my phone is in a recovery loop, only starts in CWM

can you please provide me with a new link, i have a GT-i9000 keeps rebooting after i tried flashing with Odin . and can't access to recovery .
thank you for the help.
slaphead20 said:
Well i would do a clean install from gingerbread...here is a kit containing ez odin, ezbase GB, and an instruction txt if you want it...and always good to keep handy!
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip
Click to expand...
Click to collapse

Download URL that works
This link worked for me:
dropbox (dot) com/s/uskxoogzkx3lk8y/dbdata.zip
Sorry can't post urls properly, I'm a new user

Captivate not doing anything

hello all. I just started diving into the world of rooting (and android for that matter) with a friends old captivate. In the process of installing Jelly bean, I messed things up pretty bad.
I had a corn kernel installed (which I later found out wasnt usable for CM10) and when I then found a devil kernal to use, i found myself getting stuck in a boot loop. Trying to get out of it, I flashed back (using odin) to the corn kernel, which then get stuck on the boot screen with the loading bar at 100%. I then flashed around to a few different kernels i had downloaded in the process of trying to figure all of this out and now I cannot get the phone to boot back into the OS.
What should I do?? Where can I find the proper kernels for CM10 (everything I follow is always dead)? and most importantly, how can I get this phone back up and running. This forum seems to be filled with all sorts of smart people, so hopefully we can figure out a solution quickly.
Thanks

With Cornkernel 705 installed I can access the CWM5 recovery screen if that makes a difference

sjorge3442 said:
With Cornkernel 705 installed I can access the CWM5 recovery screen if that makes a difference
Click to expand...
Click to collapse
If you can get in cwm, factory reset and re-flash CM10 (as per their process). CM10 will flash with it's own kernel so you don't have to bother with flashing a kernel after.
If that doesn't work, get stock KK4 and flash with Odin (or Heimdall). Then flash Corn kernel with Odin 1.85 and finaly flash your ROM.

BWolf56 said:
If you can get in cwm, factory reset and re-flash CM10 (as per their process). CM10 will flash with it's own kernel so you don't have to bother with flashing a kernel after.
If that doesn't work, get stock KK4 and flash with Odin (or Heimdall). Then flash Corn kernel with Odin 1.85 and finaly flash your ROM.
Click to expand...
Click to collapse
.
Well, when I get into CWM since i'm running corn, I cannot locate CM10. Flashing back to stock didnt even allow me to reboot into the phone either.

sjorge3442 said:
.
Well, when I get into CWM since i'm running corn, I cannot locate CM10. Flashing back to stock didnt even allow me to reboot into the phone either.
Click to expand...
Click to collapse
Mount your SD through recovery, make sure CM10 is still on it and go from there.

BWolf56 said:
Mount your SD through recovery, make sure CM10 is still on it and go from there.
Click to expand...
Click to collapse
Just logged back into CwM to try to do this and after I mount the SD, I still cannot find any option for CM10 and I am positive it is still on the card.

sjorge3442 said:
Just logged back into CwM to try to do this and after I mount the SD, I still cannot find any option for CM10 and I am positive it is still on the card.
Click to expand...
Click to collapse
Mount the SD card to your PC to make sure it's still there, is what I meant.

well since Im really impatient, I ended up using Odin3 one-click downloader which allowed me to revert back to eclair. phone is working and I plan on starting back to getting CM10 running. Which kernel do you suggest I flash for that?

sjorge3442 said:
well since Im really impatient, I ended up using Odin3 one-click downloader which allowed me to revert back to eclair. phone is working and I plan on starting back to getting CM10 running. Which kernel do you suggest I flash for that?
Click to expand...
Click to collapse
Probably a good idea to clean flash anyway.
Corn is the kernel you'll want to get root.

BWolf56 said:
Probably a good idea to clean flash anyway.
Corn is the kernel you'll want to get root.
Click to expand...
Click to collapse
Yeah, but from what I've read and experienced, Corn cannot be used for CM10 purposes. After flashing to corn using odin (I can both 705 and 706 saved on my computer) there is no option in CwM to install CM10. I read that corn isnt able to boot CM10, but maybe I read something wrong. We're getting off topic for the post, but i'm sure others are having the same problem

sjorge3442 said:
Yeah, but from what I've read and experienced, Corn cannot be used for CM10 purposes. After flashing to corn using odin (I can both 705 and 706 saved on my computer) there is no option in CwM to install CM10. I read that corn isnt able to boot CM10, but maybe I read something wrong. We're getting off topic for the post, but i'm sure others are having the same problem
Click to expand...
Click to collapse
Maybe I'm missing something here but I'm not sure I understand.. The usual process to flashing looks like this (as you probably know):
Odin KK4 stock
Odin 1.85 corn kernel
Flash your ROM through cwm as per their instructions
Flash Gapps
Enjoy
Corn will give you root and from there, you should be able to go get your CM10.zip that is on your internal SD and flash it.
Corn will be wiped as you flash CM10 cause it flashes it's own kernel so it is only to get root when you're on stock.

BWolf56 said:
Maybe I'm missing something here but I'm not sure I understand.. The usual process to flashing looks like this (as you probably know):
Odin KK4 stock
Odin 1.85 corn kernel
Flash your ROM through cwm as per their instructions
Flash Gapps
Enjoy
Corn will give you root and from there, you should be able to go get your CM10.zip that is on your internal SD and flash it.
Corn will be wiped as you flash CM10 cause it flashes it's own kernel so it is only to get root when you're on stock.
Click to expand...
Click to collapse
This is exactly what I thought too, but using corn v706, no matter what I do, I cannot located CM10 OR Gapps....

sjorge3442 said:
This is exactly what I thought too, but using corn v706, no matter what I do, I cannot located CM10 OR Gapps....
Click to expand...
Click to collapse
That's why I said to mount your SD to your PC, make sure where you've put them (in which folder) and also make sure they're actually on it. The kernel won't hide files.. eh
If you wanna make it easy, create a folder for them (and of course, move them in). Folder: CM10. That way you won't be searching all through your phone for them.

so I placed the CM10 in the root of the SD card. On Corn 706, im unable to locate it. I flashed over to Semaphore and was actually able to find the CM10 file, but for whatever reason, when I try to install it, it begins the process and then aborts it.

That would be the norm...just select to install the Rom again from that cwm recovery that pops up.
Sent from my SGH-I897 using xda premium

4-2ndtwin said:
That would be the norm...just select to install the Rom again from that cwm recovery that pops up.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I tried doing that, but it just continues to abort it.I get status 7 error

sjorge3442 said:
I tried doing that, but it just continues to abort it.I get status 7 error
Click to expand...
Click to collapse
Wait.. When you flashed to stock, what Odin did you use?? There's a GB stock (KK4). If you flashed back with the old one click and you're back on eclair you probably don't have the GB bootloaders so you'll have to get them. Corn kernel is meant for GB, not eclair so would make sense if it doesn't work.

Well, I am currently sitting on CM9 with Semaphore. Phone is working, just need to find the correct Gapps, since thats where I store my contact info. I'll mess around with getting CM10 in a few days. I was tired of using my blackberry for the past two days while I have been trying to get this damn phone up and running. I'll do my research to ensure that I use the correct kernels and bootloaders. If you know of a guide for getting to CM10 from CM9, that would be great.

sjorge3442 said:
Well, I am currently sitting on CM9 with Semaphore. Phone is working, just need to find the correct Gapps, since thats where I store my contact info. I'll mess around with getting CM10 in a few days. I was tired of using my blackberry for the past two days while I have been trying to get this damn phone up and running. I'll do my research to ensure that I use the correct kernels and bootloaders. If you know of a guide for getting to CM10 from CM9, that would be great.
Click to expand...
Click to collapse
The instructions are in the CM10 thread. I believe they're quite basics, don't need to go back to stock.
Also, if I were you, I'd redownload CM10 ROM. Could be getting those errors from a bad download.

sjorge3442 said:
I tried doing that, but it just continues to abort it.I get status 7 error
Click to expand...
Click to collapse
...and just a friendly fyi, if u get the Status 7 error again, when u try flashing to CM10 another day, it is because of the assert script in the updater-script, of what ur wanting to flash, is looking at what the build.prop says of ur phone. (that is even hard to type, lol...someone plz correct me if i'm wrong).
U can search and read up a little probably better than i could type and try to explain it. --- But in the end it is more of a fail safe so that u don't flash something that is not for ur phone.
It will be more clear once u read up on it a little. :thumbup:
The asserts can be edited/removed, build.prop edited, or u could use a different kernel, etc. --- several options as a work around to the error.
Sent from my SGH-I897 using xda premium

[Help] Not booting phone, colored screen

I have tried lately to flash ics rom on my rooted captivate which was running 2.2 stock froyo but I made two mistakes that made me fear that it was bricked
- I removed the CWM recovery folder from the internal sd card. As a result, when I reboot the phone, it starts as usual but get stucked in the Samsung galaxy S screen.
- Trying to fix that, I tried to install a custom recovery image using Heimdall suite and with the download mode, but after flashing it, the situation worsened (may be because it was destinated to android 2.3.) and when I rebooted the phone, I get tha At&t logo and then the screen becomes an assembly of colored lines.
The only good news is that I still can access the download mode. I did nothing else to not complicate the situation.
So do you think the phone is hard bricked now? And is there a solution to relieve it? Thank you in advance

medcast said:
I have tried lately to flash ics rom on my rooted captivate which was running 2.2 stock froyo but I made two mistakes that made me fear that it was bricked
- I removed the CWM recovery folder from the internal sd card. As a result, when I reboot the phone, it starts as usual but get stucked in the Samsung galaxy S screen.
- Trying to fix that, I tried to install a custom recovery image using Heimdall suite and with the download mode, but after flashing it, the situation worsened (may be because it was destinated to android 2.3.) and when I rebooted the phone, I get tha At&t logo and then the screen becomes an assembly of colored lines.
The only good news is that I still can access the download mode. I did nothing else to not complicate the situation.
So do you think the phone is hard bricked now? And is there a solution to relieve it? Thank you in advance
Click to expand...
Click to collapse
Basically, you get that screen cause you don't have the right bootloaders. Get stock KK4 with Odin (or Heimdall) one click. You'll find the sticky in the Dev section.
From there, you can flash Corn kernel to get root and after flash w/e ROM you'd like to run.

BWolf56 said:
Basically, you get that screen cause you don't have the right bootloaders. Get stock KK4 with Odin (or Heimdall) one click. You'll find the sticky in the Dev section.
From there, you can flash Corn kernel to get root and after flash w/e ROM you'd like to run.
Click to expand...
Click to collapse
I am sorry I was on travel the last two days
So, is this the thread that I need "[GB][2.3.5][KK4] Heimdall One Click Stock w/ or w/out BL's"? I am having some doubts because my original rom is a 2.2 stock rom. If not, could you please guide me to the right one?

medcast said:
I am sorry I was on travel the last two days
So, is this the thread that I need "[GB][2.3.5][KK4] Heimdall One Click Stock w/ or w/out BL's"? I am having some doubts because my original rom is a 2.2 stock rom. If not, could you please guide me to the right one?
Click to expand...
Click to collapse
Yes, that's what you need. You don't have the right BLs to run the ROM you flashed so you'll need to flash them (KK4 with BLs).
Sent from my SGH-I897 using xda app-developers app

[Q] Bootloaders

I feel like an idiot after reading this forum for the last couple of weeks. My problem started when I really wanted Jelly Bean on my i897 instead of the stock Gingerbread. I found out I failed to install Cyanogenmod and ended up with a phone that could no longer go into download mode, couldn't get into recovery, my laptop no longer recognized the phone and when I powered up the phone it was bootlooping on the AT&T screen.
I ended up buying a jig. It came in the mail today and I got into download mode and using Heimdall flashed I897UCKK4 Stock, NO Bootloaders, Wipe-One-Click.
I wanted to root my phone so I flashed Corn Kernel. My phone didn't go into download mode (it showed the battery charging when I tried) so I had to use the jig to get into into download mode. When I tried to get into recovery, it bootlooped on the AT&T screen. And I noticed during a normal power up of my phone, right after the AT&T screen, I see rainbow colored lines.
I asked someone who has been nice to enough to help me these last couple weeks and he said that the garbled lines mean I'm trying to use a gingerbread kernel and I don't have gingerbread bootloaders. Would the easy way to fix this is to use the same Heimdall One Click I used flashing the same stock and CHECK flash bootloaders this time?
Thanks for your help in advance!

No...u need the one with bootloaders option included...because if the one u have is the one i packaged then the bootloaders are not even included in that package, so even if u chose the bootloader option it would not work.
And if i remember correctly, even with the Heimdall One Click that has the option to install bootloaders etc., it will require two flashes to get the bootloaders. The first flash installs the firmware and then the second installs firmware with the bootloaders. That is just the way it is with heimdall. Just follow the promps and u should be good.
There r other ways of gettin the i897 gb bootloaders of course. The Odin kk4 one click that contains them that i put together in that same one click stickied thread in the dev forum. Also TRusselo has a download of them alone in his Guide that is a stickied thread in the q & a forum. See his op for them.
And etc. etc. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
No...u need the one with bootloaders option included...because if the one u have is the one i packaged then the bootloaders are not even included in that package, so even if u chose the bootloader option it would not work.
And if i remember correctly, even with the Heimdall One Click that has the option to install bootloaders etc., it will require two flashes to get the bootloaders. The first flash installs the firmware and then the second installs firmware with the bootloaders. That is just the way it is with heimdall. Just follow the promps and u should be good.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Will that solve my problem of not being able to get into download mode or recovery, by adding the bootloaders this time? I don't want to brick my phone, although I've been reading that its nearly impossible to brick. ha
Thank you.

Yes the i897 gb bootloaders have solved users problems with button combos to get in download and recovery mode.
But always be careful flashin bls. Mixed matched bls or bad flash of them...loosin power to ur pc during the flash of them or loosin connection of ur usb/micro usb cord during the flash will possibly hard brick ur phone.
So just be sure to have a constant power source, reliable usb/micro usb cable, and don't interupt the flash during the few seconds it takes to install the boot.bin and sbl.bin files. And once u have installed the gb bootloaders there is absolutely no need to flash bls again. If u ever need to flash back to stock just use kk4 with No bls.
Keep us posted on how it goes...
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
Yes the i897 gb bootloaders have solved users problems with button combos to get in download and recovery mode.
But always be careful flashin bls. Mixed matched bls or bad flash of them...loosin power to ur pc during the flash of them or loosin connection of ur usb/micro usb cord during the flash will possibly hard brick ur phone.
So just be sure to have a constant power source, reliable usb/micro usb cable, and don't interupt the flash during the few seconds it takes to install the boot.bin and sbl.bin files. And once u have installed the gb bootloaders there is absolutely no need to flash bls again. If u ever need to flash back to stock just use kk4 with No bls.
Keep us posted on how it goes...
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I downloaded the Heimdall package WITH the bootloaders this time and my phone is having the same problems. I watched it flash twice but I didn't notice Heimdall installing anything different the second time. Was I supposed to check "flash bootloaders" at any time?

Yep. That gives permission for the install of the bootloaders. Check it before u begin the flash.
Sent from my SAMSUNG-SGH-I777 using xda premium

My personal preference is to do an odin flash of just the bootloader package from here http://forum.xda-developers.com/showthread.php?t=1350266 ... I bought my wife a cappy about a month ago and was trying to do a one-click to kk4 w/bl and it kept hanging. After a lot of fighting with it I ended up just flashing to bootloader package and then a custom kernel and all was good.

Yep. Some of the Captivates do not like one click packages. Mine is a 1009 build and thankfully has not had a problem with 'em.
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
Yep. That gives permission for the install of the bootloaders. Check it before u begin the flash.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
FIXED! Thank you so much. No more rainbow pixels, I can get into download mode and recovery now.
I was following the instructions word by word cuz I didn't want to screw anything up and it didn't say to check the box. I'm ignorant.
Thanks again!

^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
WOOOO JellyBeans!!!

4-2ndtwin said:
^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Ha! Watch me screw it all up again. But its all good cuz I've got a jig now, I feel a lot safer.
I think my lack of knowledge regarding Odin and Heimdall on the same computer probably had something to do with my loss of the laptop being able to recognize my phone. I learned that I need to stay away from Odin, it never worked right for me.

Haha...u ought to be fine. Just remember, no need to flash bootloaders again. And the only other possible thing to be concerned about is the "Encryption Unsuccessful" error that has happened with users of this phone and several other phone models. There are two threads in the development forum if u wanna know more about that subject. Other than that the Captivate is a really tough phone. I have enjoyed mine for over 2 yrs now.
Sent from my SAMSUNG-SGH-I777 using xda premium

southernblonde said:
Ha! Watch me screw it all up again. But its all good cuz I've got a jig now, I feel a lot safer.
I think my lack of knowledge regarding Odin and Heimdall on the same computer probably had something to do with my loss of the laptop being able to recognize my phone. I learned that I need to stay away from Odin, it never worked right for me.
Click to expand...
Click to collapse
One thing I will mention is this... Coming from any other version to Jellybean, when you do the initial flash of the ROM it will either reboot automatically or show that the flash completed really quickly and then you'll reboot thinking you're installed. Either scenario will likely land you in a boot loop. Don't freak out because this is normal when you are first flashing to Jellybean. Its because of the partition layout differences and it just requires a reboot. Just get yourself back into recovery and flash everything again and all should be good.

m1batt1 said:
One thing I will mention is this... Coming from any other version to Jellybean, when you do the initial flash of the ROM it will either reboot automatically or show that the flash completed really quickly and then you'll reboot thinking you're installed. Either scenario will likely land you in a boot loop. Don't freak out because this is normal when you are first flashing to Jellybean. Its because of the partition layout differences and it just requires a reboot. Just get yourself back into recovery and flash everything again and all should be good.
Click to expand...
Click to collapse
Is Cyanogenmod supposed to be installed before I flash Jelly Bean? I'm going to be using Slim Bean. Thank you!

southernblonde said:
Is Cyanogenmod supposed to be installed before I flash Jelly Bean? I'm going to be using Slim Bean. Thank you!
Click to expand...
Click to collapse
No, just flash Slim Bean twice. Flash the first time, get back in recovery and reflash Slim Bean right over it.

BWolf56 said:
No, just flash Slim Bean twice. Flash the first time, get back in recovery and reflash Slim Bean right over it.
Click to expand...
Click to collapse
The first time I attempted to flash it, when it rebooted, it was stuck on the AT&T screen forever. I didn't know whether or not it had froze or not so I took the battery out, powered it up, and then it started bootlooping between the AT&T and Semaphore screens.
I should have put it back into download mode again and reflashed it?

southernblonde said:
The first time I attempted to flash it, when it rebooted, it was stuck on the AT&T screen forever. I didn't know whether or not it had froze or not so I took the battery out, powered it up, and then it started bootlooping between the AT&T and Semaphore screens.
I should have put it back into download mode again and reflashed it?
Click to expand...
Click to collapse
No, you go back in recovery and reflash it. The first time, it needs to rewrite the partition so it won't fully flash. After the first flash is over, you get back in recovery and flash right over it (what we call a dirty flash). Then it should boot up just fine!

BWolf56 said:
No, you go back in recovery and reflash it. The first time, it needs to rewrite the partition so it won't fully flash. After the first flash is over, you get back in recovery and flash right over it (what we call a dirty flash). Then it should boot up just fine!
Click to expand...
Click to collapse
You guys are so smart, its sick :laugh:
I was just reading over Slim Bean installation and it says I need to boot up with CM9 or CM10. Is it still necessary to install it? Since I'm coming from Gingerbread. Here's where I read it at: http://www.slimroms.net/index.php/installation

southernblonde said:
You guys are so smart, its sick :laugh:
I was just reading over Slim Bean installation and it says I need to boot up with CM9 or CM10. Is it still necessary to install it? Since I'm coming from Gingerbread. Here's where I read it at: http://www.slimroms.net/index.php/installation
Click to expand...
Click to collapse
Can't see that page as I'm at work (yay for Gov's internet..)
As long as you have the GB bootloaders, you don't have to worry about much. Just make sure you have a cwm recovery (often gotten from flashing Corn kernel with Odin 1.85). But if you are already on a custom GB ROM, you don't have to worry about that.
Next is to factory reset, clear cache and dalvik in recovery and flash Slim Bean (Twice*) and finally the Gapps.
The process is the same for pretty much any JB ROM.
I'm a bit confused though, did you already flash it or not?

[Q] weird bug. need expert advice + solution

Today I tried to update my phone to a new custom rom.
I followed the instructions of the threads and tried to get it to work.
Of course it didn't work or else I wouldn't be here right now asking for help.
Here's the current situation.
I am able to boot into download mode + recovery mode and also boot into cwmr and install a different kernel.
I used pc odin to install it each time and it does pass and the rom (i've tried installing a gingerbread rom so that I can try everything again) does install.
the problem is that it is currently stuck in a boot loop at the "Samsung galaxy note gt-N7000" screen.
I have looked up dr.ketan's posts and tried some too.
currently i am booting abyss note kernel 42cwt touch original. (I know for sure it is a workable kernel because I've been using it this whole time.
here's what i've done. please tell me what i've done wrong and the possible ways to reverse it.
1. backed up everything
2. went into recovery
3. factory reset/cache clear
4. use pc odin to install new kernel (since I was looking into switching to another kernel anyways)
5. use pc odin again to install gingerbread rom (I do get the green light saying it did get installed
6. phone auto reboots
7. it gets stuck at the boot loop like i have mentioned above
i will try to attach a few pictures of my note as soon as I can so you can see what's going on with it.

What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?

nokiamodeln91 said:
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
Click to expand...
Click to collapse
Right now it reboots to 3e recovery.
The rom that I tried to inject to it is currently a the stock gingerbread rom from dr. Ketans thread.
The rom that I had on it is the official ics rom for the hk region.
The rom that I wanted to inject to it was a custom jb rom that uses hydracore as a kernel.
Thanks!!

try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..

nokiamodeln91 said:
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
Click to expand...
Click to collapse
If I do a stock ics update can I just do it through kies or do I have to do it through pc odin? Also. Would abyss or hydracore considered as a safe kernel???

yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels

nokiamodeln91 said:
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
Click to expand...
Click to collapse
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.

Well I am not sure but I soft bricked my phone when I tried that Abyss Kernel. In my view Hydracore is safe. Philz is super safe.
Flash ICS which matches your region using Odin. If phone boots flash Philz, If not, then be ready to read a lot of stuff or get phone repaired.

asian_boi said:
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Click to expand...
Click to collapse
instead of flashing kernels. flash a complete rom using PC odin.

nokiamodeln91 said:
instead of flashing kernels. flash a complete rom using PC odin.
Click to expand...
Click to collapse
You have so much patience
Sent from my Amazon Kindle Fire using Tapatalk 2

the only thing i have...

Hey guys. my note seems to have cooperated and allowed me to flash a new rom and also a new kernel. Here's the catch though, now it's stuck in the samsung logo and won't boot beyond that. Any suggestions of what to do? I am continually searching on the forums to find a solution.
At least I'm happy to know it's not a brick that can't be fixed.
Thanks nokiamodeIn91 for your help so far. I really appreciate it.

which rom did you flash and which kernel? how?

He spent a lot of time helping you. Be sure to hit thanks button

Sent from my GT-N7000 using Tapatalk 2

I currently flashed the abyss note kernel 42 cw touch and I downloaded an old gb rom from sammobile .
Here's what I did.
1. Put my phone into download mode
2. Run as admin on PC Odin
3. Selected the Abyss kernel then flashed it.
4. Boot into the cmw, wiped cache then booted the phone into download mode again.
5. Then I installed the old GB Rom on to my phone and restarted it.
6. Phone starts, loads past the GT-N7000 logo and goes into the samsung boot logo.
7. Phone repeats the animation of the samsung logo a time or two then restarts on its own. This loops until the phone is completely drained. I know that the rom works because that was the rom that I used to root my phone. I definitely don't mind downloading another rom if I have to.
my current goal, if we can fix this, is to quickly just update to the official jb rom for n7000 and not play around with the rooting and such until I have even more time to learn more.
at least I know for sure my phone isn't hardbricked, I would imagine I have either missed a step or something that caused the problem.
I have read through the forum and I did come across one post talking about checking my phone's partition and such.
I got to be honest, I'm really not technically skilled enough at this point in time to dare to mess around with that type of thing yet especially with so much coding to make sense of it. (I know this is kind of dumb to say especially when I rooted my phone and screwed up this bad). More importantly, I don't even know for sure if I need to do a partition or not.
Please let me know what I did wrong and how I can fix it.
I got a question though (out of curiosity), how come there's no toolkit for the n7000 like the S3 and also the note 2???

this is the name of the old gb rom that I tried flashing.
N7000ZSKJ6_N7000OZSKJ6_N7000XXKJ6_HOME.tar
I actually have tried several other roms as well (from GB-JB, official and custom) and all of them so far has gotten to the samsung boot logo
I have read on the forums to try using Philz-cwm 6 kernel but I don't know if it'd solve my problem.
let me show you one of the threads I have read, if I dived into the wrong material let me know and I won't consider using it (or learn how to use it) for my current situation
http://forum.xda-developers.com/showthread.php?t=1661590&highlight=samsung+logo+bootloop&page=2
like I was saying before, I really have no experience in coding so all the things that really made near no sense to me. I understand the basic concept of what its trying to do it's just seems like a very unsafe method for me to try especially when I lack the necessary knowledge in this area of expertise.

did you flash the GB rom using the standard PIT file ?
also you could try with the 5 file flashing method from this thread
http://forum.xda-developers.com/showthread.php?t=1530501

Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2

asf58967 said:
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
Click to expand...
Click to collapse
Yeah true... should also format system..
**** if you can boot into recovery , do a facotry wipe now