So I was in the apk, theme, taskbars, icons Hero mods thread and picked out some icons to try out. I took the zip and put it on the root of my sd card and went into RA and chose ""Flash zip from sdcard". I then rebooted and it freezes at the HTC screen at the word quietly, where it would normally say
htc
quietly elegant
and it freezes at
htc
quietly
Can you please tell us what ROM you were running and exactly what you flashed?
So then restore from your most recent Nandroid backup...
I am running Fresh 2.0d and the icons I flashed were some 2.1 icons from the user Godzson
NOTHING on the first page will work with the newest roms. With the exception of those that are actually labeled that they will work...Hope you backed up....
@ccapasso I am a little new to the whole android rooting, custom, whatever. Does nandroid come with Fresh 2.0d? Either way I don't have a backup. I guess the easiest way to fix it would be to just wipe it/factory restore and flash Fresh 2.0d again?
@obannvi If I installed some icons that work on my rom, would it replace the ones that screwed my phone up and make it work?
Nand backup is created in RA. It's recommended that you create one before flashing anything new. Just boot back into RA and reflash Fresh.
Okay thanks for everyones help, I will make sure to do a backup next time
Related
I've been running JACHero 2.7.3 lately and happy with it, I've also been using the cm-recovery 1.3.1 recovery image but noticed there was a v1.4 with a few new features and also thought I'd try out Drizzy's TouchFLO 3D to see if it appealed to me more. Here's what I've done so far..
Hero 2.7.3, cm recovery v1.3.1 - nandroid backup done a few days ago.
Updated cm recovery to v1.4 while in Hero.
Rebooted, nandroid backup done from v1.4 recovery image.
Wiped then applied Drizzy's firmware.
Repaired permission (always do, just in case) then rebooted.
Phone starts up, G1 splash and then I get to the Hero splash image where it goes into a loop. It won't go past the Hero splash at that point.
Figuring I might not have formatted I recreated the partitions on the SD card, can't fail to be formatted that way. I also decide to reflash JACHero 2.7.3 and try to restore my nandroid backup from about 10 minutes earlier.
Restore completes, I reboot and it got stuck on the Hero splash again. I've just managed to flash it again and it has gone into the OS but it's a blank slate. I've got both a nandroid 2.1 and 2.2 backup but trying to restore the 2.1 with 2.2 failed.
The question I'm looking for an answer and help on is would I be better off putting cm recovery 1.3.1 on and using the old backup or is there something I'm doing wrong with the 1.4 recovery and nandroid backup? I can go about setting the phone up again manually but that's the point of the backup. Help :/
OK, I'm not sure what stopped the Hero splash lock-up but it's gone now. I restored the backup and it worked... all I had to do was reinstall applications since they were all showing as broken links. False alarm or pain in the butt freak problem, either way it's resolved.
Dyonas said:
I've been running JACHero 2.7.3 lately and happy with it, I've also been using the cm-recovery 1.3.1 recovery image but noticed there was a v1.4 with a few new features and also thought I'd try out Drizzy's TouchFLO 3D to see if it appealed to me more. Here's what I've done so far..
Hero 2.7.3, cm recovery v1.3.1 - nandroid backup done a few days ago.
Updated cm recovery to v1.4 while in Hero.
Rebooted, nandroid backup done from v1.4 recovery image.
Wiped then applied Drizzy's firmware.
Repaired permission (always do, just in case) then rebooted.
Phone starts up, G1 splash and then I get to the Hero splash image where it goes into a loop. It won't go past the Hero splash at that point.
Figuring I might not have formatted I recreated the partitions on the SD card, can't fail to be formatted that way. I also decide to reflash JACHero 2.7.3 and try to restore my nandroid backup from about 10 minutes earlier.
Restore completes, I reboot and it got stuck on the Hero splash again. I've just managed to flash it again and it has gone into the OS but it's a blank slate. I've got both a nandroid 2.1 and 2.2 backup but trying to restore the 2.1 with 2.2 failed.
The question I'm looking for an answer and help on is would I be better off putting cm recovery 1.3.1 on and using the old backup or is there something I'm doing wrong with the 1.4 recovery and nandroid backup? I can go about setting the phone up again manually but that's the point of the backup. Help :/
Click to expand...
Click to collapse
If I'm not mistaken, the new nandroid version in Cyanogen's 1.4 gives the subfolder under the nandroid folder a different name than the 1.3 version. 1.4 may not be able to find your backup because its looking for the wrong folder. I believe the folder under the "HT blah blah" used to be just a numeric date in 1.3. Now in 1.4 it is alpha-numeric. You may look into this as being the culprit and try to flash 1.3 back to perform the nandroid restore.
i have cyanogen's 4.0.4 rom. nandroid installed and i should have a nandroid copy. i think i mixed up xrom black theme update.zip file with cyanogen blue theme update.zip file as it looks like i installed xrom update file and now phone is stuck on the Tmobile G1 screen! i hooked up my sd card to the laptop and put the right update and tried again. nothing. put cyanogen's rom again and tried. nothing. used nandroid backup. still, phone is not booting!!!
what do i do in this case?
wiping before flashing always cleans the pipes better, so wipe and reflash to make sure you got it all cleaned up
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.
Is there a way to get rid of the clockwork mod boot on the nook color
As per onstuctions on this site, I got a 1.1 pre roote version and installed it
from the sd card with the clockwork menu which informed me that the
"NookColor" install complete.
when I reboot, it starts with the welcome message,but then only reboots into the same recovery menu.
At this point I would just like to go back to a stock rom, but cannot boot anything but the recovery.
By the way, I can boot froyo from the sd card
Please help me
I've moved your thread to the correct forum.
So you dont have the CWR sdcard in? Because if you did, you would need to remove that first. Sorry if this dumb, but thats all I can think of right now. Maybe reflash the 1.1 pre rooted rom? Or follow the instructions in Samuelhalff's "Easily restore to stock" thread located here in the Nook forums.
The "Easily restore to stock" saved the day. I am now up and running.
Thanks
How did you do that? I have CWR on mine and I went to buy a book from the shop on the Nook and it downloaded and installed 1.1... Now when I try to go back and restore from backup CWR doesn't respond... All it does is sit there and if I select something from the menu it goes to the background image (the circle with the top hat) and sits there. I would like to remove this so I can reroot my Nook...
Thanks for any help.
Bob
See the other thread or sticky that's labeled "How to Restore to Stock easiliy." I believe you can also use the power down and on 8 times trick to restore to stock as well.
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
porear said:
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
Click to expand...
Click to collapse
Ditto that. I reinstalled CW and everything seems to be working fine. Has anyone else had issues with using Rom Manager on the NC? I've had to go back to stock twice whenever I've used it.
I had a problem when trying to roll my 1.1 rooted NC back to stock because I futzed it up that I ended up in a CWR loop. 8 resets didn't get me a reflash, it got a recovery. Took me finally getting the NC flashed and rerooted at 1.1 a second time when I reinstalled ROM Manager and ended up with the problem again. Took me this wasted effort to realize that CWR runs in lieu of the reflash if CWR is installed and that's an obvious problem when I wanted a reflash and not restore a different backup.
There is a thread with a zip that CWR can run that blasts CWR off and reflashs stock and getting that done put me back both times I messed up above.
Seems to me that perhaps the whole "can never brick" response when people ask for help needs to have an addendum about how CWR gets in the way of an 8 reboot reflash and provide guidance on how to get that update file and use it instead to get back to square one. (Plus some advice on when to clear caches and data partitions to avoid weirdness later).
Now rerooted on 1.1 with no ROM Manager running but I'm missing the nandroid bacjup capability, so maybe I reinstall but stay away from the recovery option until I need it?
I reinstalled CW after I rerooted 1.1 and have had no problems with it so far, but I also haven't tried to backup or anything since the first time (which initially got me into this mess).
I do think you're right about having some sort of addendum thrown in. I was running circles around the XDA forums for a few hours trying to find some sort of fix the first time my Nook started acting weird. The 8-reboot trick just wouldn't work, and my battery was more or less drained because CW was interfering. Maybe this is just understood by most, but it certainly would have saved me some time (and some gray hairs) if someone had mentioned it earlier.
So what is the conclusion of this thread? I have a new NC, updated to 1.1 and installed AutoNooker 3.0, immediately installed Clockwork and did a NAND backup... bad thing is that it won't boot off the eMMC anymore, only CW.
I can boot roms off of the SD card (ie Honeycomb) but this isn't want I want. I've downloaded and flashed several roms but its looped at CW. So the rom isn't the problem.
If we can't install Clockwork Recovery, then how can we flash new roms to the eMMC?
[UPDATE]
Found a flashable file which removes Clockwork Recovery.
http://www.etoile-laconnex.com/CWR-removal-rootsafe.zip
After I flashed that I am now booting off the eMMC froyo rom. Nice! Saved me from Restoring it, updating it, and reRooting it.
[UPDATE 2]
Well while it worked initially, it loaded the homescreen and reset. Now it is stuck at the "Touch the Future of Reading" screen with no Recovery... which worse off. Now I have to make a CWM bootable SD, flash the restore, and start over. Nice.
[UPDATE 3]
Finally got it back to stock after hours. I found a "MonsterPack" here:
http://forum.xda-developers.com/showthread.php?t=922870
Even this was more complicated then it needed. I had to download the 128mb RootPack image, and get it going so I can grab the needed root files. Then download the right size Clockwork image for my memory card and get it going. The end result ended in a Clockwork SD card. Then I made a "sdcard" folder from where I added the rootpack files and the stock image 1.0.1 flashable zip file.
Format the system and boot partitions, then flash the stock zip.
I just upgraded stock to 1.1, then will proceed to boot off the microsd and root, install GAPPS, etc.
I wish I knew of a great custom rom to flash. I flashed Nookie Froyo 0.6.8 and it powers down immediately (several complaints about this). Maybe CM7?
Ditto
I'm having this problem as well, but I can't seem to do anything to fix it. I was running 1.1, and auto-nootered using v3.0. Everything was hunky dory until I installed CWR. I flashed, shutdown, restarted, then chose to perform a backup which brought me down into CWR and I was never able to get out. I used the Monster pack zip to remove CWR, and now I boot to the "n" screen and sit forever. I tried the 8 hard resets and it said it installed on two different occasions, but still I sit on the "n" screen during boot. I tried the 1.0.1 restore zip as well, but to no avail. What do I need to do to get back up and running?
CW Recovery only
So I flashed my NC with both the pre-dualboot and the dual-honeycomb rom, but every time I reboot with the SD card inserted, it only boots to CW recovery. When I take it out..it boots to NC stock OS.
Am I suppose to remove clockwork recovery with the CW-removal zip? I tried that.. once it rebooted it went right back to CW. Should I be using two different SD cards? One for CW recovery and one to load the eMMc?
So confused...
What I need to know is what should be on the SD card after everything is flashed.
Mw : you could use a bootable cwr sdcard and flash 'emmc recovery repair', then format data and restore your backup.
Ehamonn: you have to remove cwr from the sdcard. Format should do the trick. But you'll loose the data on it..
Sent from my Desire HD using XDA App
Do I need to keep a boot image on the card after I format?
Well, if you only want to boot from internal memory, no.
So I've never had problems backing up my Nexus one in the past using clockwork mod, but the past day, I've been trying to back it up so that I can try out Rodriguezstyle's new MIUI mod, but the backup keeps getting stuck on "Backing up sd-ext"
In particular, it says its getting stuck on "apparently this looks like a link?"
look down vertically for the thing I'm getting stuck on.
However, when I've pulled out my battery and reset into the recovery, I've found that the backup I was trying to make has actually been logged. I've been too scared to actually try to restore that backup to see if it's worked, because honestly I don't have any other recent backup and I don't want to mess anything up.
Any help would be appreciated! I might try to flash another recovery and backup that way...
I'm running RodriguezStyle's 2.9.2 MIUI ROM along with wildmonk's kernel and the most recent version of ClockworkMod Recovery if anybody's asking.
apparently I can't write out the exact file that it's stuck on...it thinks that it is a link...
ok here goes: "[email protected]@[email protected]"
Have you tried to fix permissions?
Yup I've tried that multiple times, rebooted, and it still didn't work.
You using cwm 3.0? It's known to cause problems like that. Happened to me before that's why I switch to amon ra
crazylilazn said:
So I've never had problems backing up my Nexus one in the past using clockwork mod, but the past day, I've been trying to back it up so that I can try out Rodriguezstyle's new MIUI mod, but the backup keeps getting stuck on "Backing up sd-ext"
In particular, it says its getting stuck on "apparently this looks like a link?"
look down vertically for the thing I'm getting stuck on.
However, when I've pulled out my battery and reset into the recovery, I've found that the backup I was trying to make has actually been logged. I've been too scared to actually try to restore that backup to see if it's worked, because honestly I don't have any other recent backup and I don't want to mess anything up.
Any help would be appreciated! I might try to flash another recovery and backup that way...
I'm running RodriguezStyle's 2.9.2 MIUI ROM along with wildmonk's kernel and the most recent version of ClockworkMod Recovery if anybody's asking.
Click to expand...
Click to collapse
Did you find any solution? I have the same issue after trying to restore from CWMrecovery. I have changed to Amon_RA so I will never come back to CWMr...
But I would like to recover to backup...
Clockwork recovery versions 3.x and higher have been known to mess up ext partitions. You may need to reformat your card and switch to an earlier version of Clockwork (or maybe try Amon Ra).