Hi Guys, I have a SGS i9000M, and I used this forum post http://forum.xda-developers.com/showthread.php?t=1379650 to install CWM and ICS 4.0.3. I also installed Semaphore Kernel 1.2.0. It was working great for a month until I was messing with the Semaphore settings and enabled Bigmem, then when I rebooted it was stuck on the Semaphore Kernel screen, I couldn't get into CWM, but I could get into Downloading Mode.
I Run Odin 1.85 and select my I9000UGKG3-homebinary.tar file to go back to stock and when I do, I get the message: Cannot open the specified file (Line 1876). I have downloaded 3 different versions of that file, so I know it's not the file.
I've tried every combination of buttons I can, but it's not going into CWM, I just get the black screen of death whenever I reboot any way other than into Downloading Mode.
Can anyone please help me? Thanks!
*Edit: I flashed the PIT, PDA, CSC of the JVP Rom from the above linked post, and got it going, flashed chainfire, it works fine up until then, but when I install the ICS zip, it just flashes some installing stuff, then reboots, over and over, never completing, please help! I've tried different downloads of ICS 4. To repeat: It works fine installing Gingerbread and chainfire, but ICS gets stuck in a loop during install!
I remember something similar when I first flashed to ICS.
I just popped the battery out for a bit, not too long, and then re-flashed the ICS ROM. I was using the teamhacksung rom.
You could try flashing cm9 nightly (galaxysmtd), and Google Apps, and the cm7-kg3 modem.
I can't emphasize enough that you have to read, read, and re-read so that you do it exactly as written. There are lots of youtube videos that may aide you seeing what the "word instructions" mean.
Persist and you will get there.
As the the op says in the second thread of the link you quoted:
if your upgrade to ICS fail
do not despair...
just repeat the Odin steps to get back to KG3 stock + CWR
and flash another ICS build
A further thought may be that you do a factory reset at the beginning of your process. Make sure anything precious is saved to your external sd card.
Hi there, thanks for your reply. I will try your suggestion of the factory reset at the beginning. *Edit: tried, and same problem. When I go to flash stock rom I9000UGKG3, error Line 1876.
The problem i'm having is I can't flash back to KG3 stock, when I try to flash I9000UGKG3-homebinary.tar file to go back to stock, I get the message: Cannot open the specified file (Line 1876). All I can do is load the JVP rom. I have tried multiple different downloads of my I9000UGKG3 stock rom.
I've left the battery out overnight, and tried to flash all different versions of ICS multiple times. I do agree with the 'try again and wait' theory that goes with this stuff, because it works, but in this situation, it gives me the same error 1876 every time, I can't flash back to stock. That might be why I can't install ICS.
I was able to do all of this first time before and ran ICS 4.0.3 with Semaphore Kernel for a month before I messed it up.
Anyone know any other ways to get back to stock?
Thanks!
Hi,
Here some stuff I had in my notes, I'm just copy/pasting, excuse the repitition.
Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.
http://forum.xda-developers.com/show....php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.
I remember ODIN flashing JVU before going to ICS. Just wanted to see what the value pack was all about.
PDA - use JVT/JVU
Phone - KG3
CSC - KG3
PIT - 512
Re-Partition - ON
Auto Reboot - ON
F. Reset Time - ON
---------- Post added at 01:47 PM ---------- Previous post was at 01:36 PM ----------
Here was something else in my notes:
Recovery
Mounts and storage - Format cache, data, and system
Flash stock
Hiya, thanks again for your reply. I also live in BC, Vancouver.
I will try your further suggestions, thanks so much for sharing your notes.
The link included seems to be dead, any chance to find the thread it would have pointed to?
Cheers.
Here it is:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJW6, XWJW5, XXJW4]
I'm in Kelowna-fornia.
fixed - ICS install issue
That's sweet, Kelowna is a nice area :>
Well, I worked my butt off for almost two weeks, 4 hours a night.
I should start off by saying I still cannot boot to Clockwork Recovery with any button combination, i've tried all the usual suspects and then some atleast 50 times, probably way more. The only way I can is once in awhile a miracle occurs and it reboots to Clockwork Recovery 5 (the blue text themed one), or if I install CF-Root and use to reboot into recovery in it's options.
I should also mention that whenever I do get into Clockwork Recovery, it's like version 3, with the orange text theme. And I don't know if it helped, but I am now using Odin 1.87 instead of 1.85.
I was finally able to flash stock by flashing the 4 separate files, 512 Pit, PDA, Phone, and CSC rather than flashing the UGK3homebinary.tar.
I tried multiple different versions of Gingerbread with CF-Root to try to get ICS or CM9 working, JVT, JW1, JVU, all of them worked, but the same thing happened when going to install ICS, and even CM9, the install would start, once it got to the part where it says "Rebooting if necessary" on the ICS or CM9 install, it would reboot, show the install beginning again, then reboot at the same spot, infinitely. I made sure to try atleast 50 times so I could bypass the suggestion of trying again.
During this process the phone was acting very buggy, you know what I mean, restarting, freezing, force stops, mounting storage issues. I went into the options and set the phone to factory default, also during another miracle one time it booted to the stock android recovery, you know the one with like 4 options. Format, Wipe, go back, reboot. I formatted and wiped from there as well. These two things seemed to help alot, and the phone was less buggy and more willing to receive my treatments.
After browsing some more, I found this kernel cleaner, i'm surprised no one in the forum mentioned it to me, perhaps they were angry I hadn't discovered it on my own. In any case it's called 'Ultimate Kernel Cleaning Script - 4.0 [MIUI/CM7 and SAMSUNG]', there is one for Samsung Roms and one for CM roms, and all you do is run it to clean out the old before installing ICS. Link: http://forum.xda-developers.com/showthread.php?t=1166954
Ok, so I am now I am excited, this tool looks like my answer. I flash stock, install JVT rom with CF-Root for JVT, (I run my sweet kernel cleaner zip I found) and go for ICS 4.0.3 install.....and same thing happens, sigh. Flash stock again, and oh what's this? I found another custom ICS Rom I can try, remICS http://forum.xda-developers.com/showthread.php?t=1687727
Ok, so I flash stock again, install JVT, CF-Root for JVT, install remICS and....D'oh! Same thing, it's rebooting........but wait, this time it's rebooted into Clockwork Recovery 5 on it's own without any keypress, instead of looping. What a great time for that Miracle! (This only happened 3 times in about 60 hours of working on the phone!) Ok, but what to do now? Well, ICS didn't really install, it just started to, maybe i'll try to restart the install from in here! Choose install zip, this time I chose remICS only because so far it had the lesser fail rate - I didn't want to mess up this golden opportunity, I know it's just a different version of Clockwork popping up, but when anything different than the same failures happens, you don't want to waste it. It's installing....complete! Do I dare risk installing a customer kernel and destroying all of my progress? Yes! Install Semaphore 1.2.6 for ICS, working great!
So, I don't know if it was the kernel cleaner, the remICS, or the miracle Clockwork 5 boot, but I don't want to take anymore chances, that's how I got here, fiddling with what's working great already.
I probably didn't need to post this, but I wanted to recount my experience for anyone else having a similar problem. I have now been running stable with all my apps installed for 12 hours. I would like to have stock ICS with phone rooted, but I don't want to take any chances. This remICS custom rom is very nice, speedy and alot of the bloatware removed, along with some killer SGS3 menus and layout.
I would like especially to thank my Canadian friend for helping me :victory:
Related
Hi guys,
I have browsed the forum and have tried several of the remedies here but still no luck. I have been running Darkyy's 9.0.2 rom for a few weeks now, with a 500hz- speedmod kernel (don't remember what flavour, but was flashed via CWM). It has been running great since I flashed.
The problem arose when I went into settings to simply change the lock screen. I selected another lockscreen and my phone rebooted. Then it gave me quite a few FC errors,so I decided to boot into recovery and 'restore' a previous save. Now my phone just shows the samsung logo and reboots.
I am able to get into download mode but not recovery. This will be the fourth time I have to send it away. Is there another option or is this still my only option?
Any thing specific I should try to flash.
If it helps I am on the BEll network (gt-i9000M)
try to flash JPY base stock ROM with Odin......
try without repartition and pit (1 file PDA, no pit file from samfirmware.com)....
Then flash the latest speedmod kernel.....
Now it should work (maybe! XD)!!
Thanks for your reply, I tried your suggestion but still the same problem. I also tried all of the suggestions on this link. I finally was able to get into the recovery console by flashing JPY (no part, no pit), then immediately flash JL2 (with bootloader, no flash, no pit) but I got the dreaded 'no such directory'...again. So I am SOL but have to take it back today.
Did you tried flashing with 3 files + pit + repartition?
With this method it should work...
Remember: no bootloader update!
Sent from my GT-I9000 using XDA App
Did you ever upgrade to the official Bell JL2? If not, I'd probably do that through Odin and have it update the bootloader. I had gone from JH2 to different cooked roms and would always run into corruption/fc problems a week later. And eventually the phone would just not boot into the OS. The last time it happened, even flashing to another cooked ROM would not work. The official bell JL2 has an bootloader update that seemed to have fixed the issues I was having.
Booted official JL2 and remembered how much I hated lag After that, flashed a 2e kernel through Odin then seeARM's cooked JL2 through clockwork. Been running that for 3 weeks now without any issues.
Hi Guys,
I should probably write down what I flash when I flash it. I honestly do not remember what I flashed. I went through all the threads I could find and tried everything. So to answer your question, I cannot say for sure if I did that or not. But I ended up sending the phone away. It was weird, I asked my fiance to take my phone in while I was at work. She called me later that day and told me that her phone did the same thing so she sent hers back the same day....weird.
Ok guys, first i want to apologize for asking, but i still am a newbie and have absolutely no skills in AOS development. All i do is follow guides.
After a lot of reading in your forum, i finally had enough courage to root my phone, flash a kernel and a custom ROM.
Well everything went well, i flashed webstar1's Ultibread v1.4 ROM, and my phone started flying, it was awzum
But it seems it has corrupt graphix (at startup, in some games some times etc etc)
So i wanted to switch to another ROM, BUT when i enter CWM recovery (vol up+home+power) its gfx are effin messed up! After a lotta guessing i finally found *reboot system now* so i got out of recovery, but damn it... how do i change my ROM, wipe data and such when i cant see what im pressiing in recovery?!?!
So here is my Question: how do i fix CWM recovery?
Things i've tried:
multiple reboots
ROM manager
reboot into recovery from Ultibread v1.4's power menu.
Oh and, i can enter download mode with no probs. So if there is a way i could wipe out everything and go back to Froyo, to start over, it would be best.
Thank you all for your caring and attention in advance!
well if you cant make sense of recovery, try flashing a rom thru odin, maybe go back to stock and start again,
All stock firmwares can be found at www.samfirmware.com or on the first page of general on this forum.
Ok so, how do u flash a stock firmware... same way as kernels? And what is the pit file for?
Oh and... how do i say "thanks"? ;p
Edit: i saw the thanks button once i logged in
similar to flashing a kernel only with more files... there should be a instruction guide where you downloaded your ROM from... its pretty simple PROVIDING YOU READ PROPERLY,,
and finally PIT file is incase you have had a lagfix or something activated to change from ext 2 / 3 / 4 back to stock RFS.. you should only use pit if you have a 3 file firmware.
Ok so i when ive first entered CWM recovery after installing Ultibread (yeah it wasnt bugged for a while) there were lagfix options
Does that mean i have to install a pit file?
Edit: so this is what it shows me when i dial *#1234#
PDA: I9000XWJV1
PHONE: I9000XXJVE
CSC: I9000XXJV1
So is that the 3 files u are talking about?
Edit2: Ok i flashed a stock 2.3.2 firmware, so its all good all. Except it has Froyo interface LULZ.
I do plan on getting Darky's ROM, since its the commercial choice as i see, what would you advice me, azzledazzle?
I do plan on getting Darky's ROM, since its the commercial choice
Its not commercial at all neither is it the best its just one guys constantly changing rom .Its the choice of newbies for some unfathomable reason .
Go to the developers section and read up on the different roms .
jje
Jimmybg said:
Ok so i when ive first entered CWM recovery after installing Ultibread (yeah it wasnt bugged for a while) there were lagfix options
Does that mean i have to install a pit file?
Edit: so this is what it shows me when i dial *#1234#
PDA: I9000XWJV1
PHONE: I9000XXJVE
CSC: I9000XXJV1
So is that the 3 files u are talking about?
Edit2: Ok i flashed a stock 2.3.2 firmware, so its all good all. Except it has Froyo interface LULZ.
I do plan on getting Darky's ROM, since its the commercial choice as i see, what would you advice me, azzledazzle?
Click to expand...
Click to collapse
It all depends what you want.. your best option would be to go to www.romkitchen.org there you can build your own rom to your own likings, its very good and is always upto date with the latests version of ROMs,
just choose your rom, cook it up, and flash it thru CWM.. if u have any troubles PM me
Similar to Masterslackers issue.
The phone was originally a stock Optus Éclair 2.1. About 6 months ago I decided to customize the i9000 with a custom Froyo 2.2.1 Rom (Doc's Rom Docs_XWJS3_Wipe-v9_1) from “The ROM Kitchen”. It worked really well and was much faster and responsive..
Yesterday, I decided to look at a move to Gingerbread and cook another ROM @ the ROM Kitchen, this time a Gingerbread 2.3.4 iteration.
The phone was rooted so I used Rom Manager to get into recovery mode where I could flash my new, Doc's JVR_No_Wipe-v8-00-08-22-10-09-4e6a8e4e86718.zip Rom.
All seemed to go well, but after the Flash, as the phone booted the first screen became filled with 100s of random coloured lines, then it transitioned to the normal Samsung start animation, but soundless.
After booting, I noticed that I no longer had a notification bar where battery, time, signal strength etc. was normally displayed atop the screen. I tried several different launchers to see if that was the issue, but to no avail. I tried to enable the notification bar using Go Launchers gesture setting (no go)
I tried rebooting the phone over and over, the notification bar would not return.
I was starting to lament my decision to flash when the following occurred.
I tried to re-enter recovery mode via ROM Manager to install a different ROM, but the phone bypassed it and then hung @ the Samsung I9000 logo screen. I then had to power the phone off before it would reboot into its UI. I could no longer reach recovery mode by any means.
Because I was getting nowhere and I had read that after flashing a new rom, root would often be lost, so I tried rerooting with "XXJVP-Complete-Rooting-Package" from
http://androidadvices.com/how-to-root-galaxy-s-on-android-2-3-4-xxjvp-firmware/ This also failed but it has also left me with a soft bricked phone.
The phone will not boot up or boot into recovery now, however It would still boot into (3 button) download mode.
I have tried various versions of Odin from v1.0 to v4.28 to ReFlash the phone back to life but with no success yet.
Using Odin, the phone hangs with no sign of progress and reports the following when left for 30minutes or so.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
Anyone have any suggestions that might help to get the phone back.
Thanks, TeZ
So you didn't flash stock gingerbread before flashing custom rom? so you should first flash stock jvr and do hard reset after booting. Then you are safe to flash cwm capable kernel and custom rom.
For the odin problems, maybe you have kies running in background? Kill all kies processes and try again.
And I'd suggest reading all guides found in romkitchen thread..it saves lots of trouble. Hope that can fix your phone
Sent from my GT-I9000 using xda premium
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Thanks for that, I did install kies after I bricked it, in the hope (probably missguided) that it would somehow help. Uninstalling
bigmadpete said:
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
Click to expand...
Click to collapse
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Your post looks promising, I'm going to try this method out and see where it leads. I'll reply back with the outcome, many thanks
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
bigmadpete said:
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
Click to expand...
Click to collapse
Thanks for the info, running out of time today, will try for tomorrow
When moving from a froyo (2.2) rom to gingerbread, (2.3), you need the gingerbread bootloaders or you'll get all sorts of crap when turning on your phone (ie what you have).
Use odin to flash back to froyo, or flash a gingerbread firmware that comes with bootloaders. (I would recommend going back to froyo first to make sure everything is ok, since flashing bootloaders is a bit risky, as messing it up can permanently brick your phone)
cobrasixtysix said:
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
Click to expand...
Click to collapse
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Ok, here's where I'm at:
For the sake of simplicity I will detail what gave positive results rather than a tirade of what didn't.
Uninstalled Kies, rebooted
As instructed, went to:
http://forum.xda-developers.com/showthread.php?t=1102881
downloaded: Odin v1.82
downloaded: Gingerbread 2.3.3 (Australia and New Zealand)
XWJVN/XXJVQ/XSAJV5/Sbl (CSC: XSA): Download (150 MB) (Build date: Sun Jul 10 11:30:54 KST 2011)
Loaded up Odin and followed instructions.
Flash went ahead as normal and I now have a working phone again, thanks to you DSGE, I'm a very happy man
So I now have Gingerbread 2.3.3 installed and running.
My only issue's now is, that.
1. Half my apps dont work now or force close even after a reinstall.
2. Some apps won't install at all IE; my fav launcher; Go Launcher
3. I no longer have root access so Rom Manager and Titanium backup wont work.
4. My Backup Pro, works after I rewrote the correct path to the External Sd, but do I want to do that just yet? and just how much data should I reinstate so I don't corrupt the new system?
What should I do now?
Install busybox?
do a hard reset?
Flash a different Rom that will work for me?
Thanks so very much for all the good advise.
Cheers
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
bigmadpete said:
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
Click to expand...
Click to collapse
OK, latest update:
Everything is working fine including all my progs.
Like you say, I just need to root it now.
Can you point me to the correct files to root?
Thanks
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
bigmadpete said:
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
Click to expand...
Click to collapse
Seems to relate to 2.1 to 2.2.1 didn't see any mention of 2.3.3. I'm afraid I'll stuff the phone if I use the old root files.
I was on Slim ICS and downloaded an update (2.8) which was to include a wifi toggle fix. After downloading directly to my phone, I tried to install it and it started looping (kernel then into recovery). I could not stop it in recovery. It would loop through the boot up and then I could see the recovery and but it said something about not being able to read zip file (corrupted download?). It just kept looping.
I was able to get Odin to work once (that is why I get the AT&T screen). Now, I can get Odin to recognize my phone but I cannot get beyond that. I have tried to reflash kernels that have worked before (assuming that I needed to start over). But Odin just sits there with the tar file in the pda section (for well over five minutes). Working on a Windows 7 machine (64-bit).
My phone's current status is that it is frozen at the AT&T screen (from the boog kernel without bootloaders - since I was on gingerbread before). I can get into download (volume buttons, plug in USB).
FYI, in the past I had flashed Continuum, Andromeda3, Mosaic IX, Fusion ICS, and Slim ICS, without a problem other than a soft brick or two that I was able to fix using Heimdall. (I am realizing I know/knew enough to be dangerous)
Am I "bricked" or can it be repaired.
Any direction as to what to do right now would be greatly appreciated.
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Red_81 said:
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Click to expand...
Click to collapse
I will try it again but I did try once with Odin and after about ten minutes, I cancelled the process (hopefully that did not add to my problems). It seemed to be hung up on the message, "Do Not Turn Target Off," but there was no process started.
Try a heimdall one click then. It might solve the issue.
Red_81 said:
Try a heimdall one click then. It might solve the issue.
Click to expand...
Click to collapse
Red_81,
Thank you!
Heimdall worked (http://forum.xda-developers.com/showthread.php?t=1300843)! Although I loaded the version that contains bootloaders, it actually flashes the kernel first and then give you the opportunity to flash again installing the bootloaders. Since the phone worked after the first flash, I did not bother doing a second flash. Now, back to Slim ICS!
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Red_81 said:
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Click to expand...
Click to collapse
Heimdall worked but I was left with two problems. One was that the Kernel installed by Heimdall did not have CWM in it, which I need to flash Slim ICS.
The second problem is that my computer will not recognize my device when I try to use Odin since Heimdall installs different drivers (I have read about how to covert to Odin and/or uninstall/replace the drivers, but it is hard to find that time given family and job obligations).
Since Heimdall did work to fix my original problem work, I found a package to install Apex 12.4 (http://apex.merseine.us/installation/) on my phone. I did this so I can have a working copy of CWM in order to re-flash Slim ICS.
Given the travails of the last two days, I may wait a battery charge or two on Apex (lots of customization but higher battery drain, which is why I went from Fusion ICS to Slim in the first place).
Anyway, thanks again for your help.
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Red_81 said:
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Click to expand...
Click to collapse
Believe me, I tried seven ports on three different computers with two different cords (my Kindle cord is actually the most dependable ).
I then searched for a Heimdall package that had CWM. It has a Talon kernel with CWM 3.0.x and I can get into recovery with the option of installing from my internal sd card.
I just have to wait for my nerves to settle (and this is a very fash gb rom and I have had no issues yet).
hello,
i bought a fresh n7000 with stock ics firmware on it. i wanted to go to paranoid android.
1. i rooted the stock ics
2. found out that i need gingerbread to flash custom firmware
3. installed sdk, driver on ubuntu
4. installed heimdall, as its the odin for linux
5. downloaded N7000XXKJ4 from samfirmware.com
6. extracted it to have the single images to flash with heimdall 1.3.1
7. booted in download mode, attached the phone to usb and hitted detect device in heimdall
8. device was found
9. started flashing, first without repartition
boot.img as BOOT
param.lfs as PARAM
factoryfs.img as FACTORYFS
cache.img as CACHE
zImage as KERNEL
Sbl.bin as SBL1
hidden.img as HIDDEN
modem.bin as MODEM
10. flashing went all thru, the phones screen showed the progress also
11. phone did a reboot, after all flashing was done
12. stuck at bootscreen
13. found in the web that its normal and i should do a factory reset in the recovery (its not cwm)
14. stuck at bootscreen
15. repeated step 9. with pit file and repartition
16. same bootscreen
i know the phone is not dead, just not booting, but i have absolutely no chance to find out what to flash exactly and how to do it.
hm could i now just flash the abyss kernel and cwm recovery.bin or so and install a custom rom?
if you are now on GB then flash a kernel, either in CWM or odin and do a full factory reset along with all caches and dalvik cache.
i wouldnt recommend flashing a custom ROM until the stock rom is booting, you dont want to be covering up any underlying errors.
Also, Why did you re-partition ? Did you re-partition using a 3 file firmware (PDA, CSC, Phone) or just a single firmware - PDA ??
hm i dont know on what i am, because it doesnt boot.
i thought i eventually had to repartition because i changed from 4.0 to 2.3.5 ... i used the n7000 16gb pit file.
Well what did ODIN say ? Did it complete or did it get stuck and fail ?
You can flash a kernel in ODIN which should allow you to enter CWM and do a wipe, However you might get issues if you flash a GB kernel over ICS Firmware and vice versa
heimdall ran complete through, said its all fine and the phone rebooted at the end of flashing as it should be. seems all perfect.
the issues i get can not be worse?! if i would now flash a gb kernel, even if there is ics under the hood, the phone would also just not boot?!
I dont know really, Ive never tried, nor do i intend to lol.
But i imagine GB is now on your phone considering it all passed without fail So i guess you should try to flash a kernel and then do a full wipe and see if it boots then
chances are there are some ICS files left on the system preventing it from booting.
and following the guides on xda im not allowed to flash the other kernel with heimdall/odin.
i should use the cf-kernel for my firmware and flash it with the bat-script, is this correct?
Just flash this in ODIN and you will be fine
https://dl.dropbox.com/u/69014495/GingerBread-speedmod-kernel-n7000-k2-12-Odin.tar
boot into recovery, do a factory reset, then clear cache partition, then go to advanced and clear dalvik cache, then reboot
then report back
ok. now i have the yellow triangle. i wanted to avoid this.
BUT it looks very promising. clockword mod is starting. did the wipes. and when i reboot it boots directly in cwm. i think this is good atm.
i have to leave at work now. tomorrow morning i can flash a rom with cwm right? and if i flash an ics rom, then i have to flash a ics kernel, too?!
Dont worry about the triangle, Use this app to remove it https://dl.dropbox.com/u/69014495/eu.chainfire.triangleaway-47fe5bbd55070e4eddce741c0ef13110.apk
Like i said above, Make sure the phone boots before flashing any other ROMs. If you want to upgrade to ICS you will need to flash ICS in ODIN, Unless you want to use a CM9 / AOSP based ROM like Paranoid Android, In this case you will stay on GB, Just full wipe and flash ROM in CWM
EDIT: I mis read your post, Your phone is not booting, But only booting into CWM, In this case, try a custom ROM, Nothing to extreme just a simple GB ROM and see if it boots properly then
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
xmaskx said:
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
Click to expand...
Click to collapse
Your welcome!
Glad to see you're up and running again
Oh and if you go to your very first post on this thread, Click edit then you should be able to put [Solved] in the title bar
Buddy start from crap...and one advice..u never know the depth of an ocean unless u dive into it..be brave...just follow cursed4eva tutorials on youtube.u will know everything...and only u can teach uraelf no one else..what i did when i was a boy,i mean when i was new to note,i followed this guy and he saved my daymy recommendations is to use odin...flash a 3file rom whose links are provided in cursed4eva's video..and flash it...u will be on stock gb..
Sent from my GT-N7000 using xda app-developers app