[Q] CWM not installing - Galaxy S 4 Active Q&A, Help & Troubleshooting

Hello!
I was trying to root my samsung galaxs s4 active (GT-I9295). I installed usb drivera and used odin 3.07 and cwm v1-2(CWM-Recovery-gt-i9295_v1-2.tar.md5). I turned my phone off and back on with volume down pressed and then confirmed with volume up, after that I plugged in usb cable(original one) and launched odin with administrative rights. In odin I clicked PDA and added the downloaded .tar.md5 file, then I pressed start and it flashed the file on the phone and rebooted the phone. After the phone booted and asked me for pin a popup showed saying couldn't download, try again later. To make myself sure I restarted my phone with volume up being pressed and it opened android recovery, not cwm. I tried the same thing on multiple pcs and usb ports(I even tried on linux but didn't get far because as it seems heimdall doesn't accept .tar.md5 ). I even tried using another cwm image(recovery_6.0.4.7.tar.md5).
Does anyone have an Idea what could be causing this?

batlefield said:
Hello!
I was trying to root my samsung galaxs s4 active (GT-I9295). I installed usb drivera and used odin 3.07 and cwm v1-2(CWM-Recovery-gt-i9295_v1-2.tar.md5). I turned my phone off and back on with volume down pressed and then confirmed with volume up, after that I plugged in usb cable(original one) and launched odin with administrative rights. In odin I clicked PDA and added the downloaded .tar.md5 file, then I pressed start and it flashed the file on the phone and rebooted the phone. After the phone booted and asked me for pin a popup showed saying couldn't download, try again later. To make myself sure I restarted my phone with volume up being pressed and it opened android recovery, not cwm. I tried the same thing on multiple pcs and usb ports(I even tried on linux but didn't get far because as it seems heimdall doesn't accept .tar.md5 ). I even tried using another cwm image(recovery_6.0.4.7.tar.md5).
Does anyone have an Idea what could be causing this?
Click to expand...
Click to collapse
Try a different cable, try a different version of Odin (3.08 is the one I used). Can you better describe what happens when you boot now? Does it boot to your ROM normally or do you get a black screen or does it boot loop, etc.

I will try and use another cable(the one I used to flash nexus 7), I already tried using other versions of odin but results were the same. After flashing I can boot normally there is no bootloop or black screen or anything like that, the only problem is that i cant get into cwm - when I try to (power + volume up) it doesn't put me into cwm recovery but it puts me in stock android system recovery. It also seems like that odin does something since when I go to ota update menu it says device was changed and when I go in download mode it says im using custom something, I can't really remember now :-/ but i think it says custom firmware and custom bootloader(don't take me for granted on that!). So yeah the only problem is a) cwm isn't installed or b) im too stupid to get into cwm

Related

[Q] Can't enter download mode after running Odin

Hello,
I verified that I am able to enter download mode by plugging in the USB cable while pressing both volume buttons with the device turned off. I also verified that I can enter recovery mode by pressing both volume buttons and the power button. So I am pretty sure that I know how to enter the modes.
I then ran the Odin version from http://forum.xda-developers.com/showthread.php?t=731989 (by mistake, I didn't know it differed from the one in http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html). I assume that simply overrode everything with the stock ROM instead because I did not get the chance to select the SpeedMod kernel.
However, after that the hotkey method was no longer working. I was only able to enter download and recovery mode using adb. I used this to flash SpeedMod using the correct Odin version from the SpeedMod page.
Then I proceeded by going into recovery mode and extracting captivate-efsbackup.zip. I went into download mode (again with adb, keys still didn't work) and flashed cm7-captivate-initial-kernel.tar.
Now, however, I'm in real trouble. I can enter neither recovery nor download mode. No matter if I use hotkeys or adb, the system reboots, but then just shows the "Galaxy S\n cyanogen^(mod)" image.
Anyone able to help? Why aren't the hotkeys working anymore after running Odin?
I have no explanationas to why buy do have a suggestion. Try the AIO tool box. If the phone boots, just enable usb debugging and follow instructions. You should probably use the 3 button fix option.
I recently had done a clean up of my cappy because after tons of flashes it had become a mess. After flashing back to stock I lost dl mode and recovery. Whipped out the AIO...ver.2.5 , booted phone, put in debug.. Reformated with 3 button and boom!, back in business. Be sure your net framework is current 4 version, install the C++ lib as siggested.
Took a likely pain in the ass and turned it into an inconvenience. Just follow the instructions...
Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
First of all, what model of Captivate do you have (the model number is underneath your battery, on the phone itself. It will be a number between 1006-1014).
And I hope you do realise that CM7 is a particularly difficult (than standard) ROM to flash, and if you don't know what you're doing (or miss a step), you can perma-brick your phone easily.
If you can't get into Download Mode by any means, then the only last suggestion I can give you is to try a USB Jig (search around in the Captivate Forum here, you'll see what I mean).
Thanks for the suggestions. Here is how I recovered:
Download SpeedMod Kernel
Create a nandroid backup on a working phone, copy that over to the broken one
Copy zImage from SpeedMod kernel to SD on broken phone with adb
Enter shell mode on phone
Look into misc/recovery.fstab to figure out the name of the sdcard block device
Mount sdcard with `mount [blockdev] /sdcard`
Flash zImage with `flash_image boot /sdcard/zImage`
Flash nandroid backups with `flash_image {system,cache,datadata} /sdcard/{system,cache,datadata}.img` (but not data)
Leave the phone without battery for at least 1 and at most 6 hours (my phone appeared completely dead after this operation, not even adb shell access, so I went to bed frustrated)
Now you can boot into download mode again using "adb reboot download" (which didn't work when running the CM7 kernel)
Use One Click Odin to revert to stock firmware
Install 3ButtonFix to get combos working again
Note that the original problem that caused all the trouble was that flashing the stock ROM with Odin One-Click disables the 3 Button combos. You have to use the 3ButtonFix to get it working again.
Nikratio please help me i was updating samsung galaxy 5 2.1 eclair to 2.2 froyo but when i was using odin then it stops working and i unplug the device the after that phone is not getting switched on and even not getting is recovery mode ... m very sad and even dnt have the backup of any phone and none of my frnd have android phones so that i have backup please help me bro m afraid of my mom too coz i just bought it few time back please hem me bro

Odin successful, but still stuck in boot loop

TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM
Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.
Just out of curiosity, what is your build number?
I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.
May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App
I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?
Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App
I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?
You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.
FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)
ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......
Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.

ODIN flash mistake...

Okay so I was flashing through ODIN, and I flashed through the PHONE section instead of PDA because for some reason I turn into Dolan Duck at 11 PM. Now ODIN won't get past "Setup connection..." and Heimdall gets an error when it attempts to "handshake with Loke". Switched to three different computers and it always acts the same, so I'm thinking I might have really jacked the ability to write directly onto the phone through the computer. Phone still powers on, but just boots to the AT&T world phone screen and stays there. No recovery mode so if I can have a way to fix this and get a kernel written onto my phone that'd be really great.
treygrizzard26 said:
Okay so I was flashing through ODIN, and I flashed through the PHONE section instead of PDA because for some reason I turn into Dolan Duck at 11 PM. Now ODIN won't get past "Setup connection..." and Heimdall gets an error when it attempts to "handshake with Loke". Switched to three different computers and it always acts the same, so I'm thinking I might have really jacked the ability to write directly onto the phone through the computer. Phone still powers on, but just boots to the AT&T world phone screen and stays there. No recovery mode so if I can have a way to fix this and get a kernel written onto my phone that'd be really great.
Click to expand...
Click to collapse
Hey hi,
1. By far the best way to go back to Stock ROM's :good:
2. I'm not sure if this is exactly the solution to your problem but hope it works.
- I've had problems with heimdall and odin, drivers not being compatible, the driver that is installed for heimdall doesn't seem to work with odin and if you try installing the driver to get the odin to work, heimdall stops working. So your best option would be to try this:
a. Go to the forum link above, download all the required files.
b. switch off your phone, wait for 3s, then hold the volume buttons "+" and "-" at the same time, you can just use your thumb, but those two buttons must be pressed at the same time, now hold it! Insert the usb connector from the laptop/pc to your phone via the micro usb slot. Wait for it.. and voila you are in download mode.
c. Now, if you are running Odin and if you HAVE the correct drivers, you will have the correct green/yellow indication when you use the software, which basically tells you that there is a "handshake" between the Odin and cappy.
d. Once this is done, you can follow the steps that you were planning to do, otherwise follow the steps from the thread posted above. one by one.
If you already have ROM's on the SD card, and you've already got CWM on the phone, you just need to go into recovery mode(hold the volume buttons and then hold onto the power button, it should work, otherwise give it another shot ), once in recovery you can install the new ROM using the normal method.
(a suggestion) Most people face problems coz the driver installed isn't the right one, so if you are using windows OS, and the drivers aren't detected, download the drivers again, go into device manager, completely uninstall the driver for samsung captivate, and install the one that is working.
Watch how it is done using one touch Odin3 --> here
If you are upgrading your ROM to ICS, after you flash the ROM, flash the Devil kernel for cappy, --> is a good one :good:
**Always remember to back up data**A clean install is always preferable**
---------- Post added at 09:26 PM ---------- Previous post was at 09:01 PM ----------
You can also try reading this post http://forum.xda-developers.com/showthread.php?t=1671969
Yeah the little box turns yellow in ODIN but it just hangs there at setup connection. I also, sadly, don't have recovery mode because my kernel flash is when it all went terribly wrong. I can connect to ODIN and Heimdall with no problem because I have the respective drivers, the problem just seems to lie in the fact that neither program can write to the device so it continually hangs.
treygrizzard26 said:
Yeah the little box turns yellow in ODIN but it just hangs there at setup connection. I also, sadly, don't have recovery mode because my kernel flash is when it all went terribly wrong. I can connect to ODIN and Heimdall with no problem because I have the respective drivers, the problem just seems to lie in the fact that neither program can write to the device so it continually hangs.
Click to expand...
Click to collapse
quick question for clarification, the phone is in download mode and then u connect it to ODIN and when u hit start(to flash) nothing happens?
You could try this.
1. Install another version of Odin, or even the Odin one click with gb
2. Remove battery and cable connecting phone and PC.
3. connect USB to PC and then go into download mode and try flashing the new package.
Let me know if its still not working, i kinda had this problem, but i tried with different Odin packages, try to flash the one with the gb bootloader.
Yeah that's what happens. Its recognized and everything then just hangs at setup connection part really don't know what's up but it's kind of weird.
I really like have tried to change it like odin packages and everything but it just won't be read past set up connection. I just wonder if I messed up my partitions to the point of no return.
Sent from my SGH-I897 using xda app-developers app

[Q] CM10 Stuck at bootloop, can't enter recovery, and computer doesn't detect

So I've seen a lot of threads on here with this kind of problem but none of the solutions work for me.
I just flashed CyanogenMod 10 nightly, was tinkering around on it, rebooted and I was just stuck in a bootloop. I can't get into recovery but I can get into download mode. However, my computer just doesn't detect the phone at all. I can't get Odin to detect it to flash a new bootloader or anything. I've tried installing Nexus drivers and everything. It just doesn't even detect that anything has been plugged into the computer. But the usb powers on the phone. If I plug into power I just get a spinny loading wheel that doesn't move and refreshed every few seconds.
I'm stuck. I can't get into recovery to flash, and I can't get my computer to detect it to flash. Help me please?
EDIT:
Okay so tried 3 different USB cables and I've found one that works. I tried flashing a new bootloader but I used the bootloader bit on Odin instead of pda (total noob mistake) now my screen is just black and won't turn on. I can get into download mode to flash stuff again. But what do I need to put in the bootloader section to get it back to normal?
I think you have to start from Gingerbread again
Search on samifirmware a 3 files firmware of Android 2.3.6
After that search on google a Step by Step guide how to flash a Rom with Odin.
I think after that i should work.
ChrissehB said:
So I've seen a lot of threads on here with this kind of problem but none of the solutions work for me.
I just flashed CyanogenMod 10 nightly, was tinkering around on it, rebooted and I was just stuck in a bootloop. I can't get into recovery but I can get into download mode. However, my computer just doesn't detect the phone at all. I can't get Odin to detect it to flash a new bootloader or anything. I've tried installing Nexus drivers and everything. It just doesn't even detect that anything has been plugged into the computer. But the usb powers on the phone. If I plug into power I just get a spinny loading wheel that doesn't move and refreshed every few seconds.
I'm stuck. I can't get into recovery to flash, and I can't get my computer to detect it to flash. Help me please?
EDIT:
Okay so tried 3 different USB cables and I've found one that works. I tried flashing a new bootloader but I used the bootloader bit on Odin instead of pda (total noob mistake) now my screen is just black and won't turn on. I can get into download mode to flash stuff again. But what do I need to put in the bootloader section to get it back to normal?
Click to expand...
Click to collapse
Nothing. Never put anything in the bootloader section. Instead, look for a rom that has bootloader in it. I believe that the darky resurrection rom has bootloader.
Sent from my Nexus 7 using Tapatalk 2
I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
I've managed to fix it in the following way:
1. I've downloaded the Semaphore kernel for JB (Semaphore ver. 2.6.0), and unpacked it.
2. I've used heimdall: `heimdall flash --kernel zImage`
3. After that the phone boots and CM finishes the upgrade as usual. (I've did not lost anything from my data.)
(Environment data: OS: Ubuntu 12.04, Heimdall 1.3.2)
Boot loops with cm-10-20121125-NIGHTLY-galaxysmtd & cm-10-20121126-NIGHTLY-galaxysmtd
frantique said:
I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
Click to expand...
Click to collapse
Thank you very much for the information!
I was thinking I did something wrong... :crying:
Update:
The newer versions cm-10-20121129-NIGHTLY-galaxysmtd & cm-10-20121130-NIGHTLY-galaxysmtd are OK again.
With kind regards
Joe
frantique said:
I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
I've managed to fix it in the following way:
1. I've downloaded the Semaphore kernel for JB (Semaphore ver. 2.6.0), and unpacked it.
2. I've used heimdall: `heimdall flash --kernel zImage`
3. After that the phone boots and CM finishes the upgrade as usual. (I've did not lost anything from my data.)
(Environment data: OS: Ubuntu 12.04, Heimdall 1.3.2)
Click to expand...
Click to collapse
I want to buy you a beer Thanks a ton
I did this on windows 7 x64 without any problems (I had to install driver from heimdall suite)
Same here, but computer WON'T detect, normally does
Hi
I'm desperate, no phone, stuck on galaxy S boot screen, will boot into download mode but not recognised by computer
Any ideas?
Thanks

Boot-Loop, Can't Access DL/Recov Mode

Well, I was running J.B. by Slim Beam Version 8 (latest version as of August 2013) + Semaphore Kernel V 3.0.0s for it.
I was planing on giving this phone away to a family member so I went into recovery mode using ROM Manager and clicked "wipe cache" and "wipe delete/factory reset".
After this was done, I went on to reboot my phone and is now stuck on boot-loop. Well, stuck on the "Galaxy S" screen. There's nothing I can do. The phone was fully charged when I started all this.
Plugging it to my PC won't do anything, just charge, as the phone isn't being recognized by my PC.
Holding the volume up, down, home button and any possible combination of the three while starting-up the phone does absolutely NOTHING.
I have no idea what to do, I really need help.
Thanks!:good:
UPDATE: Managed to get into DL Mode, still no way of getting my PC to recognize it. Using different USB cables and computers. The computer "installs drivers" but it doesn't recognize the device. Opened ODIN and it recognizes the device but when I try to flash, it is stuck at <ID:0/003> SetupConnection.
Any ideas?
possible solution: When using Odin to Flash, Open task manager and close these: Kies.exe, KiesTrayAgent.exe and KiesPDLR.exe found here http://50.23.216.69/showpost.php?p=30415128
pryerlee said:
a possible solution : When using Odin to Flash, Open task manager and close these: Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe found here http://50.23.216.69/showpost.php?p=30415128
Click to expand...
Click to collapse
Fixed it. Rebooted phone, downloaded newer Samsung drivers and ODIN worked perfectly. Used the Resurrection ROM by Darky and now flashed Slim bean v8 and Semaphore 3.0.0.
All working great now!
glad to hear you managed to fix it
Have a new problem now, it seems.
No matter what I do, I can't seem to get the Network working, I have no IMEI. I read I had to go back to STOCK and so I did and got my Network back with Android version 2.2.1. Now with 4.2.2, still no network... what should I do?

Categories

Resources