Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Ever since CM9 went into its first Beta, I wiped and installed it in place of the CM9 Alpha builds I used previously on my Droid 3 XT862, a CDMA phone for which CM9 requires no patches to run as I understand it. Ever since the nightlies started rolling out, every attempt I've made to install them has left me with one of two situations. If I install a CM9 nightly and the latest corresponding GApps pack, without wiping it gets stuck at the "Upgrading Android" screen saying "Starting Applications" forever. If I wipe and install a CM9 nightly and the latest corresponding GApps pack, the phone never passes the Motorola "Dual Core Technology" screen. I end up flashing back to complete stock (requires activation and rooting) Motorola 2.3.4 GB rom every time it does this. I don't know how to get to CWM recovery if I can't boot into Android itself. Moto's menu Recovery mode option doesn't point to the 2nd init that CWM Recovery uses if I understand it correctly. I know an earlier version of the bootstrap used PB Tools to point to CWM Recovery. I think this is due in part to the fact that the D3 bootloader is still locked... I wish they would just unlock the dam thing...
I just want to know is there a way to get to recovery without booting into android if the key combo used during boot up doesn't work, (Power + X or M key for me)? In my case I can only get to Recovery by having CM9 reboot or using the BootStrap installer to do it. More often than not using rom manager or other recovery switch apps lead to the Android Exclamation screen.
I'm getting tired of the phone activation wait music every time I have to do this...
Also no one seems to mention this problem in Hashcode's CM9 DEV topic and I can't post there yet.
Jsonic said:
Ever since CM9 went into its first Beta, I wiped and installed it in place of the CM9 Alpha builds I used previously on my Droid 3 XT862, a CDMA phone for which CM9 requires no patches to run as I understand it. Ever since the nightlies started rolling out, every attempt I've made to install them has left me with one of two situations. If I install a CM9 nightly and the latest corresponding GApps pack, without wiping it gets stuck at the "Upgrading Android" screen saying "Starting Applications" forever. If I wipe and install a CM9 nightly and the latest corresponding GApps pack, the phone never passes the Motorola "Dual Core Technology" screen. I end up flashing back to complete stock (requires activation and rooting) Motorola 2.3.4 GB rom every time it does this. I don't know how to get to CWM recovery if I can't boot into Android itself. Moto's menu Recovery mode option doesn't point to the 2nd init that CWM Recovery uses if I understand it correctly. I know an earlier version of the bootstrap used PB Tools to point to CWM Recovery. I think this is due in part to the fact that the D3 bootloader is still locked... I wish they would just unlock the dam thing...
I just want to know is there a way to get to recovery without booting into android if the key combo used during boot up doesn't work, (Power + X or M key for me)? In my case I can only get to Recovery by having CM9 reboot or using the BootStrap installer to do it. More often than not using rom manager or other recovery switch apps lead to the Android Exclamation screen.
I'm getting tired of the phone activation wait music every time I have to do this...
Also no one seems to mention this problem in Hashcode's CM9 DEV topic and I can't post there yet.
Click to expand...
Click to collapse
I can't answer your question, but I know that CM9 is no longer working with recovery bootstrap... You have to use Safestrap. I had CM9 stuck at the dual core logo 3 times before I decided to google it and find this out. Hope that helps you.
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
I flashed the Cyanogen mod 10.1 nightlies for 2013-01-05. The boot animation was running for an abornomally long time so I pulled the battery and booted up and now the boot animation will not stop running. I tried searching for help but with no avail I have not found it too fix this problem. Also I made a CWM backup.
jubjubcat said:
I flashed the Cyanogen mod 10.1 nightlies for 2013-01-05. The boot animation was running for an abornomally long time so I pulled the battery and booted up and now the boot animation will not stop running. I tried searching for help but with no avail I have not found it too fix this problem. Also I made a CWM backup.
Click to expand...
Click to collapse
Also after trying too restore it, I just get the error Couldn't find directory no files found.
jubjubcat said:
Also after trying too restore it, I just get the error Couldn't find directory no files found.
Click to expand...
Click to collapse
Nevermind fixed it.
How did you fix it? rh
How did u fix it? I am facing a similar problem.
and when i tried to upgrade from cm10 to cm10.1 i was stuck at "Android is upgrading - Starting apps" screen. and a fresh installation of cm10.1 was stuck at the boot animation.
I am using Siyah Kernel 1.8.7 and having cyanogenmod as my secondary rom.
Plz help somebody
utsav7r said:
How did u fix it? I am facing a similar problem.
and when i tried to upgrade from cm10 to cm10.1 i was stuck at "Android is upgrading - Starting apps" screen. and a fresh installation of cm10.1 was stuck at the boot animation.
I am using Siyah Kernel 1.8.7 and having cyanogenmod as my secondary rom.
Plz help somebody
Click to expand...
Click to collapse
SiyahKernel s3-v1.8.8
Posted on January 13, 2013
Changelog
rebased on i9300 update7 sources (sudden-death issue is supposedly fixed in this source drop)
reverted temporary fix for exynos-mem exploit as i9300-update7 sources already fix that
cm10.1 is now supported in dual-boot configurations
1.8.7->1.8.8: fixed cm10.1 not booting when installed as 2ndROM (a tiny typo in ramfs)
BUT,it doesn't work anyway (just trying now at it's stuck on the boot screen)
Just try it and report back! :good:
You do realize that the siyah kernel is for the international S3 which has different hardware then our s3? If you are using a kernel for a different phone then of course it wont boot....
R: [Q] Flashed cyanogen mod 10.1, stuck at boot animation
By "International", you mean the exynox version unlocked right?
Sent from my GT-I9300 using xda app-developers app
R: [Q] Flashed cyanogen mod 10.1, stuck at boot animation
Whatever, it's been released v1.8.9 and it's said to fix the CM10.1 issues
Sent from my GT-I9300 using xda app-developers app
Flash problems
I've had installs stick at the boot animation or shortly thereafter several times. Usually it's because of a dumb mistake. The only thing that's consistently worked for me is flashing back to stock VZ firmware via Odin and doing the whole process over from root through installation. It sucks but it always works.
Howdy.
I've just flashed CyanogenMod 10.1 - 20130315 to my droid 4 with Safestrap, and I haven't been able to boot into it; the cyanogenmod splash screen with the rotating wheel graphic shows up, but it spins for upwards of 40 minutes without doing anything.
I followed the guide on the cyanogenmod wiki for the droid 4 device. The forum won't let me post a link to it.
Before I installed I wiped / factory reset, and after install I wiped cache/dalvik; still no dice. I've tried doing the same process several times (even wiking the system before trying to reflash), but the same result has always occurred: ever unhelpful eternal wheel...
I'm a bit at my wits end; I haven't been able to find any other information about this that wasn't solved by wiping cache / dalvik, so I turn to y'all for help.
Same here
I installed Cyanogenmod 10.1 with CWM the link:[Recovery/Bootstrap][5-sep-2012] CWM Touch recovery v6.0.1.1 - xda-developers and i went ahead and installed the mod: cm-10.1-20130211 all went fine untill i noticed that my camera is not working (not a big deal) but then i noticed that my phone only saw 488MB out of my 32GB this was un acceptable after i found how to connect my phone to my pc so it showed up as a storage device do that i copied the same mob but a different version (cm-10.1-20130129_v2) so i went ahead and booted into Android system recovery <3e> and i did a factory reset and then i said oh f*** i need CWMR to install the thing so i just waited for it to do its thing and then reboted the device thinking after i boot up i will reinstall CWMR but i was never able to boot because im stuck on the boot animation. Been waiting for +20min or so and nothing please help me what can i do this is my only phone please help
help with CM10.1 ROM issue
Hi folks,
this is my first post on XDA. I have a Sprint htc EVO 4G LTE phone which was running on JB.
Thought of root and flash with CM. So, first I unlocked the bootloader using htc dev and installed TWRP custom recovery and then rooted.
Then I flashed the stable CM 10 then flashed gapps which is compatible for CM 10 version. so far so good. oh, btw I did nandroid backup before flash and also wiped to factory reset, cache and Delvic cache.
After the flash i clicked on reboot system and I see the Cyanogenmod boot, but its stuck at that stage and I waited for more than an hour. No luck.
Thank god I did back up before this, otherwise not sure what I'm gonna do.
But, could someone tell me why it gets stuck at this point. I know some of you guys had this problem. I searched everywhere but didn't get help. I thought of posting this in android development forum, but as a newbie I can't do that.
Please help me out.
P.S: when I'm on boot screen (power button + vol down button) I see unlocked at the top but I also have TAMPERED in red color on top of that. Was this normal? or do you think that is causing the problem? and what should I do now?
(First of all I am not an expert)
It happens sometimes about 1/10 of every flashes I did with cm10
It might because some files didn't get copied or got corrupted.
Just try this method
Format data
Format system
Format cache
Wipe dalvick cache and factory reset
Now flash the ROM
Hit thanks if I helped
Sent from my WT19i using xda app-developers app
---------- Post added at 11:35 PM ---------- Previous post was at 11:27 PM ----------
(First of all I am not an expert)
First wipe every thing(system,data,cache,dalvick,android secure....)
Now install ROM,
Wait don't install gapps
Now find an extended cm10.1 kernel or lupus kernel(or such kernels) for your device and flash it via pc
I prefer flashing kernel after installing the rom
Hit thanks if I helped
Sent from my WT19i using xda app-developers app
NEED HELP Cm9
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
neso97 said:
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
Ask in the Xperia X10 mini forums.
Three-finger salute
Ran into this situation today when I tried to restore a backup and I couldn't get past the CM10 logo on bootup. Holding down all three buttons, power, volume up and down, got me back to the Clockworkmod boot screen.
ETA: Sorry, posted in wrong forum. My situation pertained to a Samsung Galaxy 5 Media Player.
neso97 said:
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
Hi...i just happened to flash my x10 mini to cm9-robyn yesterday...same thing happpened to me...boot the animation until run of battery....i accidently booted it to recovery and just leave it...fortunately after sometime it booted by itself and run as normal. The cm9 run ok except the wifi is not working. Hope that will help. I am not an expert.
Ok, so I gave my wife my old TF101 when I got the 701. I reflashed it with a fresh install of timduru's KatKiss ROM. It's been running reasonably well aside from random reboots. all of a sudden, yesterday it stopped booting up at all. It shows the normal Asus flash screen, but then when it shows the OS specific one (in this case, the weird little picture of timduru's meerkat thing...) it's just flashing random little bits of tha tpitcure all over different parts of the screen an some sort of random flickering and never going past it. I can still boot to the recovery normally, so I wiped it and tried reflashing the same ROM and ended up with the same thing. Tonight I plan to try to download the newer version of the ROM and try, but I fear I may be SOL. Any other suggestions?
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
*Detection* said:
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
Click to expand...
Click to collapse
Yes, I did that. Still no good. I'm pretty much screwed, aren't I?
If your TF serial number starts B6O or lower, some B7Os too, then it is SBK1, which means you can use NVFLASHable ROMs - they delete and remake every partition on the TF and reinstall stock ROM - you could try that in case the sdcard is corrupt
stuck at TWRP screen, failed to flash bootloader
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of yesterday, it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TWRP logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle. I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a day now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.