Related
I had the unofficial wm6 upgrade on my device for a while and i wanted to unlock it so i used the unlocker program provided here and i could not get past the second step it kept giving me this really long erorr every time. I downloaded the real ATT wm6 upgrade and it erorrs out after the phone resets to the color screen boot loader, i tried the SD card method and the bootloader won't boot from the card. The card is formatted in fat 32 and i downloaded the official sd card setup and also tried the cheeimg.nbh method. The phone is stuck with no ability to be flashed, i tried all the versions of wm6 on here and i get stuck at the bootloader every time nothing happens. PLEASE PLEASE can somebody help me? All I want to do is put the factory wm6 on that just came out.
I flashed using SD method but It still read v2.23 so i used the palm Updater, same thing with me it would get to boot loader then stop and I noticed that the Palm update program would crash, I tried several times but same thing happened. I finailly went to another PC installed AS 4.5 got that working then tried the Palm updater again (edited the payloads file) and i guess 3rd time was a charm up date took that time.
Is your device currently functioning at all or??
I would try another PC if you can run the palm updater and remember to edit the payloads.xml file.
If your going to use the Palm Updater take out the SD card and leave it out just to be safe.
vista
yeah my device works but the radio isn't right due to the unlock tool failing and whatever other error the ungrade has cuase by not finishing 5 or 6 times.... I'm using vista, but shouldn't the sd card method work? when i enter bootloading via ptt button and reset it flashes for a nano sec a white loading screen then goes to color screen and sits there, i mean it flash's by super fast you have to be watching it without blinking to see it. you think the pc update will work if i go to a win xp computer?
Dam honestly I dont think the swapping PC will help you I think the Unlock fugged up your device somehow by not finishing the unlock process.
But yes the SD method should work. Im no expert in this but i havent bricked my device yet. You may have to call att, but dont tell them you tried to unlock it nor that you have a hacked WM6. just tell them you tried to flash with the latest up date and my device get stuck...in other words LIE so they send you a new device. If you are able to get a new device from ATT I
would screw up your current one so it doesnt load WM at all so they cant check the Version on it. in any event GL.
Now your sure your SD is fat32 formatted?
format
yes i'm sure it's fat 32, i can prolly get a replacment but it will be a referbished one. Yay then it will have some other problem.... oh well thanks anyway, i shouldn't have tried to do the unlock. don't know why it didn't work everybody else says it was easy.
for sale
Know anybody that might want it, that might fix it? it works just need a radio update i guess. $120.
not off hand no, you can try ebay.
warranty
ok i got a replacement phone coming via warranty, How would i go about messing it up so it won't boot windows????
I decided to try and root my stock G1 this morning. The bootloader does not allow me to flash down to RC29. It gives the "Update Terminate" after it fully flashes it, but before it checks the flash. Then it only loads into the bootloader and stops.
However i just successfully flashed to RC30. None of the guides on here specify that I had to load another spl or bootloader first.... Am I missing something?? Thanks for your help.
Bootloader:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
Solved!!!: Apparently I was on the right track. My US T-Mobile G1 was locked somehow to only accept only RC30 and above. I made a goldcard for my SD card and the image no longer failed (same sd, same image file) at the flashing the .nbh. If anyone has been having issues flashing a US G1... try a goldcard... It instantly fixed the problem! I guess its not only for German and UK?!
BTW.. thanks to pk at codeandroid.org for his guide to make the goldcard without a WM device or linux... http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2 (in broken english... lol)
Thanks to Viper and revskills.de for their work on goldcard images
Thanks to JesusFreke for this bada$$ ROM (1.5)
Thanks to Haykuro for his android 101 guide.
Great work everyone really...
you need to make sure that your sd card is formatted fat32 and checksum on the DREAIMG.NBH
then try again. should work.
thanks for replying did that. The md5 checksum matched perfectly I have 3 different sd cards all formatted in fat32 only. still no go. I have tried 3 different links to the dreaimg.nbh. made sure it was in all caps and everything. nothing.
It will find the file.
It will flash the file to 100%.
When it would normally check the integrity of each portion it says...
"dreaimg.nbh - FAIL"
"Update Terminate"
"Update FAIL".
The odd part is it will flash the RC30 nbh just fine... same sdcard, same instructions.
try a different sd card- my stock one didnt flash either, same error over and over.
use this nbh -
http://www.mediafire.com/?sharekey=78b87e4b3d9bce857f7ec40ada4772a691de501fd3b9a6eb5be6ba49b5870170
tried all 3 cards with your file. same thing. Why will it so willingly let me flash rc30 the exact same way?
you got me.....
this was the confusing part. so im sitting on rc 30 right now for the 5th time. i have had 30 or so unsuccessful flashes of RC29 and EVERY flash of RC30 was successsful... this is my barrier to Haykuros and/or JF roms...
The file names are case sensitive. It must be DREAIMG.nbh . All caps for the prefix, no caps in the suffix.
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
That may not be the issye... I had RC30 when I bought the phone. I was able to get to RC29 with no issues... I don't think tmobile did anything to the phone.
i wish it wasnt but how can this phone reject rc29 but accept rc30. does anyone have a rc28, rc19, or below .nbh?
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
ICBM said:
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
Click to expand...
Click to collapse
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
crushsuitandtie said:
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
Click to expand...
Click to collapse
You are right, you need root to be able to load a different boot loader. I got a replacement sent to me from T-Mobile with RC33 on it maybe 3 weeks ago and i had no problems with obtaining root. If i were you i would call up T-Mobile and tell them the Menu button is not working every time on your replacement. They may send you an express replacement...
makes me wish i had kept my launch phone... I got it with RC17 or 18... but i remember getting rc19 ota... this sucks. The only reason i traded it in is because GPS wouldnt ssync anymore unless i did a wipe... so i knew it was a software problem... if i had just rooted it I bet i wouldnt be in this crap. i couldbe on haykuros... right now...
Sounds like a hardware issue to me. The data from the SD card isn't being written to flash properly so the SPL can't verify it. I would try calling T-Mobile to see if they can send you another unit. Obviously don't tell them you tried to flash an unsupported ROM, just make up a story and they will likely believe it.
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
crushsuitandtie said:
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
Click to expand...
Click to collapse
ok i received my phone like a month ago an it came with Rc33 install and my phone when try to flash Recovery, i get a error EveryTime, look at all My Topic you see
I just keep on trying and i get it on my 7th try lol I'm not lien
bp8575 said:
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
Click to expand...
Click to collapse
The correct image name is DREAIMG.nbh. looks wrong but its right... I think it IS a hardware issue. The is writing but not verifying certain images... and its now giving me checksum errors on rc30 after 8 successful loads, but when i retried without doing anything to the file it completed. I would say its my card but I have 3 different cards...
bump for anyone else having trouble...
WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.
Rooting my 1.2 was easy... unrooting has been a nightmare, until now.
Once the sappimg files for both the fender and 1.2 were found I thought i would easily just power into hboot and rename to sappimg.zip blah blah blah etc. Well for some reason, i was getting the main version is older error.... as if I had created my gold card wrong. Gold card or regular SD card, it just was not working.
Afraid to change my SPL and try again, I decided to use my goldcard to revert back to the original 1.5 sappimg we all used to originally root our devices. Booted, got the dead touch screen and finally powered off. I was finally able to boot into hboot and install the tmobile sappimg for 1.2. Voila!
Anyways, this method should work for all, not just some. I will probably go back to root so i can keep playing around with the slide rom, but I'm happy to know I can revert without hitch if I decide to get the 2.1 OTA update whenever that happens.
rando191 said:
Rooting my 1.2 was easy... unrooting has been a nightmare, until now.
Once the sappimg files for both the fender and 1.2 were found I thought i would easily just power into hboot and rename to sappimg.zip blah blah blah etc. Well for some reason, i was getting the main version is older error.... as if I had created my gold card wrong. Gold card or regular SD card, it just was not working.
Afraid to change my SPL and try again, I decided to use my goldcard to revert back to the original 1.5 sappimg we all used to originally root our devices. Booted, got the dead touch screen and finally powered off. I was finally able to boot into hboot and install the tmobile sappimg for 1.2. Voila!
Anyways, this method should work for all, not just some. I will probably go back to root so i can keep playing around with the slide rom, but I'm happy to know I can revert without hitch if I decide to get the 2.1 OTA update whenever that happens.
Click to expand...
Click to collapse
good to hear you got it to work... sorry i couldnt be much help myself since i havent attempted to unroot.. but if you wanted to unroot because you where worried you wouldnt get t mobiles ota update to 2.1.. it wasnt necessary to unroot, all you had to do is flash the stock fender rom with root and you will get the update...
am i the only one having a problem making a goldcard?
i've seached several threads here and several external links to how to make a goldcard all with slight variations but still cant get it to work.
i have used both a kingston mirco sd and a sandisk mirco sd to no avail..
i have tried using mmc0, mmc1(well mmc1 wasnt available) and mmc2, i copied out the numbers from the CMD, reversed them manually, replaced the first two-digits with '00', got the image from the website and did the hex editor thingy and confirmed it worked by removing it and putting it back into computer and phone without any error prompt to format, but still i cant get the downgrade to work. i always get the 'CID error, update failed' message.
im trying to downgrade my desire z from the OTA 2.3.3 to something that can be rooted following this guide http://forum.xda-developers.com/showthread.php?t=1178912, and i was hoping to try out this custom Rom, http://forum.xda-developers.com/showthread.php?t=1216997 but it seems like my dreams wont come through coz of the goldcard issue.. :-(
we are on the same boat man! hirap amp!
try to ask here...
some already downgraded their units...
soon for my phone but still reading some stuff which rom to use
its so hard to root htc desire always cid installation failed