phone stuck on cyanogen boot logo - myTouch 4G Q&A, Help & Troubleshooting

So this is what happened.
> Was successfully running RC3, have done wipes and re-installs multiple times with no hitches.
> Upgraded to new Clockwork mod recovery
> Did "fastboot erase system -w"
> Booted into recovery and installed RC4
> Rebooted phone, stuck at boot logo
> Re-did steps and re-installed, same problem.
Any ideas what could be wrong guys?
Update:
So I have tried flashing 3.0.0.6 via fastboot and installing the stable for glacier with no luck, it keeps rebooting at the cm boot logo. Then I installed RC3 and it got stuck on the T-Mobile logo. COULD SOMEBODY PLEASE HELP!!

This is happening on CWM 3.0.2.4?

Yup, just updated to the newest one before I flashed RC4, im downloading the stable for glacier now. Hopefully the problem lays in the copy of RC4 i downloaded.

So I have tried flashing 3.0.0.6 via fastboot and installing the stable for glacier with no luck, it keeps rebooting at the cm boot logo. Then I installed RC3 and it got stuck on the T-Mobile logo. COULD SOMEBODY PLEASE HELP!!

If you flashed the recovery via fastboot, I'm sure it's good. To my mind, the only variable left here is a bad SD card. Beyond that, I have no other ideas.

Is there a way I could flash the ROM directly from my computer erasing the element of the SD card?

Good question, but I myself can't answer that definitively. Looking at the list of fastboot commands, it seems possible. If it can be done, I might do that from now on rather than using recovery.

What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?

As far as im concerned you should do a factory reset after the fastboot erase system. That worked for me
If gou want flash the ROM via fasfboot it is a bit more complicated as the. Zip not only contains the ROM but also the boot imagw and some other components.
You can try extracting the .zip and tell me what files you get so maybe we can figure some commanss out. I would recommwnd the factory reset first though
Sent from my HTC Glacier using XDA Premium App

xchaos said:
What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?
Click to expand...
Click to collapse
Formatting the SD CARD will most likely have no effect
Sent from my HTC Glacier using XDA Premium App

xchaos said:
What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?
Click to expand...
Click to collapse
I would do exactly that. If after formatting the SD the ROM still fails to boot, I think then you can say for sure the SD is the problem.

everest.deth said:
As far as im concerned you should do a factory reset after the fastboot erase system. That worked for me
If gou want flash the ROM via fasfboot it is a bit more complicated as the. Zip not only contains the ROM but also the boot imagw and some other components.
You can try extracting the .zip and tell me what files you get so maybe we can figure some commanss out. I would recommwnd the factory reset first though
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
How do you do a factory reset? Is it an option within the clockwork recovery? And yeah TeeJay trying it right now, will update.

xchaos said:
How do you do a factory reset? Is it an option within the clockwork recovery? And yeah TeeJay trying it right now, will update.
Click to expand...
Click to collapse
Yep, it says wipe data/factory reset
Sent from my HTC Glacier using XDA Premium App

Will I have to do any additional steps if I preform a factory reset?

xchaos said:
Will I have to do any additional steps if I preform a factory reset?
Click to expand...
Click to collapse
At that point the phone is wiped clean (except for recovery of course). In fact if you haven't already, wipe all 3 items in recovery before flashing anything.

WOOT! I don't know what did the trick, formatting the SD card or factory resetting but its WORKINGGG I'll thank you both for your help. Thanks guys.

xchaos said:
WOOT! I don't know what did the trick, formatting the SD card or factory resetting but its WORKINGGG I'll thank you both for your help. Thanks guys.
Click to expand...
Click to collapse
Glad you got it working bro
Sent from my HTC Glacier using XDA Premium App

Im having this same issue. Im gonna format my MemCard and see if thats the fix for me as well. Will report back in a minute.

Looping Issue
I have the looping issue too. I formated the mem card and I went into HBoot to factory reset. Whats different here is when i do the factory reset, it loads me into CWM Recovery and that does nothing. I hit any option and all i get i get is a black screen with the hat. Is it my Recovery version? (v3.0.2.4)

Tylormde said:
I have the looping issue too. I formated the mem card and I went into HBoot to factory reset. Whats different here is when i do the factory reset, it loads me into CWM Recovery and that does nothing. I hit any option and all i get i get is a black screen with the hat. Is it my Recovery version? (v3.0.2.4)
Click to expand...
Click to collapse
lolz im lost, Why would you go into HBOOT to do the factory reset? You need to do that via recovery. A black screen with the hat? :S Ok, try to reboot to recovery, do a factory reset from there (to scroll around you use the vol down and vol up, to selct you use the power key), then hit install zip from SD card, install the ROM you wish to use and reboot. that should do the trick

Related

Phone hangs on Dual core logo, need help

I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?
did you make a backup before installing the beta?
It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?
I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta
I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App
Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...
im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

[Q] Stuck on Google Logo

Please help me ='( so I went to recovery mode and did format/system format/data format/cache format/sdcard and when I try to reboot it is just stuck there on the google logo ='( please help me I know I messed very very bad I need help ASAP please.. How do I fix this?
http://forum.xda-developers.com/showthread.php?t=2010312
That will get you back to stock. You also might learn something.
If someone comes in here and tells you to use a toolkit, don't listen to them.
Alternatively, you can use use adb to push a ROM to your SD and then boot into recovery and flash it.
adb push romname.zip /sdcard/
Can you just tell me where are all these people seeing posts that are telling them to format their whole system and sd card?
Format system wipes your Rom so you have nothing to boot into to.
Rizy7 said:
Can you just tell me where are all these people seeing posts that are telling them to format their whole system and sd card?
Click to expand...
Click to collapse
If they're having issues and trying to return to stock then that is an option.
I format system when upgrading a Rom, that is flashing a new version of the same Rom.
Sent from my Nexus 4 using xda premium
fone_fanatic said:
Format system wipes your Rom so you have nothing to boot into to.
If they're having issues and trying to return to stock then that is an option.
I format system when upgrading a Rom, that is flashing a new version of the same Rom.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I meant the sd card bit which surely gets rid of all the files?
Rizy7 said:
I meant the sd card bit which surely gets rid of all the files?
Click to expand...
Click to collapse
You only can do that prior to flashing a factory image in fastboot, allthough flashing a factory image allready wipes the sdcard.
I formatted everything because I am a noob and I wanted to wipe everything off my phone, and the factory reset option just wiped some off not everything, so not knowing what I was getting myself into I just went to recovery mode and formatted everything then BOOM!! stuck on google logo, good thing is everything is fixed I just restored my stock image thing. This thread can be closed thanks guys

[Q]Wont boot after failed 4.4 OTA Update (Bootloader Unlocked, CWR)

Hi guys,
I unlocked my Bootloader, installed Clockwork Recovery a while back. Still had Vanilla Android on it.
Today I updated it, there was an error shown in the Clockwork recovery during the update, I rebooted the device.
Now I am stuck in the 4.4 Bootscreen.
How can I get a Recovery Image on my Phone now? (Booting in Recovery works without any issues)
When I reset my device is all the data in the sdcard folder gone? If so is there a way to back some of it up now?
Thanks
acidr4in said:
Hi guys,
I unlocked my Bootloader, installed Clockwork Recovery a while back. Still had Vanilla Android on it.
Today I updated it, there was an error shown in the Clockwork recovery during the update, I rebooted the device.
Now I am stuck in the 4.4 Bootscreen.
How can I get a Recovery Image on my Phone now? (Booting in Recovery works without any issues)
When I reset my device is all the data in the sdcard folder gone? If so is there a way to back some of it up now?
Thanks
Click to expand...
Click to collapse
Its best to do a clean flash and delete all your data. Phone vs Pics? I'd take the phone. Besides, some stuff is backed up by Google servers. Follow this:
http://forum.xda-developers.com/showthread.php?t=2010312
You can't update OTA while having cwm. OTA can only be completed using stock recovery or twrp recovery. Cwm haven't had this ability yet. Just follow the guide given in a post above and flash kitkat factory images. All your problems will be solved. Or, you can use this guide ( http://forum.xda-developers.com/showthread.php?t=2527142 ) and delete the -w to save your data.
For your second question, if you factory reset using stock recovery, then yes, it will wipe clean your sd card. If you reset using cwm/twrp, then no, it won't wipe your sd card and your pics, music will all still be intact.
arffrhn said:
You can't update OTA while having cwm. OTA can only be completed using stock recovery or twrp recovery. Cwm haven't had this ability yet. Just follow the guide given in a post above and flash kitkat factory images. All your problems will be solved. Or, you can use this guide ( http://forum.xda-developers.com/showthread.php?t=2527142 ) and delete the -w to save your data.
For your second question, if you factory reset using stock recovery, then yes, it will wipe clean your sd card. If you reset using cwm/twrp, then no, it won't wipe your sd card and your pics, music will all still be intact.
Click to expand...
Click to collapse
thanks both of you i kept using this method, -w didnt seem to work properly so I wiped it comleetly now it boots up propperly
thanks again
acidr4in said:
thanks both of you i kept using this method, -w didnt seem to work properly so I wiped it comleetly now it boots up propperly
thanks again
Click to expand...
Click to collapse
How did you wipe your phone completely? I actually have the same problem you had.
aznpro said:
How did you wipe your phone completely? I actually have the same problem you had.
Click to expand...
Click to collapse
nvm, i figured it out.

bricked?

Hi,
I tried out ubuntu touch and wanted to revert to stock before flashing cm (because I havn't had a rom on my storage).
After flashing the stock image via fastboot (using that flash-all.sh included in official download) my nexus stucks at boot animation.
Then I flashed recovery (I tried both, CWM and TWRP) and tried to do a factory reset -> unable to mount internal storage, also the space of my internal storage was 0MB (obviously because it can't mount anything), so it exited with an error. Then I formatted just every partion in CWM and I was able to mount again, flashed stock image ... stuck at boot animation. Tried flashing cm via sideload... stuck at boot animation.
Google didn't helped me.
Does somebody know what to do now?
Thanks
Bagbag
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
jd1639 said:
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
Oh ye, i tried it, but if i try to enter it, there's just a droid with a red triangle.
bagbag said:
Oh ye, i tried it, but if i try to enter it, there's just a droid with a red triangle.
Click to expand...
Click to collapse
Hit vol up when you see that. It's normal
Sent from my Nexus 5
jd1639 said:
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
you should only have to clear the cache...factory reset shouldn't be necessary. Remember if you do have to do a factory reset, it will wipe all your storage completely if you use stock recovery to do it. Don't forget to back everything up first!
hp420 said:
you should only have to clear the cache...factory reset shouldn't be necessary. Remember if you do have to do a factory reset, it will wipe all your storage completely if you use stock recovery to do it. Don't forget to back everything up first!
Click to expand...
Click to collapse
The OP just flashed the factory image, flash-all, do he doesn't need to worry about data any more, too late for that
Sent from my Nexus 5
jd1639 said:
Hit vol up when you see that.
Click to expand...
Click to collapse
Does not work, it just stays at the screen with dat red triangle. Also vol up + power at same and other things I found in google don't work.
I already made backups, but anyway, they wouldn't help me in any way, if I don't have a working phone..
bagbag said:
Does not work, it just stays at the screen with dat red triangle. Also vol up + power at same and other things I found in google don't work.
I already made backups, but anyway, they wouldn't help me in any way, if I don't have a working phone..
Click to expand...
Click to collapse
Boot into fastboot mode. Then from your pc with your device hooked up via usb type fastboot boot recovery. See if that will get you into recovery
Sent from my Nexus 5
It says 'cannot load 'recovery'' and also, I tried flashing ubuntu touch again and it worked.
Edit:
I think it has something to do with my /data partition. It said unable to mount /data again. After fixing that (for some reason it works if I select "format /data and /data/media (/sdcard)" (CWM) I can also format /data. But there a difference between that an all other partitions: for every other partition its like that: mount -> format -> unmount, but for /data it just don't do the last step, it stays mounted.
No on an idea? Do I need to send it in?
Try downloading The Root Toolkit Here.
Connect your phone, open the toolkit. On The First Page select "Soft-Bricked/Bootloop" and Flash Stock+Unroot.
This should Help.
Yeeeeeeey, I have no idea what the tool did, but it works now
Thank you for the tip
Bagbag

Categories

Resources