Related
I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Did u try rebooting into cwm recovery and try to re install the rom again ?
U may need GB bootloaders as well for cm 9 (?? I'm not sure though)
Sent from my SAMSUNG-SGH-I777 using xda premium
If you still want to run cm9 try flashing a more recent kernel inn recovery. look in the Dev section for glitch kernel or devil kernel (i like devil) they have a more recent version of cwm that should work. I haven't used this method with cm9 but it worked with aokp.
Sent from phone with app
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
lan_baba said:
I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Click to expand...
Click to collapse
You should be good to go. You should be on GB bootloaders. Just reflash CM9 in CWM.
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
irfarf said:
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
Click to expand...
Click to collapse
lan_baba said:
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
Click to expand...
Click to collapse
you're welcome,
glad i can help
Hi, I'm stuck with installing new rom, so I hope, that you'll help me.
There are steps what I've done:
- followed THIS topic and ROOT the device with ODIN and CF-Root 4.4 file.
- OKAY, I'm rooted, so let's flash the new ROM
- entered in Clockworkmod Recovery and format EVERYTHING ( /data, /system, /cache, /sdcard etc.... just everything) for clear system
- next I load package with ROM and than INSTALLL
and here is the most important part
- when installed ROM gets something like bootloop but with restart - ROM is loading and after about 40 sec its RESTART
- and the same thing over and over again - restart ->loading->restart.... System never start up correctly to the end
- then when I saw that it does not work, I tried go into the CWM, but there was no CWM (!!!) - it was erased (by installing new ROM maybe???)
- so I must flash (old and stock) ROM via ODIN and again root device with CF-Root (with CWM) - that was only functional rom, what I was able to run, and again did this procedure
I tried this way, perhaps with millions of different ROM and EVERY was stucked (restart) while loading.
I think there are some non-deleted files in device, which should be erased (and which cannot be erased by CWM) for clear start of new installed ROM, what do you think?
Would someone please help me? I don't want old Gingerbread with Kies
Thanks for every responce!
Does it say in the thread that you have to flash a custom kernel?? Give.me the link for the thread so I can make sure that you've done everything right
Sent from ma 5assak
there is a link, but in hypertext THIS, i repost it in full text:
http://forum.xda-developers.com/showthread.php?t=788108
I think, when I've root and CWM, there is no problem and install a new rom will be very least, so not as it seems
Dude this is a kernel not a rom what's the matter with you??:what:
Sent from ma 5assak
please read all my topic - i flash this kernel only for clockworkmod recovery
through CWM I can flash any other rom
through ODIN only stock - cant find any ICS or JB rom which I can flash via ODIN (.tar file)
What variant of i9000 do you have? Are you sure that the rom you are trying to flash is made exactly for your variant?
EDIT: Try Darky ROM, they have an ODIN flashable version called "Resurrection Edition" or something.
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Samsung Galaxy S I9000, i'm sure 100%. NOT I9001, NOT Samsung Galaxy S2. Tried many roms from Development section for I9000, tried from get.cm etc... always the same result bootloop with restart
donhashem.dh said:
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Click to expand...
Click to collapse
OK. For example: this rom cm-9.0.0-galaxysmtd and cm-9-20120815-NIGHTLY-galaxysmtd from http://get.cm/?device=galaxysmtd
Or this one last ([ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S) http://forum.xda-developers.com/showthread.php?t=1778526 and 20120808 build.
and [ROM][PORT][ANDROID 4.1.1][BETA] TAJB: Jelly Bean port for Galaxy S V7.1 http://forum.xda-developers.com/showthread.php?t=1747042
and this too [4.0.4][ROM] Dark Knight 5.5 [27/4/2012] http://forum.xda-developers.com/showthread.php?t=1510940
and many more....
realy unhappy from this
Nikishek said:
Samsung Galaxy S I9000, i'm sure 100%t
Click to expand...
Click to collapse
I meant I9000 or I9000B or I9000M or I9000T there's a difference between them
I9000 only, checked it several times
Ok so you can flash Darky Rom Resurrection Edition through ODIN with no problem. Its GingerBread if i remember correctly, but it should give you a recovery mode and fully operating phone. From this point you can flash whatever you want.
....And there is one more important thing:
When I have a stock kernel and stock rom from Samsung, cant get into recovery mode - VOLUME UP and POWER non functional. Only when I type: "adb reboot recovery" in terminal.
Just after when I flash a new pre-rooted kernel with CWM, VOLUPE UP and POWER is now functional
k4Z3666: OK, I try and give you an echo I think, when I format everything in CWM, there will be no sign of the earlier system and ALL WILL BE CLEAR
Nikishek said:
I9000 only, checked it several times
Click to expand...
Click to collapse
ok, flashing ICS, may need to be done twice, as first flash may bootloop, IF you want to return to stock to get out of this mess, since you are not sure as to where you are now, due to flashing many roms, use any kit from My Android Collections, link below to get you to a booting ROM, than add a kernel with CWM (use EZbaze package with kernels)
that's helped me too thank you
Sent from my GT-I9000 using xda app-developers app
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Thanks to all who responded, if anyone else wants to reply feel free but i'm going to mark this as resolved so their won't be any confusion.
amd-dude said:
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Click to expand...
Click to collapse
if you are on stock kernel then download Philz kernel for LP7, flash that in recovery, should give you root again aswell. then you can flash away to any of the ROMs you listed above. just every time you flash a ROM or think of factory reset or data wiping make SURE you're on a SAFE kernel. that's all
as you are rooted, just install any safe kernel like hydracore or philz. thats all. then you can try out any rom. Just make sure you follow the instruction to flash the rom in the OP
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
amd-dude said:
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
Click to expand...
Click to collapse
this is the one you use - PhilZ-cwm6-UBLPC-UUB-2.7
http://www.mediafire.com/file/35d4kd...2.7-signed.zip
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
nokiamodeln91 said:
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
Click to expand...
Click to collapse
First, forget about the franco kernel. The franco kernel for the Note is outdated and thus useless. Second, if you plan to flash a JB leak the only kernel you should use is PhilZ. And especially important with the JB leaks is to stick exactly to the instructions how to flash. Otherwise your phone won't even boot.
Have fun with your device! The Note is still an outstanding phone.
Sent from my revived Galaxy Note
Thanks guys for the quick replies, i'm gonna flash the philz kernel now and give the leaked version of JB a try.
make nandroid backup 1st..
I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
c-droid said:
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
Click to expand...
Click to collapse
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
lulek01 said:
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
Click to expand...
Click to collapse
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
c-droid said:
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
Click to expand...
Click to collapse
Have you tried going back to stock android 2.3.6? Maybe that would work for you
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
tetakpatak said:
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
Click to expand...
Click to collapse
My last stock ROM was GB
lulek01 said:
My last stock ROM was GB
Click to expand...
Click to collapse
OK, then we know at least that your phone has a proper bootloader.
For people who upgrade directly from Froyo is very important to flash a GB bootloader, as all newer custom ROMs suppose that GB bootloader was already installed.
---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------
c-droid said:
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
Click to expand...
Click to collapse
You didn't get it mate.... I meant: which was your last stock ROM.... Froyo or Gingerbread?
Oh... sorry...
so... before I've flash the custom ROM SlimBean...
damn... I've already forgot, all I remember was I've waited for the phone's warranty to end before trying out custom ROMs, but I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
c-droid said:
Oh... sorry...
Click to expand...
Click to collapse
no problem
so... before I've flash the custom ROM SlimBean...
I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
Click to expand...
Click to collapse
Yep, probably you do have a Gingerbread bootloader then (2.3.x), after all the updates.
Froyo firmweres were 2.2.x
If not sure, here you can see it in my i9000 thread (also with video) how to flash only a bootloader and there you can download all the files.
Make sure to read whole the step-by-step guide for flashing with Odin under section 2 as flashing a bootloader shouldn't go wrong.
Thanks tetakpatak,
I've read your thread, specially the warning regarding flashing bootloader that one mistake could hard brick the phone.
So, I wanted to clarify some things before I proceed on flashing the bootloader...
1. The baseband of the bootloader attached on your thread is XWJVU while my phone is XXJVK, should I search for bootloader the same as mine or the one on your thread is fine?
2. On your thread, the text guide says to choose the bootloader file under "PDA", but on the video, you choose it under "BOOTLOADER", I assume the video is correct as I can see the phone successfully boots...
3. I couldn't see clearly on the video and also not specifically stated on your text guide if I have to choose on Odin the "i9000Boot_XWJVU.zip" file or I have to extract first the "i9000Boot_XWJVU.tar" inside it and choose that one...
Sorry if I asked too much, not that I'm skeptical with your giude, just following your warning...
I was about to try tetakpatak guide on flashing only the bootloader, but I don't know why my phone was not detected by Odin?
I run Odin as administrator, choose the bootloader file, tick the "Phone Bootloader Update" and uncheck "Auto Reboot", then turn-on the phone to download mode, connect to PC, Windows detected the phone as "Gadget Serial device", but did not appear on Odin...