yashsingh1/xdaforums huggingface dataset:
[Desire HD Q&A, Help & Troubleshooting] kgulruh:
I tried many threads and find no answer to my question.

On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.

1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.

2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?

It flashed cwm perfectly. But I am not shure about flashing radios and stuff.

Thanks for the links to the Leedroid cwm version
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........

Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash :eek:. Also ensure notebook & phone batteries have near full charge.

Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.

:confused::confused:...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux

Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)

To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.

If you want to use CMD:

Place image inside SDK folder where fastboot & adb.exe are located.

Rename it to radio.img (unless you like to type the whole name again)

CMD type: " fastboot flash radio radio.img", then

"fastboot reboot"

I am not too sure about Linux PCs, always been Windows until Android.
[Desire HD Q&A, Help & Troubleshooting] SERGI.3210:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...

this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
You'll have to post that question to the ROM Manager Koush.

If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img

OR

CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
[Desire HD Q&A, Help & Troubleshooting] superstick1:
Thanks UpInTheAir

I'll try it later tonight. Guess I will try to manually flash them.

It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?

I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
If you are referring to the "tool" as in the CMD (Command Prompt)?

If this is what you mean, the answer is Yes & Yes.

Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
[Desire HD Q&A, Help & Troubleshooting] superstick1:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(

This is what I do

1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"

2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"

and it pops up that error. =/
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
Ensure Fastboot is OFF & USB debugging ON in phone settings

When in FASTBOOT, does it say FASTBOOT USB when phone is connected?

Did you test Fastboot communication by command "fastboot devices"?

Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.

Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")

Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
[Desire HD Q&A, Help & Troubleshooting] superstick1:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings

Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^

2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?

How do I check this? =/

3. Did you test Fastboot communication by command "fastboot devices"?

Same as the above. How do I check this?

4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.

Yes. Checked.

5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")

Tried. Did not work. Same error coming out.

I try flashing other recovery such as 3.0.2.6 but still the same error.
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
1. Mine works fine with usb debugging on & fastboot off.

2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.

3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"

If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
[Desire HD Q&A, Help & Troubleshooting] superstick1:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.

I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.

Anyway thanks a lot ya. ;)
[Desire HD Q&A, Help & Troubleshooting] SERGI.3210:
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.

Certainly .... which is the meaning of "koush"???:o
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.

3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.;)

Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8

I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.

View attachment 579282

View attachment 579283

Installation:

1. Power off your DHD

2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.

3. Plug-in the USB cable. (FASTBOOT USB)

4. Extract xxxx.zip

5. Double click on install-recovery-windows.bat if you're using windows,

execute install-recovery-linux.sh if you're on linux

or install-recovery-mac.sh if MacOSX.

6. Done! The device will be automatically rebooted.

7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.

I tested the windows commands and worked perfect :D Linux should too!!

I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
[Desire HD Q&A, Help & Troubleshooting] superstick1:
Thanks UpInTheAir!

I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.

Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?

Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.

What happen here? Its getting complex. =/
[Desire HD Q&A, Help & Troubleshooting] kgulruh:
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.

For me typing in linux is better then knowing nothing in windows:D
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).

Try that way.
[Desire HD Q&A, Help & Troubleshooting] superstick1:
Ok, flashing ROMs manually is my first time doing it. And it seems that it replaced my stock ROM with ARHD's ROM already. But all the apps, personalisation is all still appears based on how the stock ROM is.

Looks like I have to full wipe it first before I flash any ROMs. Hmm.
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
Search for a flashable zip, "tool xda HTC desire hd full wipe".

Full wipe 1.2 for cwm 2.xxx

Full wipe 1.3 for cwm 3.xxx

Formats various partitions in one go. Does not wipe sdcard.

There is also a Easy Upgrade zip as well.

Would give you the link, but not at pc. Just Google it.
[Desire HD Q&A, Help & Troubleshooting] superstick1:
I've managed to flash them. Now everything is back to normal. Im sticking with LeeDrOid. Lol.

Once again, thanks UpInTheAir. x)
[Desire HD Q&A, Help & Troubleshooting] UpInTheAir:
No worries at all. It's just a learning curve. I'm still everyday.
[Nook Color General] Tool Belt:
B&N Update Next Week?

Just showing you the link:

http://androidos.in/2011/04/nook-co...-update-on-april-25-froyo-incoming-with-apps/
[Nook Color General] Paul22000:
Doubt it. Would be all over the internet if it was (Engadget etc). Seems like a shady site.
[Nook Color General] bigdaddyrobb:
I saw the same thread earlier today on the Barnes and Noble site.

I cannot post the link but title of the thread is "Monday it is"
[Nook Color General] lafester:
http://bookclubs.barnesandnoble.com/t5/NOOKcolor-General-Discussion/Monday-it-is/td-p/970372
[Nook Color General] Larry94:
Look at post #6 in that thread. "Go to B&N if you need help with anything." Yeah right im going to make a trip to Barnes and Noble and tell a representative that i don't fully understand how to use the new update LOL.
[Nook Color General] rigy73:
I too heard the chatter, it might actually be monday. Let's hope they come out with a newer kernel. The one we have is kind of getting old.
[Nook Color General] nategator:
I just hope the update contains something of use to the community that it doesn't already know -- like being able to use Bluetooth beyond a couple of feet.
[Nook Color General] doncaruana:
Just as interesting as the date is the content. If you keep reading that thread, you get a link to another thread where they say a manager actually saw (and shared) the update: She shared what she saw....WOW. Flash, new PDF and lots of aps.

Monday will be interesting: if the updates actually comes, will it manage to get past the OTA blocking?
[Nook Color General] eneloop:
Just calm down and relax,if you're looking on the B&N Community board there's daily some folks that fool around those update.
[Nook Color General] Larry94:
Does anyone know if this update could maybe increase app compatibilty due to an official update to froyo such as Homerun battle when we get it rooted with android market and/or sideloading? Cause that would be the only reason I'd have for updating.
[Nook Color General] CamelToeJoe:
It will be interesting
[Nook Color General] skeeterpro:
Agree. It will be what it will be. But to be on the safe side, I've flashed back to stock 1.1.0 for a couple people at work who rooted. That should allow the OTA (whatever it will be) to install as BN designs.

And so it goes....
[Nook Color General] EnTg888:
I really hope it's 2.2 and not 2.1 with an app store. I wonder if they're going to release a new kernel (and its source)? That would really help out the CM7 people...
[Nook Color General] buzz killington:
I would think the likelihood of an update this week is very high. Remember they're taking on a major retail partner in Staples starting May 1st. If they have an update, they would want to make sure that it's finished before Staples start selling them, it'd make things a lot easier for their new partner.
[Nook Color General] Paul22000:
Where did you hear/read this?
[Nook Color General] rudegus:
I think one of the most exciting features of the upcoming update will be an official froyo build that will have full aceess to all of the internal storage. That and an overclocked kernel plus being rooted will be pretty damn awesome in my opinion. I can't wait, time to backup my nook and revert to stock in preparation.
[Nook Color General] fpga_guy:
BN

Straight from a BN press release

http://www.barnesandnobleinc.com/pr...aples_announces_plans_to_sell_nook_color.html

Also the fiscal year for BN ends on 4/30. There may be things you want announced before year end or if it is bad news after year end. The NC product distribution strategy is beginning to resemble the Apple one. However, BN does not have its app developer support strategy in place.
[Nook Color General] xxiworld:
Auto Update came through today (despite devicemanager editing and OTA certs renaming)

I was using my nook today, when all of a sudden a B&N permissions dialog screen popped up (specifically, it said something like "permissions error, rebooting". Then it rebooted into clockwork(???) which formated my data and cache partitions, pulled up a list of errors trying to change other things (possibly because I am rooted with an OC kernel?), and then rebooted.

Despite this, it managed to reboot into stock. I didn't get any further than the setup, before I decided to flash my nandroid backup. I'm actually kind of regretting that a bit now, since it would have been interesting to see what the new stock was like (presuming it worked correctly), but ultimately, I think it is probably best to wait for XDA to tell me what to do about updating or otherwise. In the meantime I'll be leaving my wifi off.

I've been debating upgrading to CM7, but the sleep / battery issue has prevented me. If this update really is froyo, and the devs here get it rooted nicely soon, I may not make that step at all, or at the least I may be able to wait much longer for the sleep issue to be fixed.

Also of interest is the fact that I had renamed the OTA certs and used sqlite editor to tweak the devicemanager.db file. I don't recall if I had spoofed the build.prop or not. But this seems to imply that we don't really have any reliable way of preventing OTA updates at this point, other than installing a completely new rom. That alone might be enough to warrant switching to CM7. I'm so confused! ;)
[Nook Color General] danbutter:
I'll have to grab my NC and turn it off and take out the sd card.

I don't think I've turned it off for a couple of weeks...running CM7.

Nothing new showing up here yet:

http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
[Nook Color General] xxiworld:
CM7 won't auto-update, will it? I was running stock 1.0 rooted (and now that I've flashed my nandroid backup, I am again, though I lost two weeks worth of tweaking).
[Nook Color General] japzone:
1) I agree that Updates should be Voluntary; maybe with an option in the settings menu and a Notification that an Update is available. It makes more sense and the Update should go much smoother. I had such a pain Updating Stock to 1.2. I would put the Update on the Nook and it would delete the file without Updating. In the end I had to do a Factory Reset back to 1.0 in order for it to recognize the Update.

2) The reason some apps cost $$ in the B&N Store and don't in Market is because the Market Apps have Ads but B&N don't want any Ad powered Apps in their store; so Devs have to charge up front instead of trickling payment off of Ads.

____________________________________________________

Sent from NookColor CM7 using Tapatalk
[Nook Color General] botossi:
xxiworld, what happened with you was not an update... but a simple glitch... all of us that used or use Autonooted versions now or then go thru it.... with me happened once when I installed Laucher Pro... Ii would suggest you to change the thread title before it raises a lot of question about the so expected 1.2 update !!! good luck with your restore!
[Nook Color General] xdajunkman:
CM7 will not auto-update. Running a custom ROM is the only way to know for sure that you will not receive B&N updates - the other tricks that were tried (build.prop edit, file renaming, DB tinkering) are only experiments until a new update is actually released and we see if they worked. It appears from the experience above that they may not have actually worked.

The problem with waiting for the devs to root the new firmware is that the next time B&N decides to release a minor update, you will be back at stock and waiting for another re-root. Who knows how oftern mior updates and firmware fixes will be pushed out by B&N - I expect that there will be a few after this major update is pushed and users start complaining of a few bugs that need fixing.

It is tempting to revert to stock and wait for the new stock root method, but it means that your device will be a ticking bomb waiting to revert back to stock with any future random B&N update. I will be sticking with CM7 from here on - the stable release has been just that - rock stable - for me and the vast majority of users here that don't want to tinker with the experimental kernels and nightly builds. I am quite sure that the new stock OS will not have any critical functionality that I don't have with CM7. Unless you consider the Nook children's books and magazines critical - though similar apps and services are available through from providers other than B&N.
[Nook Color General] xxiworld:
Hmm, interesting. Thanks. I never heard about spontaneous restores to stock before. And weren't we expecting a possible OTA update tomorrow anyway? I thought I had just gotten it a bit early. I hadn't done anything like install a new application before this happened. It was seemingly spontaneous. It is possible this was the 1.1 update not the 1.2 update, since I was on 1.0. But I've gone for months without the 1.1 update happening, and it seems to be a large coincidence if it happened now. Maybe they are doing something to prepare 1.0 people for the 1.2 update?

Unfortunately, I can't confirm one way or another, since I flashed my nandroid backup immediately. I just need to re-install dalgrin's more stable 3-31 OC kernel rather than the older version I had in this old backup.

It would be useful to know, though, because if this is just a glitch, I can turn my Wifi back on. I suppose, since I know the nandroid backup works fine, I could go ahead and turn it on and see if it re-auto updates again.

As for re-titling the thread, I don't seem to be able to do that.
[Nook Color General] xxiworld:
No, but I feel the ability for the nook to sleep is somewhat critical to me. YMMV. I'm really torn about whether to go to CM7 or not. Once the sleep issue is fixed, it will be a no-brainer, but for now . . .
[Nook Color General] dalingrin:
I'm probably biased but I don't think 2 day battery life is that bad. Only standby/sleep battery life should be affected.
[Nook Color General] japzone:
Just run CM7 from a 4gb Class6 MicroSD like me. I haven't even rooted my stock. You won't have to worry about updates and you still get access to B&N stuff (AppStore) when they come out, but you also have CM7 to work with and screw up as many times as you want(Making image backups with DD is easy).

As far as the 1.2 update, it's not here yet. I left my Stock on a few hours yesterday and didn't receive any update, and B&N Nook Color FAQ still has the 1.1 update.

Come On B&N!! I want my Appstore!!

____________________________________________________

Sent from Nookie Froyo using Tapatalk
[Nook Color General] xxiworld:
No disrespect intended at all, Dalingrin. I hugely appreciate the work you put in, and I understand if the sleep issue is proving difficult to fix. I tried CM7 on an SD card and loved it, at least until I started getting FC errors all over the place (which I put down to my Transcend SD card being shoddy, despite being supposedly class 6). I'm sorely tempted to go to CM7 on emmc, as it really is a huge improvement. I also use your OC kernel on eclair, and really appreciate that as well.

But I use my nook pretty heavily, and only get 2-3 days battery life running stock 1.0. I am a bit nervous about what the battery life would be if it was running down when I *wasn't* using it, too. Also, I listen to podcasts with the nook when I go to sleep. With stock, the nook just goes to sleep on its own as soon as the podcast is done playing and the battery is still fine in the morning. If it didn't sleep, I would need to leave it on the charger at night, and I don't know how good that would be for the long-term battery life.

I'm not complaining, or trying to rush the developers at all, just debating whether or not CM7 is currently worth the tradeoffs for me. I don't want to buy *another* SD card hoping I get one that works reliably, and replacing the stock completely is a big step. For others, I'm sure it is very much worth it, and I may decide it is worth it for me, too, but I'm undecided.

To bring things back on topic, the inability to stop auto-updates would be a major push towards CM7. Given no-one else seems to have received an update yet, I'm willing to believe my experience may have been a glitch, rather than an update to 1.2 - though it seems very odd to have a glitch that involves a message about permissions from B&N, formats your data and cache, and un-roots your nook. Since I was on 1.0, it may also well have just been an OTA update to 1.1.

Whether this was a genuine 1.2 update or just a very, very late 1.1 update (and again, I'm kicking myself for going to nandroid backup right away before finding out one way or another), it does seem to imply that our current methods of blocking OTA updates may be inadequate, which is a concern.
[Nook Color General] poofyhairguy:
http://www.pdfdevices.com/nook-color-to-get-froyo-update-and-app-store/
[Nook Color General] japzone:
Fingures crossed for update. I'm hoping for a Netflix app :D Hey, a guy can dream ;)

I haven't rooted my stock because I want to see what B&N does. Besides worrying about OTA screwing up my Setup would be a pain. I just run CM7 from a 4gb Class 6 MicroSD. I can screw around as much as I want and not have to worry. Makimg Images with DD is SO easy.

____________________________________________________

Sent from NookColor CM7 using Tapatalk
[Nook Color General] xxiworld:
Provided you happen to get an SD card that runs CM7 reliably. I bought two Transcend 8GB class 6 cards based on recommendations here, and couldn't get nookie-froyo or CM7 to run off of either SD without tons of FC errors.
[Nook Color General] Gin1212:
Always buy sandisk, even kingston can be a gamble.