Ok here goes. I got another G1 from T Mobile. I did a backup using nandroid 2.1. The new phone had 1.5 on it already from T Mobile. I down graded it to rc29 and rooted. I went to restore my backup and everything seemed to be ok untill it reboots. I had no errors doing the restore with nandroid. System, userdata, and boot images all had ok's. The only backup it will let me do is one from May and I was running JF 1.5 crb21. I have upgraded to JF 1.51 crb43 and did a backup of that but when I try to restore it freezes on te G1 screen. I now have Nandroid GUI and everything goes smooth untill it reboots with any new backup. It will let me put any version of android on but will not let me restore it. I have used Hard SPL and Engineering SPL. I'm pulling my hair out here.
Anybody want to try?
Not 100% sure this will work, but might as well give it a try:
First try completely wiping the phone. Let it boot (if it does) into Android.
Then, try to re-restore the backups you have by turning it off and Home + Pwr
I did that already. Next.
oxman504 said:
Ok here goes. I got another G1 from T Mobile. I did a backup using nandroid 2.1. The new phone had 1.5 on it already from T Mobile. I down graded it to rc29 and rooted. I went to restore my backup and everything seemed to be ok untill it reboots. I had no errors doing the restore with nandroid. System, userdata, and boot images all had ok's. The only backup it will let me do is one from May and I was running JF 1.5 crb21. I have upgraded to JF 1.51 crb43 and did a backup of that but when I try to restore it freezes on te G1 screen. I now have Nandroid GUI and everything goes smooth untill it reboots with any new backup. It will let me put any version of android on but will not let me restore it. I have used Hard SPL and Engineering SPL. I'm pulling my hair out here.
Click to expand...
Click to collapse
if you know how to use adb,type in adb logcat and see whats going on.
if not, put JF's latest rom on your SD card, rename it update.zip
do a nandroid restore, stay or reboot into recovery, and flash the JF rom and see if that helps. if not you will have to learn how to use abd
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.
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.
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
blackinches said:
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
Click to expand...
Click to collapse
Since you have no idea what you've currently got running and you can't seem to get into recovery then my only suggestion is to get it into download mode. From there get yourself the KK4 one click and take it back to stock. Then flash back to helly bean. As far as your backups go if you're sure of which one is which at this point you should be able to restore from it. But you might just start from scratch and forego the potential issues again.
The backups should all be there though, unless your internal and/or external storage got wiped by accident at some point.
Hello!
Before I want to go on to CWM I want to tell you what happened before.
Yesterday I flashed TWRP recovery which resulted in a really bad situation. I was stuck in recovery. If I pressed reboot it went straigt to recovery again, even if I pulled out the battery. So flashed the stock firmware via the KDZ flashing method and everything worked again.
Then I rooted again, installed CWM, installed CM, installed all my apps (TB backup on PC was quite old),....
So all in all it was a big amount of work and it took me a few hours.
Then everything was working again as it should and I updated all my TB backups and then I wanted to make a Nandroid backup so that I wouldnt have to do all that flashing and installing again.
So I went to recovery--> backup and restore --> backup
But it didnt finish. It always stopped with this error: Error while meaking a backup image of /system!
So i thought maybe I should install everything again, which i did. (I had already made a TB backup of all my apps, so i thought this woulb be done fast)
Well, went to recovery again, did a factory reset, wiped dalvik cache and even formated /system. Then I installed the latest CM + GAPPS and rebooted.
And the first thing i recognized was that the screen popped where it says "android is upgrading". And I wondered even more when I realized that all my apps where stille there. So obviously the factory reset and also format /system didnt work properly.
If I format /system and dont install any ROM then the device doesnt boot (which i guess is the normal behaviour). But what I want to say is that the format works there but if I flash CM afterwards all my apps are still there (despite the fact that i also did a factory reset).
All in all the phone does work normal now, but I'm not able to make a Nandroid backup and I'm really wondering why.
(I also reflashed CWM recovery but that didnt change anything)
I would be glad if s1 could help me.
PS: Could the solution be to flash stock again via KDZ and then do everything from the beginning?
Never heard of anything like this before.
Did you flash the recovery as a .IMG or through Rom manager (I would suggest to flash it with Rom manager).
Try this and report back (maybe your recovery image is damaged or smth.)
Sent from my LG-P880
I have no idea what caused this crazy behavoiur of CWM, but I started over again with flashing kdz and now everything is fine
Maybe your SD card is full. Try deleting a few files from your SD and then do the backup.
Sent from my GT-I9070 using xda premium
I dont have any external sd card and on phone memory there were more than 10GB free space