Database Users

Trying to root - problems [SOLVED]

Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.

Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.

So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?

I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.

Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App

whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.

Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?

Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.

i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique

Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.

Did you run the stage1 and stage2 bats while in recovery?

dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?

jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.

Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?

Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?

Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave

Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App

EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?

Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.

jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!

Please, help a n00b. I think I broke my Nexus S 4G

Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?

Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.

My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?

CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip

here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......

I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App

soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer

[Q] another brick story

I have been working on this for the past few days and for the life of me cannot figure out the problem. I'll start by just laying out a sequence of events.
Bought A500 about a month ago. OTA'd to HC 3.1 4.010.13_com_gen2
Decided not to wait for OTA 3.2 and rooted with iconiabreak.
Did not do a backup (like an idiot, i know)
Flashed Taboonay 2.0 with Thor's 2.1 kernal.
Saw awesome post to get rid of cell standby by deleting phone.apk and telephony.apk....do i did that.
Realize i am an idiot and then run a Nandroid backup.
Was happy for a few weeks when i see that Vache had updated taboonay to 2.1b and decided i wanted to do that.
Downloaded the files and started to flash with CWM. Factory, cache, dalvik wipe. Run Taboonay zip.
Get stuck in bootloop at Taboonay boot screen. $#!t......
Think "it's ok, ill just do an update.zip and go back to 3.1"
Try almost all the files on Vache's full package and update thread.
I put each one on an ext sd card and throw it into recovery boot. The Android guy with gears shows up and it looks like it is going to work.
The progress bar gets about 90-95% of the way when everything just stops. Gears animation, progress, everything.
It then reboots and gets stuck in a bootloop at the android screen. Load a different update.zip and same thing happens each time.
I try to just do a normal recovery boot, but CWM isnt there anymore and i get the ! android.
Normal reboot gives me a bootloop.
So i am stuck and asking if it is the phone and telephony apks that caused everything? if that were the case, how would i be able to load them back up since im totally locked out. I havent tried adb since im out of town for a few days. Thanks for any help that anyone can lend me. Ill try to answer any questions for any information that might be needed.

bumping for great justice~
I've tried decrypting update.zip files and vice versa.
still no luck..

try the fall back to 3.0.1
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.

rorohajj said:
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
Click to expand...
Click to collapse
Thanks for the reply.
I don't think that will be a viable option for me since i'm not able to get my UID. i've plugged my tablet into the computer and gotten the "hardware found" bubble. It prompts me to look for drivers (which i havent be able to find) and, i assume because it's in a bootloop, wont show up on the computer.
Does anyone know why the update.zip files would fail at 90%? I think that's really the thing that boggles my mind and is most frustrating.

Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.

jeffw111 said:
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
Click to expand...
Click to collapse
Unfortunately, no I never plugged my A500 into my computer.

quick update:
I was able to use a different computer and found something interesting.
While trying to transfer or open a decrypted update.zip file, i get an error message saying, "Please insert the last disk of the Multi-Volume set and click OK to continue". Clicking OK just brings it back and i am forced to click cancel.
Anyone have any idea what that would mean??? It doesnt happen when I open or transfer the non-decrypted file. Only the decrypted file using Thor's Acer Update Decrypter application on HC 3.1 and 3.2 files.
While loading the decrypted update.zip on the A500, it almost instantly shows the ! android guy, while the non-decrypted files go 90-95% and then reboot into bootloop.
Any help would be greatly appreciated!

first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.

erica_renee said:
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
Click to expand...
Click to collapse
Thanks for your reply, first off.
I'm sorry I didn't make it clear that I had done all of those things during the events of the first post EXCEPT try a different sd card.
So I went out today and bought a PNY 2GB sd card as opposed to the SanDisk 4GB i was using. I formatted it in my Atrix 4G and threw a full update.zip file in there. The first file I tried (from Vache's http://forum.xda-developers.com/showthread.php?t=1113878 thread) was Acer_A500_4.010.38_COM_GEN1 (HC 3.1). Since I was able to open the .zip without decrypting it I loaded it only the sd card. It did the same thing as before (loaded to about 90% then freeze, reboot) except this time I got a "Boot verification failed..." message in bright red letters up at the top left of the Acer screen. Since it didn't work, I loaded Acer_A500_7.006.03_COM_GEN2 (HC 3.2) onto the sd card. Again, since I was able to open the .zip file, I assumed that there was no need to decrypt it. Loaded the sd card and put the tablet into default recovery (not CWM recovery which I no longer have). The same problem keeps happening: it loads to 90%, freezes then reboots. This time, however, it went into a bootloop at the "android" screen.
I've tried decrypted versions of those files, but I always get an error message while trying to open them and when trying to flash them in default recovery, it almost instantly goes to the ! android guy since I'm assuming those files are already decrypted and decrypting them again is bad.
Hopefully if I try enough files, I'll find the one that works...
Until then, if anyone has any ideas as to what I might be doing wrong or should be doing differently, please let me know!
Thanks.

there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.

erica_renee said:
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
Click to expand...
Click to collapse
Thanks for your suggestion.
I was able to find my UID from an old CWM backup file and tried this method. I attempted it last night with no success. I was actually in the middle of making a reply saying how heartbroken I was and that I was basically giving up. I decided to try it one more time and made a slight adjustment from my method last night. In the UID file, I had my UID in there as 0x0blahblahblah and kept getting the incorrect UID error in the program. When I tried taking out the first 0x in the program, it gave me an incorrect format error. That is where I was messing up.
Instead of 0x0, all i needed was 0blahblahblah in the UID file.
Attempted the upgrade utility again, and viola! It worked like a champ.
So thanks again to all that helped out and offered suggestions and to all the Devs for their outstanding work. I've definitely learned a lot from this experience.

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

Please Help!-Restoring a Color Nook to factory settings

Last summer I rooted my color Nook using Auto Nooter 2.1. I plan to give this Nook to a family member and I am struggling to return this to it's factory settings. I have read and watch the instructions provided by The uNlockr-How to Restore the Nook to it's Factory settings. I get as far as flashing the SD card, however that's where things take a left turn. The file names on the downloads they describe are not in the current downloads I can find. I have downloaded and flashed the img file for 4gb_clockwork-0.7.tar.gz. When I look for the actual Nook restore files every discussion thread leads me to here: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 I've downloaded the large 200+MB file, extracted it... however none of the file names match the instruction per unlockr or the video:
Where am I going wrong? I have spent nearly 4 hours trying to navigate this Chinese maze? I'm sure that I have overlooked something but at this point I can't see it.
Any help to get me to this final destination I would greatly appreciate. I have a deadline of Monday afternoon to get this root righted.

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1461172
HB

wheresgrant said:
Last summer I rooted my color Nook using Auto Nooter 2.1. I plan to give this Nook to a family member and I am struggling to return this to it's factory settings. I have read and watch the instructions provided by The uNlockr-How to Restore the Nook to it's Factory settings. I get as far as flashing the SD card, however that's where things take a left turn. The file names on the downloads they describe are not in the current downloads I can find. I have downloaded and flashed the img file for 4gb_clockwork-0.7.tar.gz. When I look for the actual Nook restore files every discussion thread leads me to here: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 I've downloaded the large 200+MB file, extracted it... however none of the file names match the instruction per unlockr or the video:
Where am I going wrong? I have spent nearly 4 hours trying to navigate this Chinese maze? I'm sure that I have overlooked something but at this point I can't see it.
Any help to get me to this final destination I would greatly appreciate. I have a deadline of Monday afternoon to get this root righted.
Click to expand...
Click to collapse
First off... the files you download from the thread above are CWM installable.... don't extract them... place the one you want to use on uSD and flash it... After you flash it... the Power + n boot will return to factory with 1.4.1 update installed.

Dizzy... Sincere thanks. Am I to assume that I should select the file romrestore.zip ? again all of the directions I've followed none have mentioned the use of this particular file. To make matters worse I downloaded a zip of nook-complete-restore-1.0.1.zip and the file is completely corrupted. I can't find a 1.4.1 version of the complete restore on available servers.

OK... my guess is that it not the correct file. I move the romrestore.zip to the nook power+ Nboot. reformatted system & data... fine. Installed romrestore.zip. "assert failed E:Error in sdcard/romrestore.zip. Installation aborted. Can someone give guidance on the correct file to install and where to find it?

You do not need the romrestore.zip.... just flash the file you downloaded from post 148 in the other thread... then if you reboot into stock recovery with power + n it will do the reset factory data.
The romrestore.zip file you are referring to was written to replace cwm recovery files with 1.0 stock recovery files... this is done with the 1.4.1 files I put together with that versions files.

Dizzy,
I appreciate you being patient with me but something is getting lost in the translation. Is this used in conjunction with the 4gb_clockwork-0.7img? I've used that to flash the SD card first. Then I've moved the entire 202MB nookcolor_1_4_1.zip to the SD card. Upon Power +nboot I come back to the same menu of options asking me whether I want to apply sdcard/update.zip. Each time the installation fails.
I fear I am mixing processes and files that don't belong together. Can you please just give me the simple steps (or point to them... post 148 doesn't explain what to do with those files). I'm batting 0 for 12 right now.

You sure are making this hard. If you will read the thread I linked in post#2 you will see just how easy it is.
It will take you back to whatever that Nook shipped with. Mine goes back to v1.3, my BIL's goes back to 1.0.0. Upgrades from there should happen automagically.

Your right. I was making this harder than what it was. I did take your advice and I tried the 3-finger reboot method. Eventually I was able to boot to the factory rom... but here is the kicker... the nook must be plugged into it's power supply (not running on it's battery) to hard reboot. Again, Google is both thy enemy and thy friend. I understand hacking doesn't come with a manual and these forums exist for the benefit of the community, by the community, but I've found so many incomplete instructions, bad file links, corrupted files... well I'm not really sure anyone can say they have the firmest handle on this procedure.
It's done though... and for the advice given here I'm grateful.

wheresgrant said:
Your right. I was making this harder than what it was. I did take your advice and I tried the 3-finger reboot method. Eventually I was able to boot to the factory rom... but here is the kicker... the nook must be plugged into it's power supply (not running on it's battery) to hard reboot. Again, Google is both thy enemy and thy friend. I understand hacking doesn't come with a manual and these forums exist for the benefit of the community, by the community, but I've found so many incomplete instructions, bad file links, corrupted files... well I'm not really sure anyone can say they have the firmest handle on this procedure.
It's done though... and for the advice given here I'm grateful.
Click to expand...
Click to collapse
Glad it helped.
And for the record I have done this to 2 different Nooks more than one time and never had it plugged into the charger. It IS important to make sure you have a full battery before doing these things.
The good news is that it worked!
HB

Grant... to answer your question... yes the files to flash 1.4.1 from CWM would be flashed from CWM (your clockwork imaged uSD)... you would just put the file on the uSD and boot it in the nook... install zip from card... select the file and let it flash... when its done flashin... power on holding n... allow it to do its thing and you'd be at factory 1.4.1.
The benefit of this method was you didn't have to flash to original and update... but since 1.4.2 has come out it would have to update anyway.

Harrybub... when I do the three finger way, my nook brings up ClockworkMod Recovery v3.2.0.1
I need to reset factory settings, but this came up two times that I was successful with the 8 interrupted boot.
The third time, I just chose the (wipe data/factory reset) in Clockword Mod recovery. Now it just boots up into recovery
Help?

gryphon101 said:
Harrybub... when I do the three finger way, my nook brings up ClockworkMod Recovery v3.2.0.1
I need to reset factory settings, but this came up two times that I was successful with the 8 interrupted boot.
The third time, I just chose the (wipe data/factory reset) in Clockword Mod recovery. Now it just boots up into recovery
Help?
Click to expand...
Click to collapse
See the post right above your's.

I just started over, found I had a corrupted cwm, maybe... Also had Rom zip and GAPPs zip on the same card. Redid everything using cwm image on one card, then zips on a separate card. That did it!

gryphon101 said:
I just started over, found I had a corrupted cwm, maybe... Also had Rom zip and GAPPs zip on the same card. Redid everything using cwm image on one card, then zips on a separate card. That did it!
Click to expand...
Click to collapse
Just an FYI... having both zips on the card is not an issue... common practice is to have them both, along with other zips on the CWM bootable uSD... you just have to make sure of what zip you are installing from uSD.