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?
Related
Hi all.
I picked up a used cappy that was "bricked" for cheap. It simply bootlooped on the AT&T screen.
Took it home, hooked it up and odin'ed stock kfc1 with bootloaders onto it. I have now tried every one click Odin or hiemdal gb file I can find, and it just sits at the att screen. Download mode works fine, recovery doesn't.
Flashing a gb kernel with cwm through odin works, but still no boot or recovery.
What am I missing?
Thanks!
Sent from my SAMSUNG-SGH-I957 using Tapatalk
you might want to try flashing a stock ROM with Odin, I'm sure you can find some around the forum =) It's really hard to hard brick the cappy, and since download mode works all you need is a working ROM, so yeah, just go with a stock ROM first
A stock ROM is what I've been attempting to do. I have tried all the 1 click stock packages in the sticky in the development forum..
Sent from my SAMSUNG-SGH-I777 using XDA
Try not using a 1 click
I tried that as well.
I flashed one at a time (meaning just the bootloader, then just the kernel, and finally the rom itself), as well as everything at once.
Proper bootloaders flash fine, kernel flashes fine, and roms appear to flash fine.
Just failure to boot or recovery..
I'm at a loss..
Edit; autocorrect fail
Sent from my SAMSUNG-SGH-I777 using XDA
Sounds like the same problem I'm having, unfortunately I believe it's related to a bad internal sd partition and as of yet I've found no way to fix it
If you flash stock eclair, can you enter recovery?
That was the only recovery I was able to access, from there running adb shell, then dmesg I was able to see that the internalsd was corrupted or at least not mounting.
Still not able to enter recovery even on Eclaire.
I think Ill send it to Samsung USA and see what they say..
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
I figured I would update this, I called Samsung and gave them my imei number and they stated it was still under warranty.
So I sent them the device.
The internal SD was corrupt or bad as stated on the invoice.
I have it back and it works free of charge!
Thanks Sammy!
Sent from my SAMSUNG-SGH-I777 using XDA
I just bought a used Note at an amazing price. The seller stated that after wiping.. he couldnt get it to boot.. even though the phone
manages to go in Download Mode and in Recovery Mode. I'm getting it today.. my 1st thoughts were to flash a stock rom via Odin..
should i try something else before Odin?..maybe try to flash a custom rom via the Recovery? Any ideas? Thanks in advance guys...
c0rpse_grinder said:
I just bought a used Note at an amazing price. The seller stated that after wiping.. he couldnt get it to boot.. even though the phone
manages to go in Download Mode and in Recovery Mode. I'm getting it today.. my 1st thoughts were to flash a stock rom via Odin..
should i try something else before Odin?..maybe try to flash a custom rom via the Recovery? Any ideas? Thanks in advance guys...
Click to expand...
Click to collapse
You should try to flash Stock GB Rom via ODIN first..Then you can flash custom roms after you root your device with CWM installed
Best way is to flash GB ROM
If it flash successfully then wipe cache and data rom recovery.
If note damaged with emmc brick bug, it wont bootup.
guys thanks alot for the quick replies!
i shall have the Note in about an hour or so..so i'll first attempt flashing a GB Rom via Odin..
hopefully everything will turn out ok there and i won't have to search my soul out on xda about
that emmc bug that's been mentioned:fingers-crossed:.. i shall post here the outcome soon!
so.. while i can boot into download mode and in cwm mode.. the Odin fails to flash the stock GB rom.
it gets stuck (see attachment).. what's my next step? :-/ should i try to follow this guide?
c0rpse_grinder said:
so.. while i can boot into download mode and in cwm mode.. the Odin fails to flash the stock GB rom.
it gets stuck (see attachment).. what's my next step? :-/
Click to expand...
Click to collapse
I think you just hit the emmc bug- this is the classic symptom- stuck at flashing FACTORYFS after the wipe on ICS Rom.
Take it to Samsung for repair or flash using a modified PIT file. You will lose some internal memory but the note can be revived. Search these forums for instructions! Good luck!
jkananda said:
I think you just hit the emmc bug- this is the classic symptom- stuck at flashing FACTORYFS after the wipe on ICS Rom.
Take it to Samsung for repair or flash using a modified PIT file. You will lose some internal memory but the note can be revived. Search these forums for instructions! Good luck!
Click to expand...
Click to collapse
unfortunately i dont have the receipt (so no warranty) so i guess i ll do the modified PIT file method and i'll just get a bigger sd card.. thanks for the good luck part!
so i found a few posts that seemed helpful, i tried flashing the FM-Note-Kernel_V2.0 via Odin and it was successful, after that i
tried flashing via CWM the ROCKET ROM - v23 - GB - LC1.. and it started out pretty good..the progress bar was..progressing
normally..the funny part was when the progress bar ended.. because even though it ended..it kept going..to outerspace..towards
the right end of the screen..till it reached the end of the Note's screen and it stayed there.. (see attachment) for about 6-7 mins..
after that it got past it and it stuck at "Installing Kernel" at right about half of the progress bar.. that is how it is right now.. i guess
i'll give it a bit more time before i do anything..
edit: the progress bar while in "Installing Kernel" is actually progressing....!! ridiculously slowly though.. and the fact that i'm staring at it is making it even slower
edit: we got past it! now it's at "Installing Modem" and... ITS DONE! ... i am completely terrified to reboot because i am 99,99% sure it's not gonna make me happy...
edit: indeed... no luck there
Seems your device affected with emmc brick bug
Claim your warranty
Or
Try this
http://forum.xda-developers.com/showthread.php?p=26285877
Sent from my GT-N7000 using xda premium
dr.ketan said:
Seems your device affected with emmc brick bug
Claim your warranty
Or
Try this
http://forum.xda-developers.com/showthread.php?p=26285877
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
How can i claim my warranty if i have no receipt?
Do you think they'll accept it? Also, there's the yellow triangle problem..however
i also have a jig.. could I use the jig to get rid of the triangle with the phone being
as it is?
edit: Ι'll follow the guide soon after i read it a couple of times thanks
c0rpse_grinder said:
How can i claim my warranty if i have no receipt?
Do you think they'll accept it? Also, there's the yellow triangle problem..however
i also have a jig.. could I use the jig to get rid of the triangle with the phone being
as it is?
edit: Ι'll follow the guide soon after i read it a couple of times thanks
Click to expand...
Click to collapse
Yes you can remove the traingle using a working JIG. Check here and follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1354888
Sent from my GT-N7000 using XDA Premium App
Ι got to a much better state using this guide
The phone actually boots up! After the procedure i Flashed via the Recovery a GB Rocket Rom! It boots up after a while however..
at the start of it all where it sais to click on the android to begin (right where u choose the language).. i get a repeated force close
about phone.android that won't let me use the phone........ any ideas!? we are so close!!
normally after flashing GB, you may struck at the first screen. wipe data and cache and if you can go to dalvik cache, wipe that too and reboot. good luck.
dsmas said:
normally after flashing GB, you may struck at the first screen. wipe data and cache and if you can go to dalvik cache, wipe that too and reboot. good luck.
Click to expand...
Click to collapse
i get backstabbed... it won't boot at all.. again... so.. i will try the other method with the automated PIT Files... damn it damn it...........
c0rpse_grinder said:
i get backstabbed... it won't boot at all.. again... so.. i will try the other method with the automated PIT Files... damn it damn it...........
Click to expand...
Click to collapse
Don't loose heart. why do'nt you flash another GB rom?
dsmas said:
Don't loose heart. why do'nt you flash another GB rom?
Click to expand...
Click to collapse
because it wont do anything.. its the definition of a brick..it's not even going into DL Mode with the Jig...............
u should try flashing stock rom using odin 1.87 and do remember to run it as admin.
Sent from my GT-N7000
liewkingyan said:
u should try flashing stock rom using odin 1.87 and do remember to run it as admin.
Sent from my GT-N7000
Click to expand...
Click to collapse
how can i flash anything via Odin if i cannot even get into Download Mode?
any other ideas? the phone is completely dead, as if i threw the battery down a river
May b your battery is completely empty, manage for other battery then only you can move to next step
Sent from my GT-N7000 using xda premium
dr.ketan said:
May b your battery is completely empty, manage for other battery then only you can move to next step
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
unfortunately that cant be it, right before total brickage the battery level was above 60%...
i even tried charging it but.. nothing
So basically here is what I did, I flashed this ROM right here:
http://forum.xda-developers.com/showthread.php?t=1953847
And now CWM will not let me flash any other ROM, trying to flash anything else just fails and it stays on the current ROM. I can re-flash the current ROM and I have done multiple times, but I am unable to remove it, even with a full wipe and formatting /system which is really weird. It's practically irremovable. I posted a thread about it here:
http://forum.xda-developers.com/showthread.php?t=1962219
Without much luck because I'm a bit of a noob and I didn't quite understand what they were talking about.
The first time I flashed a custom ROM was using this tutorial right here:
http://www.androidauthority.com/gal...cs-cyanogenmod-9-cm9-official-nightly-107611/
I used Heimdall Suite to flash the custom kernel which allowed me to then flash CM9, (it's only after CM9 that I went to this Jelly Bean ROM and since then I have been unable to go to any other ROM)
So my question is, would I be able to just re-do this tutorial without fear of damaging the device and hopefully rescue it and flash a different ROM? (I'm wanting to flash BlackCNA)
Thanks
shameless self bump
Firstly, get rid of Heimdall unless you're on a mac? Search this forum for pc odin, make sure you've got Kies installed correctly. Go into download mode on the phone, Vol down, home and power held down until reboots into download mode. Connect to pc on mobo usb ports with original data cable, you should get a connection in pc odin, then flash any gb rom initially just to see if it completes and if not, post back with the error.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Firstly, get rid of Heimdall unless you're on a mac? Search this forum for pc odin, make sure you've got Kies installed correctly. Go into download mode on the phone, Vol down, home and power held down until reboots into download mode. Connect to pc on mobo usb ports with original data cable, you should get a connection in pc odin, then flash any gb rom initially just to see if it completes and if not, post back with the error.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
How large is the chance of bricking if I put my phone into download mode and flash a custom ROM with Odin?
georgeos said:
How large is the chance of bricking if I put my phone into download mode and flash a custom ROM with Odin?
Click to expand...
Click to collapse
Bricking is always a possibility, but pc odin is by far the safest method to flash. The possibility is very small that you'll run into any problems at all so long as you follow instructions and don't take shortcuts.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Bricking is always a possibility, but pc odin is by far the safest method to flash. The possibility is very small that you'll run into any problems at all so long as you follow instructions and don't take shortcuts.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thank you Got a friend helping me out now, pretty much doing what you've said to do except flashing ICS stock rather than a GB rom. Thanks though
georgeos said:
Thank you Got a friend helping me out now, pretty much doing what you've said to do except flashing ICS stock rather than a GB rom. Thanks though
Click to expand...
Click to collapse
If you're going for ics, make sure you flash a safe kernel such as Hydracore or philz or you run the risk of a superbrick.
Sent from my GT-N7000 using xda premium
He told you to do stock GB for a reason
Sent from my GT-N7000 using Tapatalk 2
asf58967 said:
He told you to do stock GB for a reason
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks -_-
SpyderTracks said:
If you're going for ics, make sure you flash a safe kernel such as Hydracore or philz or you run the risk of a superbrick.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did so! Working perfectly now, rocking BlackCNA
georgeos said:
Thanks -_-
Did so! Working perfectly now, rocking BlackCNA
Click to expand...
Click to collapse
Excellent, don't forget the thanks button
Sent from my GT-N7000 using xda premium
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
got a boot loop from trying to restore to stock, i came from cm 10.1 and i backed up cm 10.1 first then tried to restore but it decided to boot loop. it just stays at i897 screen, i am able to get into download mode, (haven't seen if odin recognizes it yet.) but no recovery at least i dont think, might be doing button combos wrong. i have only used odin a few times so i wouldnt know how to get back to stock, any help please?
Trozzul said:
got a boot loop from trying to restore to stock, i came from cm 10.1 and i backed up cm 10.1 first then tried to restore but it decided to boot loop. it just stays at i897 screen, i am able to get into download mode, (haven't seen if odin recognizes it yet.) but no recovery at least i dont think, might be doing button combos wrong. i have only used odin a few times so i wouldnt know how to get back to stock, any help please?
Click to expand...
Click to collapse
Get odin KK4 without bootloaders and flash it in download mode. From there, make it sure it boots up and flash korn kernel wih Odin 1.87 (or 1.85). From there, you're free to flash any ROM you want.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
Get odin KK4 without bootloaders and flash it in download mode. From there, make it sure it boots up and flash korn kernel wih Odin 1.87 (or 1.85). From there, you're free to flash any ROM you want.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
uh what lol? when i rooted it i followed a guide that made me update to stock gingerbread and get gingerbread bootloaders, i flashed korn kernel i think and was able to get root. dont quite know what to do sorry bruh xD
See this post for an Odin or Heimdall One Click to Stock i897ucKK4... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Instructions included.
Once ya get back to Stock KK4 (and maybe get Root if u wanna try that again), u probably need to stop there until u read up and get comfortable with the flashing processes etc. before u move on any further. :thumbup:
Trozzul said:
... i came from cm 10.1 and i backed up cm 10.1 first then tried to restore but it decided to boot loop.
Click to expand...
Click to collapse
You can't restore stock ROM (2.3.x) from CM10.1 (4.2.2). Different Android versions use different partitions. As mentioned in posts above, easiest way to go back to stock is Odin one-click file. No need to flash bootloaders again, so use version without bootloaders. In order to restore your CM10.1 backup you need to flash CM10.1 ROM first (to repartition), then flash same CM10.1 ROM one more time. When installing process is done, go ahead and restore your CM10.1 backup. No need to reboot the phone, nor install gapps. When restoring is complete, reboot the phone. Now you're back to your CM10.1 setup where you started from.
Easy to understand Captivate upgrade guide - https://docs.google.com/document/d/1YvC_lLbjk06WOttsifG8fD2QUHvC9_rDtZdNrDZKAFc/edit?pli=1
Val D. said:
You can't restore stock ROM (2.3.x) from CM10.1 (4.2.2). Different Android versions use different partitions. As mentioned in posts above, easiest way to go back to stock is Odin one-click file. No need to flash bootloaders again, so use version without bootloaders. In order to restore your CM10.1 backup you need to flash CM10.1 ROM first (to repartition), then flash same CM10.1 ROM one more time. When installing process is done, go ahead and restore your CM10.1 backup. No need to reboot the phone, nor install gapps. When restoring is complete, reboot the phone. Now you're back to your CM10.1 setup where you started from.
Easy to understand Captivate upgrade guide - https://docs.google.com/document/d/1YvC_lLbjk06WOttsifG8fD2QUHvC9_rDtZdNrDZKAFc/edit?pli=1
Click to expand...
Click to collapse
hmm interesting, i thought you were able to go to lower android versions, is this just like this for the cappy only? and soo pretty much alll i do is do what the guy said above me, and use your guide you gave me to root it?
Trozzul said:
hmm interesting, i thought you were able to go to lower android versions, is this just like this for the cappy only? and soo pretty much alll i do is do what the guy said above me, and use your guide you gave me to root it?
Click to expand...
Click to collapse
You can go lower, just gotta follow certain steps.
As for what you need to do, it was already all provided to you. I suggest you read through it a few times, make sure you fully understand it and then proceed with flashing.
That being said, right more you can do exactly what i told you and flash odin kk4 without bootloaders to have a working phone.
Sent from my SGH-I747 using xda app-developers app
4-2ndtwin said:
See this post for an Odin or Heimdall One Click to Stock i897ucKK4... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Instructions included.
Once ya get back to Stock KK4 (and maybe get Root if u wanna try that again), u probably need to stop there until u read up and get comfortable with the flashing processes etc. before u move on any further. :thumbup:
Click to expand...
Click to collapse
crap forgot to mention this is a rogers version (i896) not at&t. will this be a problem?
Trozzul said:
crap forgot to mention this is a rogers version (i896) not at&t. will this be a problem?
Click to expand...
Click to collapse
Nop, I'm on Rogers myself.
Trozzul said:
crap forgot to mention this is a rogers version (i896) not at&t. will this be a problem?
Click to expand...
Click to collapse
Rogers stock 2.3.3 Odin one-click is available also in sticky threads, if you prefer Rogers ROM. Just do a quick search.