Database Users

Boot infinite loop

I tried to install expresso on DC 2.07 and the zip file flashed, then when I rebooted it just keeps looping without getting to the OS. I suppose I screwed something up, so I was going to nandroid back, but now the phone won't let me get back into the recovery console. Anybody have any tips on how to get the recovery console back up?

schnoz said:
I tried to install expresso on DC 2.07 and the zip file flashed, then when I rebooted it just keeps looping without getting to the OS. I suppose I screwed something up, so I was going to nandroid back, but now the phone won't let me get back into the recovery console. Anybody have any tips on how to get the recovery console back up?
Click to expand...
Click to collapse
You pulled the battery and put it back in, then held just the home button and the power key?

if the above doesnt do it
Pull the battery put it back in power on hold down home and back. clear the data.

I am currently running the newest version of DC, hours after the update I look down the phone is continuously restarting never making it past the sprint screen.
I go into recovery it says it cant mount to the SD card. so as of right now my phone is dead in the water.
I purchased a new SD card and im loading DC onto it to do a flash. Ill let you know If I get the same thing, mine didnt do it right away but it was fine before the update this morning... oh and Damage whats up with no Wireless Tether??

Mine is doing the infinite loop also. I had everything working and did a nandroid backup. After I rebooted, it started to loop, the nandroid loops also, I wiped the ext on sd, and still get the loop.

RPerry435 said:
I am currently running the newest version of DC, hours after the update I look down the phone is continuously restarting never making it past the sprint screen.
I go into recovery it says it cant mount to the SD card. so as of right now my phone is dead in the water.
I purchased a new SD card and im loading DC onto it to do a flash. Ill let you know If I get the same thing, mine didnt do it right away but it was fine before the update this morning... oh and Damage whats up with no Wireless Tether??
Click to expand...
Click to collapse
dwertz said:
Mine is doing the infinite loop also. I had everything working and did a nandroid backup. After I rebooted, it started to loop, the nandroid loops also, I wiped the ext on sd, and still get the loop.
Click to expand...
Click to collapse
So you guys can get into Nandoird, you wipe data, dalvik and ext partition, reinstalled ROM and you still get a boot loop?

Yes exactly..
I ruled my phone bricked earlier for no reason at all. phone was fine, i did the update to 2.7.2 and hour or two later it keeps looping..
I tried New SD card,erase data, davlik, re partitioned, downloaded a fresh version off the net just incase my copy was corrupt and still looped
I took it to the sprint store before they closed and got a new phone.
I Would seriously look into this obviously I wasnt the only one

danknee said:
So you guys can get into Nandoird, you wipe data, dalvik and ext partition, reinstalled ROM and you still get a boot loop?
Click to expand...
Click to collapse
Yes TrevE says it may have something to do with /data/private-app/
http://forum.xda-developers.com/showpost.php?p=6174954&postcount=1951
All I know, it boots like normal, I install exchange, hotmail. some market apps. titanium apps, paid and free, then when I went to reboot I backed up in nandroid, then when it actually booted, it was stuck in the HTC quietly brilliant and the start up of the sprint logo and keep looping. TreVe suggested adb logcat but I can not get that far to log the error. He said he logged it as the private-app
Oh I also tried to delete sd ext, davik, remove sdcard, run from the nandroid back up and everyway made the loop. I think TrevE is onto something though. I have one app that I install that is a private app that is from Titanium that may cause this.
Oh and btw, if I wipe the rom and reboot it boots up normally so i think it has something to do with something that is installed. Is anyone else using titanium backup to restore a paid app? Installing a paid app from the sdcard??

RPerry435 said:
Yes exactly..
I ruled my phone bricked earlier for no reason at all. phone was fine, i did the update to 2.7.2 and hour or two later it keeps looping..
I tried New SD card,erase data, davlik, re partitioned, downloaded a fresh version off the net just incase my copy was corrupt and still looped
I took it to the sprint store before they closed and got a new phone.
I Would seriously look into this obviously I wasnt the only one
Click to expand...
Click to collapse
Not much left to look into since the phone is gone. I would have restored to the unrooted 1.56 ruu to test, but I guess a new phone is good too.

Try flashing a different ROM as in different frameworks. Sometimes going back to a 1.5 ROM can fix weird issues like that.

I went with fresh's Rom this time instead of dc. Everything has been good so far.

I had a problem with a loop with both DC and Fresh. It all began after I set up my Exchange email. I am using Touchdown and I haven't had any issues.

Keep on mind I never added or used any private apps. This happened after the update through the loader. I changed nothing and have been using the same apps for months.

I kept having these issues after 2.07.2 even after a full wipe and reset still no dice. So I just went to Fresh.

clockwork partition woes

So im rooted, clockworked and nandroided. i go into rom manager and attempt to partition the sd, everything looks like it went fine. i get the samsung splash tmo bootup then it goes from the S splash screen to what seems to be a soft brick, just a blank screen and four lit up buttons. i try to boot into clockwork and i get the factory recovery mode. Clockwork is nowhere to be found. my sd card appears to be partitioned it shows a 14.8g card on a 16g, but the sd card still has everything on it, it did not get wiped. i have tried using odin, all that happens there is it runs through the motions, resets the phone back into this soft brick. anyone have similar issues or helpful ideas? i will be slowly bashing my head into the wall waiting for a reply. thanks in advance, any help will be appreciated

Same Problems Here
I came on to post and hopefully find a solution for a very similar problem. I rooted, clockworked, and nandroided my vibrant this morning and it worked fine all day. I got home and realized my phone was locked and didn't respond to the unlock button. I pulled the battery and rebooted and it all seemed fine. 5 minutes later i realized it wasn't responsive and once again pulled the battery and now won't boot past the "S" boot screen and seems to freeze. Now my clockwork restore won't backup and says it can't mount. I've tried a factory reset to no avail. Anytime I attempt a clockwork recovery I get the error
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Can't mount /data/!
Any suggestions or solutions would be greatly appreciated.

I'm having the same issue, any help would be greatly appreciated.

did anyone get any help??

Same thing happened to me. I posted such on the market comment for rom manager. I ended up taking mine back to Best Buy (got another). I'm wanting to install linux on mine. Anyone been able to do that?

I hate to tell you this but you just partitioned the internal memory. If you had actually read the thread on clockwork recovery you would have seen that you cannot currently partition the external sd card with clockwork.

so what do i do??

nickerrides said:
so what do i do??
Click to expand...
Click to collapse
I honestly don't know the answer to that question. I'm kind of a casual flasher of my phones and I've never "bricked" one or had any major problem. I believe it can be fixed by using odin to flash back to stock. I'm pretty sure that you can recovery from it but it may take some work.
I would start by reading the entire clockwork recovery thread in the Android Development section. A few other people have made that mistake and may have a solution posted there. I'm at work posting from my phone or I would go look and try and find it.

Okay, I did some digging in that thread and it appears all you need to do is to use the re-partition option in Odin and then use Odin to flash a stock ROM and you should be all set.
Again, I have not used Odin myself so I don't know how easy/hard that is to do or if it will work at all.

nope i tried the repartition option in odin while flashing the stock rom.

With mine, I had success and got it out of the boot loop by using odin and flashing it back to stock.
The phone seems unbrickable, as
others have mentioned, just get it into download mode and use odin carefully.
Sent from my SGH-T959 using XDA App

wanna be more specific on what exactly you did?

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!

Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?

Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.

kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?

To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed

Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem

Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!

enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

Stuck in the CW recovery screen, tried everything.

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.

Help Please!! Phone will not boot after trying to re-load ROM.

Ok, I went in today to reload MOAR ROM on my phone. I had initially thought to check if maybe there was a higher compatible firmware version than BOC4, so I posted to the thread, but then I figured everything was working fine on my phone so why bother.
I loaded NI2 and booted up into safestrap recovery.
Once in safestrap, I tapped wipe, but strangely, it was like the touch screen registered 2 rapid taps, and before I know it the phone is formatting. Me, I try to do a data wipe after this, silly me, and it doesn't work. It no longer seems to detect distinct partitions, probably cuz the entire internal drive just got formatted.
Anyways, I proceed to install MOAR, and then the BOC4 firmware. Now the phone starts to boot, gets to Samsung screen, hangs there for a few seconds, then reboots. It's caught in a boot loop. I am guessing that safestrap might have been removed, and I am looking advice as to how I might go about reloading it, if that is indeed my problem.
Or really, any pertinent advice on how I might make my phone function again would be greatly appreciated!

Worth noting, I am able to boot into Recovery, which I am pretty certain means that my phone is not bricked. Just not sure what to do from here. Thanks!

hmm.. I just tried factory reset in recovery, and now it maybe appears to be booting for first time. I have that spinning tornado boot animation that came with MOAR. Should maybe come up in 10-15 min, fingers crossed...

musiclover7 said:
hmm.. I just tried factory reset in recovery, and now it maybe appears to be booting for first time. I have that spinning tornado boot animation that came with MOAR. Should maybe come up in 10-15 min, fingers crossed...
Click to expand...
Click to collapse
Did it work? If you formatted, assuming you are not on the latest bootloader, you'll need to flash the NCG restore tar and start the root process from the beginning.
Also, I'd suggest upgrading to @jrkruse latest safestrap, as it removes the format button.