mixed up update.zip files! bricked my g1 - G1 Q&A, Help & Troubleshooting

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

Related

Failed nandroid backup?

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.

Not completly bricked

Hi guys im wondering if any of you can help me out here.
I have been on cyanogen (latest) for a while but decided to have a go at puting the ''donut'' rom in the android development bit of this forum (eu version as im in uk) on my phone this evening.
I flashed the base version fine and it started up great. Then I flashed the extention (add on) part and it started up but after the ''android'' screen it just went black and nothing happend. So i did a hard reset and tried again, same problem occured.
I then tried to put the latest cyanogen rom back on my phone, put to root, started it up then BAM stuck on g1 screen. Didnt get passed it. So put other roms later cyan roms on and still same problem occurs.
I then freeked out and tried to go back to RC29, so i deleted everything of my sdcard and put the dreming file on, pressed power and camera button and then BAM it comes up with some sort of cyanogen screen and not the rainbow screen. So havent got a clue how to install the dreming file. So gave up there
So this is where im at. Nothing on my sd card. Still got cyan on my phone but cant get it started up, no matter what rom I try it keeps getting stuck on g1 screen.
I know this is completly retarded but I really need help to get this sorted.
ANY HELP WOULD BE GREAT
Thanks
Have you been wipping?
Wiped before flashing donut rom...And when trying to put cyanogen rom back on...
If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.
borodin1 said:
If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.
Click to expand...
Click to collapse
Wow lots of help there thanks.
Firstly tho I cant find this ''base defanged rom'' from cyans website? Can you give me a pointer as to where it is? Is that its name on the website or is that it in short?
Forget that I found ''DRC83_base_defanged.zip''. Downloading it now.

Frozen Boot w/ Custom Icon Install. Help

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

Nook Color Only boots into clockwork recovery

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.

[Q] Nook Color WON'T reset to factory settings!

Ok, so I installed cyanogen and wanted to go back to cupcake (some problems with compatibility for some apps). Made backups but lost them from file corruption. Even recent backups come up with MD5 sums mismatch on ClockworkMod Recovery. Can get cyanogen running again, but can't get back to ORIGINAL state.
I've tried hard booting 8x, I've tried running the script to change the bootcount but this just gets me to clockworkmod. I try running the factory reset/data wipe option, but it clearly doesn't remove cyanogen. When I reboot after this, I get stuck on the word ANDROID in blue. I've also tried sideloading a 1.1 version zip, all to no avail. Any suggestions? Would uninstalling clockworkmod help? Thanks.
Did you flash the 1.1 stock nook image with win32? Remember that in the 1.1 restore you just install "update.zip" through CWM. Are you sure that your original version was 1.1 and not 1.0.1? If all else fails, try a different SD card. Sometimes the SD card itself is the source of problems like this.
Factory resets won't do anything once you have flashed a new rom. You will have to restore it to stock. Nooks are very difficult to hard brick, so something should work.
No, I didn't flash it, just installed the update. My original version was 1.0, but would that make a difference? I wanted to go to 1.1 anyway. Tried a diff sd card, same problem. Any other suggestions?
No matter what I try, it seems cyanogen simply WON'T wipe. Even after formatting via clockwork, and after clockwork tells me it's successfully formatted, it still boots up as normal. I believe it's interfering with restoring to stock.
Solved
MUST uninstall clockwork mod. Finally worked after this step http://forum.xda-developers.com/showthread.php?t=960542&page=16 as per instructions here. Thanks everyone!

Categories

Resources