For Windows 32-bit (I did not test): x86.rar
For Windows 64-bit (This is what I used): x64.rar
The ROM: blaze21.nb0
Run setup.exe, be sure to grant permission to install drivers in any pop up windows you get during install.
Connect your phone to your PC, open the SUT tool and point it at the ROM. Click next and your phone will reboot.
Important: You'll see an error on your phone when it comes back up, but don't touch anything. After a minute or two the screen will go black and then you'll see some small white text. This means things are going well. If you never see the white text and the SUT tool gives an error, the fix is disconnecting your phone from your PC, rebooting your phone into FTM mode (hold Volume Up, Volume Down and the Power Button during boot), and then removing the battery to get back out of FTM mode. Connect the phone to your PC, turn it back on, and try running the SUT tool again. It should work this time.
After about 10 minutes and the phone rebooting three or four times, the SUT tool will inform you that all is well and the update has been applied.
Now that you're up and running with 2.1, let's root. Grab Universal Androot and run. It's that simple. I'm told that Androot also works for rooting the new Motorola Milestone aka Motorola Motoroi.
So is it possible to upgrade to 2.1 without rooting??
ReplyDeleteYeah. Just don't do the last step (UNiversal Androot) lol.
ReplyDeleteYou're my hero lol.. Thank you Shawn, very much appreciated!
ReplyDeleteLoving the new setup man! Sorry, I'm super stoked here. How did you get the file?? :)
ReplyDeleteI wanted to tell everyone that my files are all still there after installing the new ROM. They didn't get wiped out. This version is way~~ more stable for me, even my dialer seems to act better now, more responsive.
ReplyDeleteThat's great to hear Brian. I agree everything seems better, including the built in keyboard (even though I'm probably putting Swype back on there). The only app I've had trouble with is Key Ring Reward Cards (crashes upon opening).
ReplyDeleteI can't say how I got the file :)
Now we just need to get 2.2 right, lol.
ReplyDeleteHaha yea. Another project for another day. In fact, if any of you have an extra Blaze you don't mind possibly bricking, I have an idea how to get the 2.1 update.zip from this nb0.
ReplyDeletesean, i said thanks for the original root, and i wanna thank you now for this update. AMAZING.
ReplyDeleteSO much better. i also didn't lose any of my info when i updated (i havent re-rooted yet).
THANK YOU again.
Worked great for me, I'm glad we finally have 2.1! Thanks Sean!
ReplyDeleteLive wallpapers seem to not work for me though, anyone else have that problem?
Yeah, as in you install a live wallpaper and don't see it in the wallpapers section? I also have that problem. But having lived without live wallpapers this long, I don't know that I really care :)
ReplyDeleteOh well, I'm happy enough to have all of the other features!
ReplyDeleteWorking with the developers to fix Swype and Key Ring Rewards Cards. If FoxyRing support gets back to me I'll try and help them too. Those three apps are all broken for me.
ReplyDeleteso, is there a linux utility to flash this? I'd rather not break out a VM for this.
ReplyDeleteNo idea. If you have a Blaze to brick, I could get you the update.zip which would theoretically not need the Windows tool.
ReplyDeletewell, I don't have one to brick...this one's all I got. :) If you think it's safer, I'll just connect it to my win7 virtual machine...but I would have thought android updates were only a simple flash to phone and a multiplatform tool would have arisen. If it's not too much work, you could still post a update.zip, though. I'm up for experimenting, just as long as it's not permanent side-effects.
ReplyDeleteYeah as soon as I have it I'll post it. No ETA...depends when someone donates a Blaze.
ReplyDeleteThis doesn't look good. :(
ReplyDeletehttp://imagebin.ca/view/V2vDhp_x.html
It seems I won't be doing an update, I guess.
Hopefully that didn't brick it! The SCSI error is likely related to your VM (VMs use faux SCSI for their hard drives). I'd double check the USB pass through settings, maybe screw around with the hard drive settings if USB looks right.
ReplyDeleteI hope it didn't. It never rebooted, so it seems to still be working fine for now. I didn't see many settings for usb in VirtualBox, so I'm going to try and install something quick in vmware to see if it has better usb support.
ReplyDeletevmware gave the same error. I did also notice that both had a "unknown" usb device listen in device manager. I guess I'll wait for a linux tool or for the official upgrade.
ReplyDeleteI upgraded my Blaze as per the straightforward procedure and everything worked great! I noticed right off that the gallery and music player apps are not included. The default gallery app (3d Gallery) is in the market, but apparently not the default music app. Of course there are many other music and media players there. Hopefully this is not the final build that CBW will be releasing.
ReplyDeleteI reinstalled all of my apps, no problems, but when I tried to install the Fennec beta (Firefox for Android), it would not start at all.
I can't say that 2.1 seems any faster, but certainly not slower either.
Yeah, it's also missing 1.6's Voice Notes. You're right that this does not include everything CBW will release with their final 2.1 version, if they release it. The 1.6 Music app never worked well for me, so I use Cubed: http://www.droid-life.com/2010/03/23/android-quick-app-3-or-cubed-music-player/
ReplyDeleteHey, I tried to upgrade but it didnt work. I got the error screen(I believe) it was multi colored. Then Im not sure if I saw the phone reboot, but I did get 4 white lines of text. After a few more minutes, My SUT tool said there was an error(dont remember the error though). I rebooted in ftm mode, pulled the battery, and when I turned the phone back on, I got the same multi-colored error screen I saw when I started updating to 2.1. Chose the recovery option using the ball and selected that. Nothing happened(so it seemed) so I just pulled the battery. restarted the phone like normal, and the phone seems fine. I'm afraid to try it again. Any suggestions??? Btw I used the x86rar.
ReplyDeleteSame error I got the first time on the 2nd try.
ReplyDeleteError Code: 0xf626
(Qe,OEM,AMSS,APPSBT,aBOOT,aSYS,aRCU,aSPL,aHIP) fail,
Error=Qpd_Error_Armprg_hello_Tbuffer(0xf626)
I dont think I will give it a 3rd try.
I do get an error screen, goes black, then I get the 4 lines of white text, But after about 3-5 mins I get the above error.
Thanks
From what I've read on the forums
ReplyDelete1) Don't use a VM
2) Make sure the drivers install right (drivers are installed when SUT is installed)
3) Make sure you have a couple hundred MB free on your SD card.
Using xp 32bit
ReplyDeleteSUT program installed( I assume right)
I accepted all prompts on the install
I had nothing on the sd card except what came with the brand new phone.
Kids dont seem to be upset with 1.6. I guess I can hope(not holding my breath) that CBT will provide the an update officially.
They're supposed to... :)
ReplyDeleteThis is CBW we are talking about ;)
ReplyDeleteany word on getting swype to work? That's the only thing holding me back from upgrading at this point.
ReplyDeleteYou can follow the progress at http://forum.swype.com/showthread.php?1085-The-application-swype-has-stopped-unexpectedly
ReplyDeleteYour the bomb sean, got a 2.1 rooted blaze and couldnt be much happier! Fixed alot of issues i was having! Question? is there a terminal application that works with the blaze keyboard?
ReplyDeleteYes, on 2.1 search the market for Terminal Emulator. It will be the highest ranked one. It works great.
ReplyDeleteThanks sean, one other question? is there still an issue with the cpu, mine still reads 480 instead of 600mhz.
ReplyDeleteNot sure, when I was using a CPU widget on 1.6 it would jump between 480 and 600 depending on demand. You might want to download a CPU overclock widget and see if it can help.
ReplyDeleteyeah i did that and it doesnt seem to do anything, im using setcpu but i can't get the cpu to clock over 480mhz.
ReplyDeletereguardless this is better than the 1.6 we had, I hope the CBW final release gives us full function.
ReplyDelete1) i am using the "Screebl" app to 'fix' the screen (i have it set to force the screen to stay on while im making calls).
ReplyDelete2) from androidcommunity.com: ""For SetCPU, when it says to Auto Detect for the cpu, go to show other frequencies and choose MSM7x27. Mine also still says 480, but when you go into the program, it shows 600.""
i haven't tried #2 yet myself though.
Yo update works fine, besides my calibration. For some reason I have to lean it to the right side to get it to switch its orientation. So instead of it switching when I hold it side ways I have to lean it away from me and then it'll switch.
ReplyDeleteAny help? I've tried recalibrating and it doesn't work.
It would appear that screebl causes that, and running screebl fixes it. But if you uninstall screebl it breaks the orientation lock.
ReplyDeleteRunning it didn't fix it, what settings should I have? How can I reset the e compass manually because whenever screebl tried to the moment I move my phone it says finished. What do you mean it breaks the orientation lock?
ReplyDeleteNevermind, I got it fixed. Thanks Sean, you rock!
ReplyDeleteI'm having issues with messages and pictures. It's showing the picture as being attached when I look a at all threads but it doesn't show it inside the thread, also it's switching messages around inside threads. If I scroll to the top and back down, instead of there being the last message sent it's the first or second message of the thread. Any help? Ideas?
ReplyDeleteNot sure, I assume you're talking about MMS picture messaging but so far mine has been in chronological order by thread.
ReplyDeleteI was just looking at this:
ReplyDeletehttp://translate.google.com/translate?hl=en&sl=th&u=http://www.pdamobiz.com/forum/pdaforum_posts.asp%3FTID%3D334435%26utm_source%3Dtwitterfeed%26utm_medium%3Dtwitter&prev=/search%3Fq%3Dapanda%2B2.1%2Brom%26hl%3Den%26prmd%3Dv&rurl=translate.google.com
and was curious to ask if you think putting the nb0 on the sd card and booting into FTM would provide an update to the phone.
Nope, already tried. What the SUT tool does is convert the nb0 to the proper update.zip format, copies it to the SD card, and deletes it when it's done. That's why I need a spare Blaze to possibly brick by stopping the process midway to get at the update.zip before it's deleted.
ReplyDeleteAt what point would it need to be stopped? If the process only needs to start, I can try hooking it up by virtual machine again.(which didn't flash the phone but at least started doing something, possibly converting the image.) Would this file be found in what folder?
ReplyDeleteI'm sure it does store it somewhere, maybe try searching %temp% for update.zip while it's going.
ReplyDeleteThis is all that was made by the SUT tool in Temp before the error.
ReplyDeletehttp://www.box.net/shared/uy78vkhkey
No update.zip. Are these files any help or is there somewhere else to check?
Nope, no help...the update.zip will be around 150MB. I have no idea if it even creates it locally before copying to SD card. It could just put it in RAM and copy directly from there.
ReplyDeleteThanks! Sean! Works great for me! This is great achievement! I was trying to get the official 2.1 release from Apanda to work but for some reason some Apps wouldn't work. Then from the Apanda's forum someone directed me to your site.
ReplyDeleteA week ago I called CBW and the rep said I was the FIRST to request an Android update. This is SOOOO Cincy...
lol yea you're definitely not the first to request the update from Cinci, you can check prior comments on my Blaze posts to see other people calling CBW/whoever and asking. Since CBW tech support is in the Philippines now, it might be the first anyone out there ever heard of Android phones needing updates lol
ReplyDeleteI keep getting this error:(
ReplyDeletehttp://www.box.net/shared/uy78vkhkey
I tried putting it into the FTM mode and plugging it back in, but it didn't work. Any help please email austin.butikofer@yahoo.com
^Oops, the link was supposed to be http://i182.photobucket.com/albums/x188/mylesc2007/Untitled-5.png
ReplyDeletesorry!
The only way I know to get past that error is the FTM mode trick...maybe try rebooting your computer too?
ReplyDeleteIpodfreak
ReplyDeleteThat was the same error I got, FTM mode didn't work for me. I tried it 2x getting that same error both times. I used the x86.rar(32bit). After two fails I stoped because I didnt want to brick the phone.
Is anyone having issues with the camera? Mine freezes and force closes on launch now. Anyone know of any apps that can cause this?
ReplyDeleteI just tested mine for you, and it works perfectly. I even still have my pictures that I took when I had 1.6 on there.
ReplyDeleteI'm thinking maybe some people don't have proper permissions on their PCs or the drivers weren't installed correctly, or both..
The only issue I've noticed is that the LED apps that worked before don't now. I actually was able to get the Moto Torch LED app semi working. I'm perfectly happy with that though, it will get me by.
The issue with it is that when you turn the LED on it won't turn off until you hit the strobe on button then turn the strobe back off, then it goes off.. LOL.
Now, I'm getting an "Error Code 0X4000
ReplyDeleteMessage: Download fail
Error= DEVICE NOT CONFIGURE (0X4000)...
Any help? I've done the FTM trick multiple times, and rebooted both the phone and computer...
Just checked CBT facebook page/wall and they answered a question asked to them saying they will be annoucing an upgrade for the blaze soon to 2.1
ReplyDeleteThat's very exciting, hopefully it will fix the new issues with various apps. URL for official update news: http://www.cincinnatibell.com/blaze/upgrade/
ReplyDeleteLooks like that conversation I had with the manager awhile back actually did some good!! I say round of a applause for them for listening seriously..
ReplyDeleteHey seab the camera and camcorder has stopped working all together. it instantly freezes and force closes the moment I click on it. the hardware button doesn't even work. I don't know why and I can't seem to fix it. I've tried reinstalling the 2.1 rom with no success of fixing it. Does anyone have a back up of the original rom that came on the blaze?
ReplyDeleteAlso the guy at cincinnati bell said the update will be released in a few weeks. He also said those without the original rom won't be able to get it, that it'll just fail when trying. So we need to get the original 1.6
ReplyDeleteYou can just do a restore I think, right Sean? Besides, I think you're having another issue.
ReplyDeleteI told you this above but you must not have read my post....................... In order to learn you have to listen.
They never shared the 1.6 image with us. The 2.1 image here is exactly what's going out from CBW except for any special CBW apps. Any problems encountered in this image will not be fixed in the CBW official release - CBW doesn't know how to fix them. If your camera isn't working, take your phone back to a retail store and return it. That's what Wireless Equipment Plans are for.
ReplyDeleteI tried taking it back to the store. They refuse to do anything with it unless it has the original rom and it's unrooted. They didn't even have the tools to wipe it back to 1.6. I'm just letting you all know what I was told by them in person. He said they wouldn't work on it since it's not the 1.6 rom and said the update wouldn't take if you've already upgraded.
ReplyDeleteFew store reps know what root is. The distribution company in Florida handles the wiping back to 1.6, that's why we tried asking them for the image. You can either 1) take it to a different store or 2) wait until all Blazes have 2.1 and then return it. To unroot your phone, uninstall Universal Androot.
ReplyDeletecould you give me the number for the florida distribution company
ReplyDeleteApparently, I am clueless. I tried upgrading but I don't know how to point the SUT to the rom file. I installed, it runs and then nothing happens. Any help would be greatly appreciated.
ReplyDeleteJoAnne;
ReplyDeleteIf I understand what you are asking, is you dont know how to get the blaze21.nb0 file to your new SUT tool. If so, alll you need is to browse thru the SUT to where you downloaded the file. The little box with 3 dots on it, is the browse button. just use that to locate where you downloaded the file to. Hope this helps
"Connect your phone to your PC, open the SUT tool and point it at the ROM" This is what I don't understand. I downloaded, unzipped, and put the ROM file all in 1 folder. I install the SUT and it does a few things, then nothing. Do I need to Root first? I just got the phone.
ReplyDeleteThanks again.
JoAnne
(407) 857-3737 is the number for Q1W the distribution company. Their support email is RMA@q1w.net.
ReplyDeleteAfter installing the SUT tool, you need to open it. Start-All Programs-SUT L3-SUT L3. Click next until you're prompted to browse for the ROM file, then follow pmac_01's instructions.
ugg so i have installed the updated 2.1 which most likely is the final approved from CBT but I cant get the Androot 1.6.1 to root my phone. I get a failed ! NO -- Fu goo --- error any ideas? I must say the updated version of the 2.1 for the Blaze is alot nicer then the original 2.1 trial update from CBT. Live Wallpaper actually works on this one. But anyways would like some help on the rooting if you can.
ReplyDeleteNo idea, send over your new nb0 or update.zip.
ReplyDeleteDamn trolls, lol.
ReplyDeletecdrenty, or anyone, where can I get the updated 2.1 at? I would love for my live wallpaper to work!!! Thanks!!!
ReplyDeleteAny chance of a workaround for the whole "you gotta have the original rom to update" thing
ReplyDeleteYou talking about the official update? I'll post it here once I test it and root it. Hopefully next week.
ReplyDeleteMan, still nothing official from Cincinnati Bell at www.cincinnatibell.com/blaze/upgrade
ReplyDeleteCan't afford the pricey milestone, hopefully they will be getting new android phones in soon? There new Huawei U8100 is probably the biggest joke I've seen, 2.8 screen and resistive. Totally not worth $99 with rebate.
Yeah, I was. That's great thanks a lot! Any idea of what the differences are between the official and the one you have up here now?
ReplyDeleteNot really...for sure, live wallpapers work and Androot doesn't. I would hope they fixed the Chinese language errors that happen secretly in the background that might be causing some apps not to work with the old 2.1 image.
ReplyDelete3 new Rom 2.1 mods for BLAZE:
ReplyDeletebbarao Mod 2.0: http://boston-mania.blogspot.com/2010/10/bbarao-optimus-21-rom-mod2-root-600mhz.html
TWGoGo SOEZ Mod 1.0: http://boston-mania.blogspot.com/2010/10/testtelmod-is-now-twgogo-soez10.html
CMLeclair Mod 1.1: http://boston-mania.blogspot.com/2010/10/update-cmleclair-11.html
Anyone try these? Any issuse with imei problems or other issues?
ReplyDeleteI did twgogo mod cpu runs 600 the root apk on this page works live wallpapers work alot better rom in general. just unpacked twgogosoeb600.nb0 ran the update tool on this page.every thing was still there from seans 2.1 rom apps numbers bookmarks ect everything more responsive thanks sean and termoflua
ReplyDeletetwgo mod doesn't like Pandora music app, fcs on launch. lw work well, only 3 screens on this though. gonna tinker around and then try the cml mod.
ReplyDeleteLooks like the xt720 might be getting Android 2.2 eventually. http://pastebin.com/5k6vU4DP
ReplyDeleteGuess I will be buying this soon.
How's the updated 2.1 coming? And do you think having a Boston ROM will cause any problems?
ReplyDeleteanyone heard when this is coming for sure? We're getting fairly deep into October:
ReplyDeletewww.cincinnatibell.com/blaze/upgrade
This is CBW, the gears turn slowly, and some of those gears are missing teeth.
ReplyDeleteJust bought the Motorola Milestone XT720 today, if anyone has found any site that has gotten 2.2 working on it please let me know. Already have it rooted but custom roms seem to be blocked.
ReplyDeleteCustom ROMs need either a tool (like the Blaze's SUT) or recovery mode to be installed. Grab the ROM, drop its update.zip onto your SD card, and reboot your phone into recovery mode to install. It's a special key combo held at power on that will get you into recovery mode, try Googling to discover it.
ReplyDeleteHow's the testing on the updated 2.1 going?
ReplyDeleteHey sean, i have a blaze that i cracked the lower portion of the screen on, it still works great though. Sadly everyone im switching to sprint as it is time to get my own plan and get off my parents plan. Im staying android all the way, going to get evo 4g! As i was saying sean if you would like the phone for testing, ill sell it pretty cheap. I wanna still help as much as i can!
ReplyDeleteThanks Deven, the EVO 4G is definitely Sprint's best choice. I'm moving out of the area next week and probably also switching carriers depending on my new job, so I might not mind bricking my own Blaze soon. I'll let you know if I need a second.
ReplyDeleteright on man! Where you headed? i noticed you went to school in terre haute. Im currently living in terre haute going to ISU.
ReplyDeletefinally found a 2.1 rom i like http://www.easy-share.com/1912587091/firetrapSugar.rar live wallpapers 5 screens custom keyboard prerooted tried every 2.1 rom available this is the best by far.pandora1.5 from market forces close so get 1.4 from here http://www.filestube.com/6OxlhtpmipjSVeeQSJeCcG/signedcom-pandora-android-half-transparent.html just unpack nb0 from rar to desktop run seans update tool select new rom done gonna stick with this one till a 2.2 rom shows up
ReplyDeleteHi Sean --
ReplyDeleteThanks for the upgrade -- it worked flawlessly. One question...after the upgrade, I can't find my previously paid apps (e.g. SlingPlayer) in Marketplace. I'm assuming the new ROM isn't approved by Google, is there a workaround or am I out of luck?
It's likely that the app isn't approved for CBT's market code at 2.1 level. Many apps weren't even approved at 1.6 level. Try MarketEnabler to switch to a different market and see if it shows then.
ReplyDeleteI upgraded to the 2.1 everything works awesome...I do have a problem with the connection speed..It wont ever register 3G connection just G...I believe that is GSM...It may not even be connecting to the Edge network...I am in downtown cincinnati and the 1.6 OS would connect just fine...anybody got an idea on a fix...
ReplyDeleteG is 3G (there isn't enough room in the icon for a 3), E is Edge (2.5), e or no letter is GSM (1.5-2)
ReplyDeleteThanx a bunch Sean...
ReplyDeleteCBW is very close to rolling out the official 2.1 update. I got my Blaze (which was already running the 2.1 build posted here) upgraded today. Everything seems to be working fine, the missing apps (gallery, music player, and voice notes) are back, and live wallpapers are working. Here's the odd thing...the stores are setup to upgrade Blazes using a preloaded micro-sd with the official .nb0 (yes an .nb0 file, not update.zip) file on it, and there is a problem with most if not all of the stock Blazes running 1.6 taking the update using the chip. However, my already updated and rooted Blaze took the update and was ready to go in less than 5 min. Go figure. After the update, all my apps and data were still there, as well as most of my settings except for my ringtones. All my apps seem to work, except for Universal Androot :-( . Oh, and Blazes running 2.1 out of the box are in (at least some of) the stores now.
ReplyDeleteFrank,
ReplyDeleteSo are you an employee then? Thanks for the info if you are if not then I don't see how you would be able to get it unless you know an employee there I suppose..
i just upgraded my phone at cincinnati bell, seems they do the upgrade at the store only right now. i did however get an extra copy of the nb0 file put on my sd card.... anyone interested in it just tell me where to upload it...
ReplyDeleteso can you go update your phones at cincinnati bell stores now?
ReplyDeleteTeddy I'm extremely interested, could you upload it to rapidshare or mediafire or something ;o
ReplyDeleteyes, you can update your phone at a cincinnati bell store, at least the one at northgate mall.... that is where i got mine done, however universal androot doesnt work... but it is a very good working rom, i was using firetrap sugar 1.2, which is rooted and has several very cool changes/add ons that the cincinnati bell rom don't have, but there are severaly programs that crash on start up???? like pandora, sound hound and email(exchange setup)
ReplyDeletei will upload it and put up a link in a few min!!
did the update wipe your phone?
ReplyDeletehere is the official file....
ReplyDeletehttp://rapidshare.com/files/428414063/firmware.nb0
it didnt wipe all my installed apps, it did wipe out all my settings though.
http://www.rapidshare.com/#!download|714|428414063|firmware.nb0|191065.834
ReplyDeletei've never used rapidshare, hope this link actually works
Thanks Ted! I switched from firetrap vanilla and everythings working fine. Nice and smooth, but just a little slower than firetrap
ReplyDeleteHey just wanted to let everyone know what I found out at the CBW store today. I went in because they told me they would upgrade my phone for me. They had an issue with it and I figured it was because I had it rooted but after a bit of digging the guy said they have 3 builds, A B and C. If you go into your "About Phone" you can see which you have by looking at the letter at the end of the build version. Long story short, they started working backwards for some reason so if you have a "C" build you are good to go. If you have a "B" build you might be good to go but they are still tweaking it because it does not work on all "B" builds. And if you are the lucky one like me with an "A" build, then you are SOL as they have NOT EVEN STARTED WORKING ON 2.1 FOR THE "A" BUILD.
ReplyDeleteI assume this is why I cannot upgrade my phone using the 2.1 rom here as well.
Ken, so you had trouble with firetrap also? Does anyone know the reason behind some of the apps crashing? several apps i had crashed and i can switch builds without affecting the apps so i know pandora works iwth the official build but crashes with firetrap....
ReplyDeletei also noticed that this official build is slower also, i wonder if it is stuck at 400 mhz like some of the unofficial roms were?
Didn't notice the speed difference between firetrap and the latest posted firmware. I have app crashes on the "official" build also. Soundhound is not working. Couldn't get swype to work either.
ReplyDeleteWill stick with firmware.nb0 posted by Teddy.
Would recommend to wait a bit longer for hopefully better update.
I don't think cincinnati bell is gonna bring another update for a while, the speed difference is not bad at all, i just had overclock widget set to 500-600mhz on firetrap.
ReplyDeleteAnd Ted, I think i remember reading on boston mania that all the firetrap ROMs have those app crash proplems. Also, I'm mostly sure that the cpu is limited to 480mhz on the ROM you posted. I'll probably try out CM6 if thats ever made available
And Euge, you should try out shapewriter keyboard. It got taken off the market but you can definatly find an apk on google easily. I like
ReplyDeleteThanks Ken,
ReplyDeleteBut I'm having major problems with gesture keyboards. I have tried several versions of swype, shapewriter, slideit. Neither work for me. I was really enjoying swype on my old 1.6.
Can some one post the "official" firmware.nb0 file some where other than rapid share? security everywhere I connect blocks it...
ReplyDeletethanks in advance :-)
I'll have it up soon...
ReplyDelete@milkdud2282 Very interesting. Makes sense. I wonder which build I have. I'll check when I work on the phone this week or next.
anyone have luck rooting the official 2.1 firmware? i'd like to overclock it back to 600 mhz and run barnicle wifi tether, but cant with out root.....
ReplyDeleteOn the previous build from CBT i don't think it is possible to get the clock past 480mhz, so I'm assuming the same holds true with the newer stuff. There was something on a forum afor the one in portugal about how to root their official 2.1 ROM, but n oidea if the files there would help. They seem to have a pretty good community of developers and computer machines men working on it but they ain't got nothin on ours (sean freeney) haha.
ReplyDeleteSo for what it's worth, I go the new 2.1 "Official" ROM loaded on my Blaze. Very Very Nice! the gallery rocks! Live Wallpapers! and a nicely snappy UI. I had to use some of the tools on the xda-developers BLAZE/Gigabyte G1305/Orange Boston thread. I rolled to Apanda 1.6.2 the up to the new CBW image. also by going to Apanda I blew mt IMEI and had to fix that. All in all it works. and I have taken and made calls. I even ran the factory reset tool. In My humble opinio, It is well worth it.. :-)
ReplyDeleteCan you please help me with all the steps? I don't want my phone jacked. Thanks :)
ReplyDeleteRoot for "Official" 2.1 please.
ReplyDeleteSo...there's no way,even with custom roms,for people with A builds to update their phones? Is cinci bell going to work on this soon?
ReplyDelete@eyecreate
ReplyDeleteCorrect because the SUT is not compatible. They said they would be working it once all the B builds were able to be upgraded.
If they'd use standard update.zip procedure there wouldn't be a problem...not CBW's fault, it's FoxConn's.
ReplyDeleteI have no clue what build I had, but I was having problems with SUT at first. I have tried 3 different roms, was always getting 0X4000 error on one PC. Phone would reboot and gets stuck on the boot screen. I have rebooted both phone and PC several times, tried FTM mode. Nothing worked. Always got that DEVICE not CONFIGURE (0X4000) Error in SUT.
ReplyDeleteThen I tried my other PC. Everything worked great. SUT upgrade went through with no problems. Have no clue what the deal is. Both PCs were XP 32bit, same version, same updates.
If anyone is having problems I would strongly recommend to try SUT on a different PC.
**********
ReplyDeleteGot ROOT access on "official" 2.1 using z4root v1.2.0.
**********
Update: I pulled the SD card at the end of the Flash Download Mode only to find that no update.zip exists. I can only surmise that whatever this nb0 download mode is, it bypasses creating an update.zip. Anyone have any other ideas?
ReplyDeleteI've still had no luck getting Swype to work on the "official" 2.1 image, anyone else?
ReplyDeleteI think I did update using one of the roms with no flash inserted. Don't remember exactly, but I think I did take it out.
ReplyDelete------------
Anyways,
Forget about 2.1
2.2 Froyo is Running on Cincinnati Blaze
Cyanogen Mod 6
Swype works, Soundhound works, testing continues...
Barnacle doesn't work yet.
Best thing so far!
@Eugene: You've made me excited about CM, didn't know it was already working on the Blaze. How would I go about trying it out myself?
ReplyDelete@Eugene: How did you flash yours?(get it into recovery mode)
ReplyDeleterecovery = camera + volume up + powerup
ReplyDeletewhen I do that, it just seems to sit at the cincinnati bell logo forever. I'm not sure what's going on as both other modes don't have the logo display for this long.
ReplyDeleteHere is how to load CM6 2.2 Froyo.
ReplyDeletehttp://boston-mania.blogspot.com/2010/11/cyanogenmod-6-rom-22-for-z71-nightly.html
Just follow the instructions.
It is not the final build yet, but works pretty good. Better than any 2.1 that I have used so far, including the latest "official". And you can move apps to SD! Finally.
so, according to the site, it is necessary to have 2.1 before you can update. Is this true? I still have 1.6 because I have an A build, but I don't see how that would change recovery mode not showing up unless something deep is different.
ReplyDelete@eyecreate it's volume up + volume down + power not camera. And hold all three until you see that black FTM screen.
ReplyDeleteI've gotten to that mode before to root the device, but I thought I was supposed to see the clockwork screen that would then flash the system instead of a static foxconn screen. Should I use FTM mode in a different way to achieve this?
ReplyDeleteI have used [Vol Up]+[Camera]+[Power].
ReplyDeletewould using fastboot be able to flash or does it only handle raw images? What could be causing this?
ReplyDeleteAlso, trying "adb reboot recovery" shows the same unchanging CB logo...which is what I get with the button combo Vol up+camera+power, so maybe something is wrong with the recovery image or something. Any suggestions?
ReplyDeleteJust found this nice line in my log file. Guess it explains why I don't have recovery working.
ReplyDeleteE/flash_image( 4239): error writing recovery: No space left on device
after getting some IRC help, it seems the clockwork recovery image, despite having said support for z71, will not work on my blaze. Is it possible there are multiple hardware models under the same "blaze" name?
ReplyDeleteFlashing the 2.1 from original post seems to have fixed things.
ReplyDeleteliking the 2.2 on the blaze !!!
ReplyDeleteany news if Barbacle is working on 2.2? also, Ive put the official rom on my phone, is there anything special i need to do to flash back to a non-official rom?
ReplyDeleteBarnacle works for me, and i had to switch to the old Rom and wipe all data and cache
ReplyDelete@Deven living at HTA, working at Sony. I rooted my new Evo 4G over the weekend if you need help.
ReplyDelete@Andre delete the update.zip from the SD card, reboot the phone, do a factory reset via settings menu, then try SUT tool + nb0 again.
ReplyDeleteI've got Clockwork Recovery and Cyanogen Mod running on my Blaze at 600mhz. It's smooth and fast but there are a ton of bugs, wifi likes to cut out and only a reboot seems to help or else when you go to reset wifi it freezes the phone and crashes it. Flash doesn't get along with the browser, causes it to go into a looping FC when ever you open it, uninstalling flash fixed that. Also my Carrier/Network name comes up as "Unknown" all the time but still works. There's some other bugs too but for the life of me I can't remember them right now, sorry I'm distracted. Over all I like it but I can't wait for them to fix these bugs, they're getting so bad I'm about to switch back to a more stable 2.1 rom.
ReplyDeleteSorry I had more to add but my mind has just gone blank, I'll try to get back to you later but I'm not always home and Opera doesn't like this site for some reason it never lets me select my profile to post under just reloads the page when I select it. Oh and Opera has issues too, the bar on the bottom doesn't like to come up when you call for it. You also can't set it as default.
@ Sean tried that. gets stuck at boot screen with same message... gotta remove battery to be able to restart normally. Guess I gotta go retrace my steps further to see if I didn't screw it up somewhere else.
ReplyDeleteWorks great for me. Angry Birds won't install. Barnacle seems to work great.
ReplyDeleteCan't start the new NetFront browser - says phone is unsupported.
Any idea what 'H' means in the 3G indicator (usually 'E' or 'G' when on 2.1)?
Other than that, it is responsive and battery life seems almost better than 2.1.
Angry Birds installed perfectly fine for me. Now my phone is starting to drop service but still have bars. I think it may be my phone, I'm switching over to a Droid as soon as possible or what android phone would you all suggest for games like Pocket Legends and psx, music, videos and browsing the web?
ReplyDeletehttp://www.engadget.com/2010/10/26/the-playstation-phone/
ReplyDelete2.1 is rockin! i was having those 0x4000 errors (while 1.6 i had tried flashing new recoveries to no avail and the sut tool was probably rebooting into recovery as i suspected) so i grabed seans blaze.tar.gz and used fastboot to "fastboot flash recovery mtd3-recovery" (hadnt gotten error 0x4000 again and now i'm on 2.1 thanx sean)
ReplyDeleteI keep getting an error saying that they software image file does not match with the phone software. Am I doing something wrong?
ReplyDeleteNevermind, I figured it out. The ROM didn't download completely for some reason.
ReplyDeletedoes anyone know if you can update to the Cyanogen mod 2.2 with the official 2.1 update or will i have to download sean's 2.1 update and do it through that
ReplyDeleteYes you can go 2.2 from official 2.1. See my 2.2 post for instructions.
ReplyDeleteI'm also getting stuck at the CBW screen when I boot holding the Vol Up + Camera buttons. Eyecreate seems to have gotten past this but I don't really understand what he did? Anyone have any ideas?
ReplyDelete@milkdud2282 Try pushing clockwork recovery img.
ReplyDeleteKnow where I can get it from?
ReplyDeleteTried installing it from rom manager and it worked but I still cannot boot into recovery mode. Any other suggestions?
ReplyDelete@milkdud2282 I did the same and I can't figure it out...
ReplyDeleteAnyone know if this will fix my proximity sensor, my phone won't light up for me to type in my password when i call my voice mail... have to use other phone to check my voice mail extremely annoying... cin bell basically said they can't help me....
ReplyDeleteedit... what i should ask is: does anyone know how to fix the proximity sensor
ReplyDeletethanks
Yeah...get a new phone...I had same issue, manufacturer wouldn't acknowledge the problem. Not everyone seems to have the problem. A work around is to go outside (it's somehow UV sensitive).
ReplyDeleteDuring the Updateprcess with SUT LR I become the same Errormessage like ipodfreak20oh7!
ReplyDeleteThe Message is:
"Error Code 0X4000
Message: Download fail
Error= DEVICE NOT CONFIGURE (0X4000)..."
Have anyone an idea to solve and fix this problem?