I've just SBFed my phone after flashing a bad rom, and when rebooting, it gets to the AT&T boot animation, then cuts back to the red M, over and over again.
EDIT: Fixed
arby220 said:
I've just SBFed my phone after flashing a bad rom, and when rebooting, it gets to the AT&T boot animation, then cuts back to the red M, over and over again.
EDIT: Fixed
Click to expand...
Click to collapse
Great, I answered anyway:
http://forum.xda-developers.com/showpost.php?p=21978356&postcount=37
Somebody else could have the same problem in the future!
josuearisty said:
Great, I answered anyway:
http://forum.xda-developers.com/showpost.php?p=21978356&postcount=37
Somebody else could have the same problem in the future!
Click to expand...
Click to collapse
I have the same problem... here i posted this earlier. "OK SO, i root my Motorola Bravo and desided to get CM7. i was told NOT to wipe my data. so i didnt. and ziped it from boot screen. Then rebooted. Then it sat at the boot up screen and stayed there. I pulled my battery out. rebooted to recovery utility. WIPED everything. date/ cache. rebooted phone. NOW it is staying at the motorolla boot screen with the M in the middle. PLEASE HELP. I do have a backup from clockwork mod."
wowplayer12 said:
I have the same problem... here i posted this earlier. "OK SO, i root my Motorola Bravo and desided to get CM7. i was told NOT to wipe my data. so i didnt. and ziped it from boot screen. Then rebooted. Then it sat at the boot up screen and stayed there. I pulled my battery out. rebooted to recovery utility. WIPED everything. date/ cache. rebooted phone. NOW it is staying at the motorolla boot screen with the M in the middle. PLEASE HELP. I do have a backup from clockwork mod."
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22775486&postcount=86
Related
I have a mytouch 3g original. I just rooted it with CM, the latest update. I tried flashing with Sirmez-p_s_blue-V4.0 (hxxp://forum.xda-developers.com/showthread.php?t=569160 )(replace xx with tt) i moved zip file to sd card. unmounted phone. Turned off phone. Held Home and Power bringing me to the Android System Recovery menu..... Moved to apply any zip from sd...Clicked the zip file pressed home to confirm. Went through the installation.. pressed reboot system now...... Then it sticks on the Mytouch 3g green screen.
This was my whole process without missing a step. I found i can still get into my recovery menu. i wiped/factory reset. then went to reboot not success still green screen of death.
Tried to reboot last backup again no success.
Now i have a phone stuck on The mytouch 3g green screen of death
Can Anyone Help me Please???
If you really try to think about it... ooh boy my common senses are tingling!
jr8801 said:
i wiped/factory reset. then went to reboot not success still green screen of death.
Tried to reboot last backup again no success.
Click to expand...
Click to collapse
you just wiped your phone. Install the rom again........
It looks like an outdated thread, I don't see your file anywhere but I'm assuming that you applied a 4.2.12.2 theme on your 4.2.15.1 rom. *Please tell me you didn't do that and wonder why your phone didn't work* I hope that theme file was for 4.2.15.1!
Alright thank you for the quick reply. further looking i did apply an older theme. does that mean my phone is bricked?
Alright i just reinstalled the Sappimg.nbh from the wiki CM page and this worked. sorry for being dumb i just freaked out when my phone wasnt booting. all is good now thank you Kawata
My wireless tether app for root users wasn't working (kept force closing) so I decided to just reflash the ROM I was then using (RegawMod). So, I downloaded it from xda, put it on my SD, flashed it, and everything was going well. I booted the phone up for the first time after I flashed it and I wouldn't boot, only cycle through the boot screen (the boot screen would appear, stay for a good ten minutes, then go black, and the boot screen would appear again..). So, I nandroided back to my stock 1.5, and that booted up just fine. I decided to try another ROM (DamageControl). I downloaded it, put it on my SD, flashed it, and again everything went well, but same problem, it will not get past the boot screen, just keeps cycling the boot screen over and over again..
So..what's wrong here? Can anyone help?
In the recovery go into wipe and click on every option in that menu.
Re: So I Think I Have A Problem...
did you wipe SD ext.
centran said:
In the recovery go into wipe and click on every option in that menu.
Click to expand...
Click to collapse
Did it. Lets see what happens..
EDIT: Good work, it booted up now!! Thanks guys, gotta love these forums!
im having some serious issues, that render my phone essentially unusable. at this point, i just want a working phone. right now, i can get into bootloader/hboot/fastboot but when i select recovery, it reboots to the white htc evo screen, then sits there looping. the only way for me to get into recovery is if i flash a recovery via adb with fastboot, and then i can get in, and ive tried flashing a rom, which says is successful, then i tell it to reboot, it made it into the rom. but then i needed to reboot, and then it just kept looping the bootanimation. battery pull and try again, still loops animation. then i try to get into recovery via bootloader, and im back to square one, looping htc evo white screen.
any ideas??? thanks
-Alex
What recovery were you using?
What recovery are you using?
Damn beat me to it lol
amon-ra
thanks for quick replies
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
aadcrasher said:
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
Click to expand...
Click to collapse
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
roids87 said:
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
Click to expand...
Click to collapse
Same thing I was thinking, get outta my head lol
lol, so goto recovery, then just go down the list of things to wipe and reflash rom?
Yup wipe it all 3-5x just don't wipe sdcard or batt stats wipe: factory reset/data 5x then everything else at least 3x I always wipe everything 5x if I'm changing roms or restoring a backup
got into recovery wiped, flashed rom, and its all looking good. confused as to why it started working out of nowhere, but it seems to be good, and im fine with that lol. thanks!!
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
The mechanics of some of this stuff is still beyond me, but I'm learning.
However something weird just happened and I have no explanation for it. I was running Blu Kuban ROM with TWRP. I wanted to install SlimBean and try it out, so I told GooManager to reboot my phone into TWRP so I can do a backup of my Blu Kuban config. Now I'm stuck in bootloader loop!
Seriously... it keeps trying to boot TWRP but I'm just stuck at the TeamWin logo screen. I pulled the battery after 5 minutes, turned it back on and bam.. right back to TWRP!
I swear I did nothing to my phone. It was working perfectly before I told it to restart.
Can I ODIN flash my way out of this?!
HeyItsRyan said:
The mechanics of some of this stuff is still beyond me, but I'm learning.
However something weird just happened and I have no explanation for it. I was running Blu Kuban ROM with TWRP. I wanted to install SlimBean and try it out, so I told GooManager to reboot my phone into TWRP so I can do a backup of my Blu Kuban config. Now I'm stuck in bootloader loop!
Seriously... it keeps trying to boot TWRP but I'm just stuck at the TeamWin logo screen. I pulled the battery after 5 minutes, turned it back on and bam.. right back to TWRP!
I swear I did nothing to my phone. It was working perfectly before I told it to restart.
Can I ODIN flash my way out of this?!
Click to expand...
Click to collapse
Nevermind... I panicked for no reason. I pulled the battery, booted into download mode (not TWRP) and rebooted from there and it went back to my Blu Kuban. I'll start my whole process over, but that was weird.
HeyItsRyan said:
The mechanics of some of this stuff is still beyond me, but I'm learning.
However something weird just happened and I have no explanation for it. I was running Blu Kuban ROM with TWRP. I wanted to install SlimBean and try it out, so I told GooManager to reboot my phone into TWRP so I can do a backup of my Blu Kuban config. Now I'm stuck in bootloader loop!
Seriously... it keeps trying to boot TWRP but I'm just stuck at the TeamWin logo screen. I pulled the battery after 5 minutes, turned it back on and bam.. right back to TWRP!
I swear I did nothing to my phone. It was working perfectly before I told it to restart.
Can I ODIN flash my way out of this?!
Click to expand...
Click to collapse
i went into twrp..clicked that middle button on bottom and it wouldn't let me do a backup...i then restarteed and worked fine and wasn't able to replicate the issue
TWRP has some issues