Related
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.
I tried to uninstall Voodoo and now when I restart my phone it shows the galaxy
s and verizon animations, then loads up to a black screen and lit up capacitive icons. I can reboot into recovery, but I can't seem to mount the sd card and i keep getting errors when I try to mount any extensions. Please tell me there is something that I can do to fix this.
try wiping?
try instructions from "how to remove voodoo completely" thread. i cwm flashed the file from there when i had the same problem as u.
Take a deep breath. If you can see any thing at all on your screen, it's not bricked.
Just follow the instructions here;
How to remove voodoo
And your phone will be like new.
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
i had a similar problem when i tried to remove the old lag fix.
screen turned black on bootup and lights would come on but nothing else...
i had to use odin to restore everything and i had to wipe the cache and data from recovery.
Sometimes pixie dust works...or just listen to them
Sent from my sharks with fricking lazers on their backs
Thank you for the replies. I was able to finally mount the phone after doing a nandroid. It was force closing like crazy, but I kept with it until I was able to mount the phone from the os. Then I put in the voodoo lagfix uninstall folder and wiped and rebooted. Then I was able to nandroid to another backup and wiped, then did a odin restore, wipe and nandroid data restore. Now it's running like new and voodoo is uninstalled. This is an interesting experience coming from the hero and droid. I am a champ at those phones and I have never bricked a phone and I bricked this one twice. Kind of reminds me of the first time I started playing with my hero. It's a way to get the blood pumping.
emplox said:
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
Click to expand...
Click to collapse
This. My removal utility is a pain in my ass
I found it works, but then you gotta battery pull and nandroid back. A clean wipe wont cut it.
I disabled voodoo lagfix and the phone would not boot. I tried to use Odin and now all I get is force close when the phone boots up and it will not let me mount the card. any ideas?
Since I initially wrote this thread, I tried Voodoo one more time and when I removed it, this time with an app to see if it was user error, it once again made my phone non-responsive, it seems that it just is a bit unstable when being removed. With that said, I was where you are now and I was able to restore it. I did a factory wipe of my phone and cache through clockwork and then replaced my kernel and put the full stock image on the phone through Odin. Then I went into clockwork and went to my last backup and restored data. The phone loaded up, but it was as if I did a factory reset. I skipped everything, mounted my phone to my cpu and deleted voodoo files manually (the file needed to remove vodoo was just sitting there too). I went back into clockwork and just restored data under the advanced settings and I was back in business. Hopefully this can help you too. It may be overkill, but it worked.
You did NOT brick your phone. Will people please stop saying they bricked their phone when they haven't? Bricked means YOU CAN NOT RECOVER!!!! Stop scaring and confusing people! pretty please.
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Kamar234 said:
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Click to expand...
Click to collapse
I believe the preferred term is "soft-bricked"...LOL
Just do a wipe. I used adrenalines uninstaller. Worked like a charm. Voodoo is a pain in my butt
Sent from my SCH-I500-Fascinate using XDA App
Haha, yes, I've seen people use the term soft bricked here. Voodoo's instability is interesting though. I haven't felt this way since I started using smart phones in 03'. Just something I can't seem to get to work. Good thing the payoff isn't that great. To the person who is having trouble with their phone, I hope I, or someone else here, was able to help.
I just removed lagfix and it worked perfectly. Lol my phone never had lag until I installed lag fix. But I do love the kernal And boot animation provided.
Wanted to say I removed voodoo tonight by adding the remove file via adb. Everything worked as planned. Took about 10 minutes to get off step 2 but everything completed and booted up.
Sent from my SCH-I500 using XDA App
I can only offer <3 support... When I tried to remove Voodoo the first time, ugh I went through hell. I was stuck on my loading screen with Samsung just staring me in the face. Followed the complete remove by Adrynalyne, and everything was ok in the end.
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Self-dangerous noob here. NC 1.2, theoretically returned to stock
History:
Got NC 1.2
Rooted w/ManualNooter 4.5.25. Everything seemed to go great. So...
Downloaded, backed up, and flashed CM7 in ROM Manager
Wouldn't boot...hung on n COLOR screen
Same results w/ Phirerom (CM7 based - doh)
Able to restore MN4.5.25 from CWM - BUT noticed "Error formatting /data!" during nandroid restore. Didn't seem to matter...restore successful
Get "Error formatting /data!" no matter what
Able to boot into CM7 from SD, but it has "problems". For instance, there are no "back" or "return" softkeys. So there is no way to navigate around any app! Only the hard "n" home key works
Reflashed stock 1.2
Seemed to work, began to ask me to reregister. BUT, it won't display the keyboard, so I'm stuck at the "Login with your existing B&N...." screen! Keyboard flashes up and then immediately disappears!
As an noob, it occurs to me that all my problems are related to my inability to format the /data partition (if it's even called a partition).
Can any of you awesome people help me? And, if I'm in the wrong forum, any directions would also help. Thanks.
Same error here
If anyone can help with this it would be much appreciated.
have you tried removing CWR then do the 8-boot reset?
No, every time I've done it, it boots into CWR. Maybe REMOVING it will help. lol. Sorry to be so inept. I can flash the 1.2 stock that will remove CWR. Is that the way to do it?
Worked like a charm
Removing CWR and 8-boot-interrupts did the trick. I'm now back to a fully stock NC 1.2.0. Ready to roll up my sleeves and re-brick!
This is the most amazing community. The closest thing I have to any technical knowledge is speaking a little Klingon. VERY little. But, I have learned more here by reading these threads for a couple hours...OK, several hours... than my wife has learned in a dozen trips to the apple store. I feel more empowered every day. You are all great. Can't thank you enough.
Goldie, I wasted a bunch of time on this last night. I'm guessing you have a new nook. If you do, slap cwr on your SD (3.0.2.8 or something) and look for the thread that tells you how to repartition your nook. Follow instructions to set it to the old way. After that run manualroot zip through cwr. Reboot to cwr and wipe data, system, cache. Finally install your rom of choice from your SD card through cwr. That's what I did to finally get it to work.
Thanks. I'll give this a try. As you probably guessed, I DO have a new NC, and while I was able to get it back to 100% stock, and easily reregister it, I had the same results. The ONLY way I can get CM7 running is off the SD card. So, I'll try the partitioning trick. Why do I get the feeling this is going to work? Unfortunately, I'm not on dev's time... I'm at work by 7:30am EDT, but in bed pretty early. I REALLY appreciate the response. Later this week I'll install SDK, and all my tools at home so I'll be able to stay up all night with you awesome folks.
still looking for the thread on re-partitioning. I found the thread on restoring, but I get the error every time I try to reformat the /data.
No luck. I can restore to stock 1.2, reregister, and MN 4.5.25, all easily. BUT, once I flash CM7 (or Phiremod 6.3, etc.) it hangs at the "n C O L O R" screen (C O L O R flashing at various speeds just to fool you into thinking it's actually going to work). Here's what I've noticed...after flashing CM7, the ADOBE screen no longer flashes up at boot. Once it fails to boot the Adobe software, it won't boot at all. So, for now, I guess I'm running CM off my SD unless anyone can suggest anything.
Goldie u have to repartition to get it working. Ill go look for the thread. Also maybe you should try out the cm7 mod over the phiremod Tom. I'm on phiremod now and the lag is killing me
Wow that was painful to find. Needs a sticky.
http://forum.xda-developers.com/showthread.php?t=1094371
Edit: I take that back about the lag, set your cpu to 1200 in the ROM and change yourgovernator to interactive for an amazingly smooth experience
I've been going nuts trying to figure this out. I too ran into the "error format /data" message but I powered through it only to end up at at the Android logo--nothing. Out of frustration, I returned to CWR and wiped everything--like on my Evo (did not go through to mounts option). That seemed to go through /data but I don't know the difference between a wipe and a format (I'm looking...). Still got bootloops. I tried to return to stock but the 8 interrupts wouldn't work.
Pressing START and N worked though and that got through to CM7 and it's working great now but I'm afraid to do anything else because I still get the "error formatting /data" message.
I've heard horror stories (bricking beyond repair--if that's possible) of users repartitioning their drives though so... I hope there's another solution out there.
I love this community!!
Sys:
Thanks a million!! Everything perfect!! I just can't say enough about this awesome community, all the amazing devs.
heh you're more than welcome . i hope this helps anyone else that stumbles on your thread as well. Ive been having fun with my nook but i think its time to trade it out for something a little bigger. Maybe ill just wait till att gets its flavor of gs2 idk. So many choices out there!
thanks guys!
i just had the same problem and falshes all kinds
of zips until i found this post.now i've launched cm with status bar
really really thanks
this worked great for me too! i had a nookcolor bought in december and it had a messed up chargerand 6 really bright white spots that were really noticiable. went to b&n store and the guy just gave me a new one. it came with 1.2 and i had the cwm sd from the old one. so tried restoring my cm7 backup from the old one and error formatting data came up. flashed this zip, and im wondering, since these are too different nookcolors, should i restore the cm7 backup or flash it brand new. because i had a ton of stuff on the old one and i dont want to lose it. so can i ust do advanced restore and restore data, or can i restore the whole thing or just flash and slowly get my stuff back?
update cwm
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1
bl3achcrazy said:
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1
Click to expand...
Click to collapse
i have tried 3.2.0.1 but get same error message
3.2.0.1 on the bootable card or already on the eMMC? It has to be on the bootable card.
Thanks
It works after getting my nook color around 2pm today and taking it home. I was working on this thing all day I tried several ways and this one worked!!! Having issues with wifi that's all
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
SOLVED, not sure how i fixed it but i think its because, i first deleted everything i could form clockwork, then went to advanced deleted cache system and something else reflashed now its working...no complaints, however i read on another forum that virtuous fusion is known for brick devices upon factory data resets
Virtuous Fusion is a very outdated ROM.
Use Virtuous Unity.
joeyydaprofitt said:
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
Click to expand...
Click to collapse
well there's a lesson learned...
never EVER do a factory reset within a ROM... lol
btw, when you went to recovery, did it show any errors?
like "E:/ Can't find ..."?