Related
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.
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
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.
Dear guys and girls,
I have a problem. Since 2 days my tf300t is for some reason not starting up anymore. The start screen does not go away. Before it worked like a charm. I have tried almost everything, I can think of. As far as I know the latest firmware is installed. The problem is also that the tablet isn't in developer mode. So my options are limited afaik to fastboot. I have installed the naked drivers version 0.73. But windows is saying that the device is not started. Only fastboot is started as device. I have tried to reinstall the firmware by usb, but to no avail. It sends but doesn't write... I have drained the battery to zero level. Can anyone help me with this? What am I missing?
<>< A Dieu
Jaco Oversluizen
I'm also having this same issue. Tablet was working fine and then froze up. After rebooting we are now stuck on the Asus screen with the circular logo going. Waited over an hour with no change. Tried to boot into recovery and recovery crashes and gives me Error! This is a stock tablet that hasn't been unlocked or anything.
Update: Did a Data Wipe and the device rebooted and came up. Doing all the updates again. Hopefully it wont mess up again.
So you have an unlocked bootloader ?
(backstory) Hi, ive had an Asus TF300T, for about 3 years now, unlocked, rooted it pretty early on... cycled between cyanogenmod and omnirom quite a bit, without really any major issues. Until today, i was running Cyanogenmods latest nightly build (CM11 Nov 5 2014), it worked just as any other nightly does a few bugs here and there, but nothing major and i hadn't done any major flashing or modding to the device. On my home from university, I turned my tablet off. And when i got home i plugged in the charger, and just as always the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.5
I had TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Edit: I dont know why, but when i try using fastboot or adb, the device isnt recognized. It doesnt show up on device manager either. I dont know if its the cable cause i bought it new, it says its can sync data, or a faulty charge/sync port....
razr9622 said:
(backstory) the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.1 (I know that theres a newer version 10.6.1.27.5, but when i try to flash it, the recovery says error and fails)
I have TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Click to expand...
Click to collapse
^THIS!
I was just to open a similar thread, then i saw your post. I join your request for help!
A month ago i have done a favor to a friend by unlocking his tf300t and installing CM11 on it. A few days ago he comes to me with this problem. I've tried anything but still no success:
- restore a backup done before flashing CM11 --> restore ends correctly but the problem remains
- flash a rom (CM11 and OmniRom) --> flash ends correctly but the problem remains
- flash the stock firmware found on asus website (WW_epad-user-10.6.1.27.5.zip, the SKU is correct for my version) --> the flash process stuck (i had to force restart the tablet after almost 2 hours of "flashing")
Since the boot animation changes according to the rom, i suppose the flashing process works. But the problem remains: after a few seconds the animation freeze and the device restarts, in loop.
Informations on the system:
- build 10.6.1.27.5
- TWRP v2.7.0.1 (working!)
- adb works (i managed to set /data as rw and push the .zip file to flash)
- fastboot should work
Please help! I feel a bit responsible for bricking my friend's device
SOLVED!
Finally!
I had already tried this method, before requesting for help, but the first time didn't worked... I don't know why this evening the tablet decided to collaborate:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked for me! :victory: