Database Users

[Q] Bootloop CM9

Hey guys!
Today when i was updating to CM9 my phone started bootlooping, and the big problem is that i can't get into recovery mode by using the 3 button combo.. But I can get into downloading mode, but my computer doesn't find my phone.
I'm really out of ideas here, help is much appreciated.
Edit: I followed step by step in CM9 thread http://forum.xda-developers.com/showthread.php?t=1592131
/Korhonen

korhonen said:
But I can get into downloading mode, but my computer doesn't find my phone.
Click to expand...
Click to collapse
Had similar situation day before yesterday .after hours od checking one after the other traced it to one missing pin in the USB cable (either burned out or rolled in on the micro usb plug) ..can also happen on the phone usb slot end. ( as one other person had experienced on this forum)

xsenman said:
Had similar situation day before yesterday .after hours od checking one after the other traced it to one missing pin in the USB cable (either burned out or rolled in on the micro usb plug) ..can also happen on the phone usb slot end. ( as one other person had experienced on this forum)
Click to expand...
Click to collapse
Hmm, I can hear the phone connect to windows though, and I had it connected just before I flashed the CM9. As the bootloop appeared so did the cpu not recognizing part :/

korhonen said:
Hmm, I can hear the phone connect to windows though, and I had it connected just before I flashed the CM9. As the bootloop appeared so did the cpu not recognizing part :/
Click to expand...
Click to collapse
try reboot your PC and phone

xsenman said:
try reboot your PC and phone
Click to expand...
Click to collapse
I tried that, no difference

korhonen said:
I tried that, no difference
Click to expand...
Click to collapse
Have you uninstalled and reinstalled drivers/tried different ones?
Sent from my GT-I9000 using xda premium

slaphead20 said:
Have you uninstalled and reinstalled drivers/tried different ones?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ye, same. I've tried connecting other phones to the computer with the same cable and it works. So it's certain that the problem lies with the phone.

korhonen said:
Ye, same. I've tried connecting other phones to the computer with the same cable and it works. So it's certain that the problem lies with the phone.
Click to expand...
Click to collapse
Check the usb port and make sure pins are as they should be
Sent from my GT-I9000 using xda premium

Remove your micro sd, you should be able to get back in to recovery then. Once there, repeat flashing process including wipes. Should be okay then.

Just flash semaphore or any other ICS-Root Kernel with CWM for I9000 via ODIN and you should be fine (booting and getting CW back).
Instructions:
Download ODIN (if you don't have already)
Flash Kernel .tar package (don't check repartition!)
If you have never flashed with ODIN before I suggest you find a quick tutorial before you go to work.
Good luck!

Had your problem to, but not with cm9, i flashed it back to stock, then rooted and then updated it, seemed to work for me
Sent from my GT-I9000 using XDA

It's most certainly a driver issue. Uninstall the Samsung drivers and then reinstall them again.
If that fails, use this
http://www.4shared.com/office/ewdIWux2/usb-connection-issues-mtp-devi.html
to fix the MTP issue

superkoal said:
Just flash semaphore or any other ICS-Root Kernel with CWM for I9000 via ODIN and you should be fine (booting and getting CW back).
Instructions:
Download ODIN (if you don't have already)
Flash Kernel .tar package (don't check repartition!)
If you have never flashed with ODIN before I suggest you find a quick tutorial before you go to work.
Good luck!
Click to expand...
Click to collapse
You were right! Thanks alot! Thought I was doomed, but now it works.
A nooby mistake of me, it was the USB-drivers... Thanks for all answers and suggestions!
/Korhonen

One question...
Was it the driver issue or was it an issue with Odin?

TVwithParents said:
One question...
Was it the driver issue or was it an issue with Odin?
Click to expand...
Click to collapse
It was the drivers.

This seems like an appropriate place for a question.
I've been using the guide here:
theandroidsoul.com/cyanogenmod-9-cm9-nightly-rom-for-galaxy-s-installation-guide/
To try to install CM9. Using Odin I've flashed:
JW4_JW4_JW4.tar (worked)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar (worked)
Then I've stuck
cm-9-20120623-NIGHTLY-galaxysmtd.zip
gapps-ics-20120429-signed.zip
into the root directory, booted into recovery and tried to run the first zip.
Every time I do this it gets maybe 3 seconds into the install, and reboots. It then shows the "Galaxy S" logo, then "Galaxy S - Cyanogen" (some graphic with Cyanogen in the name) and flips to what looks like the installation text for two seconds - and then reboots and repeats.
I can't drop it back into recovery but I can force it into download mode and flash JW4 again and repeat from the top. This has happened a few times now and I always end up in the same place, which suggests I'm doing something wrong. Please fix my idiocy.

Having taken the time to read this
http://forum.xda-developers.com/showthread.php?p=24673062
....on your behalf I notice you have omitted certain steps, please read yourself to find the missing link
Sent from my GT-I9000 using xda premium

slaphead20 said:
Having taken the time to read this
http://forum.xda-developers.com/showthread.php?p=24673062
....on your behalf I notice you have omitted certain steps, please read yourself to find the missing link
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No, I read that for one of the three times I tried. I assume I missed something?
1. Root your device and install ClockworkMod Recovery. - Covered by flashing CF Root, yes?
2. Reboot into Recovery using 3-button-combo
3. Do a Nandroid backup!
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM from internal sdcard using ClockworkMod Recovery - Breaks here.
Click to expand...
Click to collapse
I did not do a nandroid backup though. Can that actually cause an issue?

OckyFlam said:
No, I read that for one of the three times I tried. I assume I missed something?
I did not do a nandroid backup though. Can that actually cause an issue?
Click to expand...
Click to collapse
Did you do the wipe/factory reset and wipe cache stage
Sent from my GT-I9000 using xda premium

slaphead20 said:
Did you do the wipe/factory reset and wipe cache stage
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yes, definitely. It was in that link in my post and in the link you provided so I assumed it was important

I need some help please!!

Hey guys,
Ive been flashing a few different ROMS today. I went back to ROOT box rom but to my horror I have problems.
1. I cant mount SD card.
2. Phone still thinks its charging even when its unplugged from the charger.
How ever I can still transfer files and what not when I use AirDroid app (Wifi file transfer).
Anyone have any ideas ??

harri077 said:
Hey guys,
Ive been flashing a few different ROMS today. I went back to ROOT box rom but to my horror I have problems.
1. I cant mount SD card.
2. Phone still thinks its charging even when its unplugged from the charger.
How ever I can still transfer files and what not when I use AirDroid app (Wifi file transfer).
Anyone have any ideas ??
Click to expand...
Click to collapse
try unmounting and mountin it again
also clean ur usb port

Try wiping your caches? Like dalvik cache perhaps? I usually wipe stuffs after i flash roms just to get that brand new feel
Sent from my GT-I9100 using xda premium

saywhatt said:
Try wiping your caches? Like dalvik cache perhaps? I usually wipe stuffs after i flash roms just to get that brand new feel
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
+1 .. Nothing like a brand new feel .... althought tbh, you should probably full wipe BEFORE flashing

you may change another kernel to try to solve

Wi-Fi not working

Have been enjoying epinter's ROM, but recently been having some issues.
Last week, everything suddenly started misbehaving, and then it rebooted and went into a boot loop. I restored to an older NANDROID backup and it worked fine. But since that event, it has been rebooting quite regularly at random times. Sometimes, it goes into a bootloop. Have realised that if I take out the battery and leave it to cool down for a few mins, it starts working fine. I suppose this is to do with overheating.
I deleted FastDormancy.apk as suggested by epinter. Doesn't seem to have made a difference.
Since day before, it isn't detecting any Wi-Fi networks. I flashed the 20120922 version of epinter's ROM too, but still have the same problem. Tried the WiFi settings, but that didn't help.
Today I cleared data and cache, and reinstalled 20120922 version of the ROM, but still got the problem.
I also upgraded radios to 37p. Didn't help.
Any suggestions on how to diagnose it? Is it possible that Wi-Fi (hardware) is bust?
Sent from my MB860 using xda app-developers app

No suggestions?

Maybe hardware!
Sent from my MB860 using xda premium

Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium

Cab121 said:
Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What do you mean by 'Load a different recovery via fastboot'? I have used fastboot to wipe fully, but could you point me to the 'recovery' to be used?
Thanks

My phone is repeatedly rebooting now. It's not in a boot loop. It actually boots into ICS and then reboots after some time.
Really would appreciate any insights on this.

You can use fast boot to flash recovery files to the phone. You need to while recovery then use "fastboot flash recovery filename.img" for example. Assuming your file is in the same directory on your PC.
I only suggest out of practice. I typically find if any part of the hardware fails to boot or load with the rest of the phone I start with a clean cwm ,rom, and so on. Start at 0 essentially. If the problem goes away then its most certainly soft wear and you can trouble shoot from thwre
Sent from my MB860 using xda premium

Does Bluetooth work ?
Sent from my MB860 using Tapatalk 2

I've been using the 20120825 version of epinter's rom, and everything has been incredibly stable for me except wifi and bluetooth. Neither will turn on, and under advanced wifi settings my wifi chip is giving the mac address as not available.
I flashed CM7 a few weeks ago to see if that would fix it and CM7 gives an error when I try and turn wifi on, also showing not available for the wifi mac address.
I've seen around here a little bit that this might be a hardware issue that happens irrespective of what rom you use or if still on stock.
Has anyone found a fix for it?
EDIT: also using the 37P radio.
I also found this thread... http://forum.xda-developers.com/showthread.php?p=26163360

[Q] Need some help with boot loop on ColdFusionX

Well, i've flashed my Blade with ColdFusionX ROM and everything seems to be great.
Then i decided to restart it and it stays on boot loop. It can be solved by entering on recovery and wiping the Dalvik Cache, but i want to know if there is another way to solve it? It's kinda annoying making it everytime i need to restart or shutdown.
Another question is for a good app to make USB Thetering, since the one on this ROM works but drains battery faster then USB provides.
Thanks and sorry about the bad english.
link to ROM's page: http://forum.xda-developers.com/showthread.php?t=1429539

Update:
Now things are worst then ever. I've updated ROM Manager to last version and then i can't enter on recover anymore and cellphone can't start.
Is there any way to flash the recovery from outside the phone?

Method 2.
http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
Sent from my GT-I9300 using xda premium

Do you have Blade drivers for Windows 8, that drivers are for 7 and they aren't working.

Tryed method 2 but it didn't work, adb can't see my device connected. Now i'm trying method 3.
How can I know what TPT should i use?
Sorry for being so noob.

If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium

UrbanDrawer said:
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It is with 4.0.4 gen2, but i don't know if i have to use chinese or european TPT.
It was manufactured in china, so I use the Chinese TPT, right? Seems obvious but i'm kinda scared.

Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)

Flash another rom.
Sent from my GT-I9300 using xda premium

vittal said:
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Click to expand...
Click to collapse
This will keep on happening because the rom u are using has stopped development. Soon u will also loose Google play.
Do what urbandriver said. I recommended konsta T' cm9 (Google it).
Sent from my Blade using xda app-developers app

Booting problem

I flashed Quarx's CM10 ROM and it runs completely fine at first, but then when I reboot my phone it gets stuck at the splash screen and won't load the operating system. The only way I've found to fix it is to reset to factory defaults, which isn't really an ideal solution as I don't want to have to reinstall everything every time I reboot my phone.
Does anyone have any idea what I can do?

Bump

Just clear dalvik cache in custom recovery. You can find it in "Advance" menu. Dalvik cache has to be clean before first boot. You can wipe all caches just in case. After this try to reboot a couple of times to see if this issue persists.

Vicsa said:
Just clear dalvik cache in custom recovery. You can find it in "Advance" menu. Dalvik cache has to be clean before first boot. You can wipe all caches just in case. After this try to reboot a couple of times to see if this issue persists.
Click to expand...
Click to collapse
I have cleared all caches and nothing has worked. I've left it to try and boot for at least an hour several times, but it just doesn't want to boot.
I'm only having this problem on CM10, by the way.. 7.2 still works.

Strange issue
Check after reboot in BootMenu (in 'boot' section) if it still boots in 2nd_boot and not in 2nd_init or normal. Normally if it boots in 2nd_boot at first, it should stay in 2nd_boot.

Vicsa said:
Strange issue
Check after reboot in BootMenu (in 'boot' section) if it still boots in 2nd_boot and not in 2nd_init or normal. Normally if it boots in 2nd_boot at first, it should stay in 2nd_boot.
Click to expand...
Click to collapse
2nd-boot is selected.

Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium

I had that problem too
thekguy said:
Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I had this problem few months ago...
I have tried everything (in my opinion) and only flashin with sbf file helped, then installing Quark's rom again...

Well, sbf is the surest way, but the method posted above I've used successfully to downgrade from cm10 to miui gb
Sent from my MB526 using xda premium

thekguy said:
Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
It boots into CM10 then I when I restart the phone it gets stuck on the splash screen again.

And what happens when only format to ext4+ cache wipe(no wipe data).
Also cm10 for me sometimes hangs or boot loops on first run, removing battery and powering up manually fixes the issue
Sent from my MB526 using xda premium

thekguy said:
And what happens when only format to ext4+ cache wipe(no wipe data).
Also cm10 for me sometimes hangs or boot loops on first run, removing battery and powering up manually fixes the issue
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Same thing happens, it just hangs.
It runs perfectly fine on the first run, but then when I reboot it it just hangs at the boot splash screen every time I restart it.

Motorola or cyanogenmod screen
Sent from my MB526 using xda premium

thekguy said:
Motorola or cyanogenmod screen
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
CyanogenMod screen.

Then you can't boot(after the first boot) even after formatting to ext4, data wipe+ cache wipe again?
Sent from my MB526 using xda premium

thekguy said:
Then you can't boot(after the first boot) even after formatting to ext4, data wipe+ cache wipe again?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yeah, that's right. It's really weird, though.. because CM7.2 works flawlessly.

Really very weird. Does the booting problem occur even if you make no changes to the filesystem and simply reboot after first flash?
You can also try a sbf flash, though it probably won't help much
Sent from my MB526 using xda premium

thekguy said:
Really very weird. Does the booting problem occur even if you make no changes to the filesystem and simply reboot after first flash?
You can also try a sbf flash, though it probably won't help much
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Okay, I tried that and I think I figured out the problem. My phone is carrier unlocked and I'm with a different provider, so I have to flash a soft sim unlock on my phone which is causing boot problems on CM10.. any ideas on what I should do?

If your phone is carrier unlocked, then you don't need to flash any unlock
Sent from my MB526 using xda premium

thekguy said:
If your phone is carrier unlocked, then you don't need to flash any unlock
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
My phone is locked to a carrier, "unlocked" was a typo.