So I purchased an HTC Dream from a friend and learned all about the wonders of rooting, and found what i thought was going to be a simple step by step guide to upgrade my phone to android 2.1, and was encouraged to use it after reading all the positive comments. I can't post the link to it as I'm a new user, but you can find it by entering "guide on how to root your htc dream to 2.1" into google, the article is on adroidheadlines.com...
I followed it step by step until I got to step 20. After entering:
adb reboot bootloader
i got "error: closed." Being stupid, I looked around on the internet and came across a page that said putting a file called "DREAIMG.nbh" onto the root of my sd card would fix all my problems. Unfortunately for me I did, and then used fastboot which i (think) flashed that rom (i think that's the right lingo, anyway) To my surprise, I turned on my phone to see "T-Mobile G1" on my screen as opposed to the regular "ROGERS" logo. My phone won't move past that screen and won't even boot into recovery or fastboot. I have this gut feeling i've bricked the damn thing and am looking for someone to tell me it isn't so. To clarify, I'm wondering if there is anyone to factory reset the phone or restore it to its original rom somehow while its in this state.
Any help at all would be appreciated, and i can't seem to find anyone else on the internet stupid enough to have made the same mistake, which is never, ever a good sign.
i think you grab the wrong Dreaimg, there is 2 different ones if im not mistaken.. have you tried turning off phone hold camera then power?
If you can get in there then you can use this guide
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_EBI1
These are the instructions you should have followed for Rogers..
The op was actively rooting the dream (just using a clone of the instructions with a typo) 'adb reboot bootloader' instead of 'adb shell reboot bootloader'
The wiki page has this correct, the comment on the article the op read indicates the correct one and comments in the thread on XDA indicate if you are stuck all we where trying to do was enter fastboot..
Unable to find any of what I just mentioned op left the guides for rogers dreams and switched to T-Mobile Howtos and got a t-mobile nbh, having already installed danger SPL it could be flashed.
80% of the time this would have left the user with RC29, however 20% of the time system fails to flash correctly, and you need to flash it again. This is made harder since now you have the rainbow SPL (no fastboot and security locked) 1.x radio, and a Rogers CID. Thus need a gold card.
There are many nbh files however; one with the rogers CID can be flashed without a gold card.
http://www.rogers.com/dream-zip
has the current 911 patched nbh file (unzip it).. that will let you start again, but do note nothing went wrong the first time so don't enter and endless loop please.
(Note I recommend you apply it twice to ensure all partitions are flashed correctly, rogers has the partitions layout of dangerSPL, not t-mobile stock SPLs)
Okay, I understand what I did wrong, and I understand how I WOULD flash the file you provided using fastboot, except that my computer no longer recognises my phone when I connect it, and as a result I can't access the phone using adb... Not sure what to do next. Would placing that file on the sd card using an sd reader change anything? Or is that what you meant for me to do?
EDIT: Nevermind, I figured out what I was supposed to do with that file, though the problem remains that my computer no longer recognizes my phone when I connect it via USB. Is this hopeless?
EDIT (again) I tried holding camera while powering up, before it didn't do anything but now the phone has booted to a screen with 4 horizontal coloured bars. the screen reads
"DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO- 1.22.12.29
Sep2 2008
Serial0"
Not sure if that means anything but I figure it could. Please advise.
weezerx said:
I looked around on the internet and came across a page that said putting a file called "DREAIMG.nbh" onto the root of my sd card would fix all my problems.
Click to expand...
Click to collapse
That is also how you can flash the rogers 911 nbh from the 0.95.* spl that has no fastboot..
It may fail but it will likely then have 1.33.0010 and the 3.x radio that if you flash it a 2nd time will work.
Once done remove the file from the sdcard
ezterry said:
That is also how you can flash the rogers 911 nbh from the 0.95.* spl that has no fastboot..
It may fail but it will likely then have 1.33.0010 and the 3.x radio that if you flash it a 2nd time will work.
Once done remove the file from the sdcard
Click to expand...
Click to collapse
I really appreciate the help but I'm very new at this and I'm not entirely sure of what it is you're asking me to do
So does that mean all i need to do is remove the G1 image from the sd card and put the rogers one on via an sd reader and I'll be okay?
weezerx said:
So does that mean all i need to do is remove the G1 image from the sd card and put the rogers one on via an sd reader and I'll be okay?
Click to expand...
Click to collapse
And power on while holding camera it ought to ask you if you want to flash it..
Well I followed all of the instructions and removed the bad image from the sd card and put on the one you provided, turned on the phone, attempted to flash it, and got to a screen that says "Update terminate UPDATE FAIL" ... ideas?
Remove sdcard, boot holding camera, tell me all the text at the top of the screen
"DREA210 PVT 32B RUUNBH
HBOOT - 0.95.0000
CPLD - 4
RADIO - 1.22.12.29
Sep2 2008
Serial0"
Interestingly enough, when I boot to that screen now (despite having no sd card in the phone anymore) it still switches to the screen it tried to update with before (light blue background, darker blue text) for a split second before switching back... it never did that before, I'm not sure if that means anything.
Again, I really appreciate all the help though I'm starting to consider sending it to someone for JTAG if we can't find a solution
Hem I think rc29 on a gold card will make your phone into a T-Mobile dream that can be rooted with the telnet method.. remember you will have a 1.x radio so you will not want to directly install danger spl.
The big trick IS unless you have another HTC phone making the goldcard
I'm nt sure what you mean by all of that I tried backing up the fles on the sd card and only putting that nbh file on the card and that didnt work. I tried putting it on with all of the other files that were on it before in place of the other nbh that screwed up the phone in the first place... unsure what to do next. Was i supposed to put the "HTC update" file on the sd card without unzipping it? :S I'm so lost. ezterry, you're from toronto and do jtag service right? cause I'm not too far away...
Okay so scrap everything I said before. I decided to investigate the whole goldcard thing and to me it sounds like it's my best bet. I have a buddy who's willing to let me use his HTC Magic to complete the process. I found a guide online here
http://www.droid-den.com/android-guides/android-guide-how-to-create-a-gold-card
It sounds easy enough to follow, but I have a few questions. First, does the app "GoldCard Helper" still exist, because i know google has taken apps off the market before. Secondly, would you recommend this method/ have any advice or maybe a different way of doing things? and thirdly, just using my friends phone to get the CID for the sd card doesn't pose any threat to it at all, right?
Related
i was following this guide here http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod and everything seemed to go smoothly. i verified the md5 thing and it matched and everything. my sd card is fat32 for the record. i got to where it was flashing the spl. the screen stayed saying it was flashing for a really long time and half way through the device rebooted itself. It was plugged into its charger and I was not touching it. It just rebooted prematurely before the spl had been flashed. now when I boot up it doesnt bring up android or anything!
i bought this phone second hand and unlocked it, im using it with telus. If its bricked can i send it anywhere to get fixed?
edit: not sure if it means anything but it said HBOOT was 0009 not 0010. apparently 0010 was perfect spl or something like that. im not sure if this matters but its just something i noticed.
ddd67 said:
It just rebooted prematurely before the spl had been flashed. now when I boot up it doesnt bring up android or anything!
i bought this phone second hand and unlocked it, im using it with telus. If its bricked can i send it anywhere to get fixed?
edit: not sure if it means anything but it said HBOOT was 0009 not 0010. apparently 0010 was perfect spl or something like that. im not sure if this matters but its just something i noticed.
Click to expand...
Click to collapse
So can you get into recovery or fastboot?
Ace42 said:
So can you get into recovery or fastboot?
Click to expand...
Click to collapse
No, it doesn't do anything.
can anyone help PLEASE
If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.
ddd67 said:
No, it doesn't do anything.
Click to expand...
Click to collapse
Which spl were you flashing? Did you flash a radio first?
Not being an ass, but you do know how to enter these modes, right.
Fastboot= camera+power held down
Recovery= home+power held down
If it is indeed bricked, there are very few solutions. Only working one is replacing board at the moment. There is other ways trying to be had in development forum as we speak. Don't start a new theard, but search and read thoses, maybe something can help you/help them.
goldenarmZ said:
If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.
Click to expand...
Click to collapse
That's the thing, I didn't interrupt the flash. I thought that if I checked the md5 hash that it would work perfectly. I didnt know it could fail without me doing anything.
fastludeh22 said:
Which spl were you flashing? Did you flash a radio first?
Not being an ass, but you do know how to enter these modes, right.
Fastboot= camera+power held down
Recovery= home+power held down
If it is indeed bricked, there are very few solutions. Only working one is replacing board at the moment. There is other ways trying to be had in development forum as we speak. Don't start a new theard, but search and read thoses, maybe something can help you/help them.
Click to expand...
Click to collapse
Can I send the phone anywhere and get it fixed?
goldenarmZ said:
If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.
Click to expand...
Click to collapse
I followed this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
My dream is a rogers one, so I assume its EBl1, I haven't done anything to it besides follow that guide.
1. I got my 2GB memory card and formatted it to FAT32 on my computer.
2. I put spl-1332005.zip on the card (I kept it as a zip)
3. I downloaded this file: signed-dream_devphone_userdebug-img-14721.zip
4. I opened that file I downloaded and copied system.img to my memory card.
5. I downloaded update-cm-4.2.x-signed.zip and bc-4.2.x-ebi1-signed.zip on my SD cards root.
6. I installed zinx recovery flasher and cm-recovery-1.4 32A flashed onto my phone (now that I think about it I didnt check to see if my phones 32A. I don't know where to do that)
7. I booted into cyanogenmod screen.
8. I flashed the SPL, it didn't get interrupted and I thought all went right, but I guess not.
That is everything I did. did I do something wrong?
ddd67 said:
That's the thing, I didn't interrupt the flash. I thought that if I checked the md5 hash that it would work perfectly. I didnt know it could fail without me doing anything.
Can I send the phone anywhere and get it fixed?
I followed this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
My dream is a rogers one, so I assume its EBl1, I haven't done anything to it besides follow that guide.
1. I got my 2GB memory card and formatted it to FAT32 on my computer.
2. I put spl-1332005.zip on the card (I kept it as a zip)
3. I downloaded this file: signed-dream_devphone_userdebug-img-14721.zip
4. I opened that file I downloaded and copied system.img to my memory card.
5. I downloaded update-cm-4.2.x-signed.zip and bc-4.2.x-ebi1-signed.zip on my SD cards root.
6. I installed zinx recovery flasher and cm-recovery-1.4 32A flashed onto my phone (now that I think about it I didnt check to see if my phones 32A. I don't know where to do that)
7. I booted into cyanogenmod screen.
8. I flashed the SPL, it didn't get interrupted and I thought all went right, but I guess not.
That is everything I did. did I do something wrong?
Click to expand...
Click to collapse
It looks as if you didn't flash the radio first. the 26I radio, that is
Oh man, which part of the guide shows me how to flash the radio?
ddd67 said:
Oh man, which part of the guide shows me how to flash the radio?
Click to expand...
Click to collapse
If you flashed the spl already, it is too late. The radio NEEDS to be flashed first
@ people telling him to flash the radio, if you're following that guide, you don't flash the radio, you leave it as is.
He did nothing wrong, he just got ****ed up by pure chance, though if he were reading the guide closely he would realize that he wasn't supposed to put system.img on his SD card.
That SPL is safe on all Rogers dreams.. either you were spectacularly unlucky with a bad flash, or it isn't actually bricked.. Remove the battery, hold the camera button, replace the battery and power on.. anything?
goldenarmZ said:
That SPL is safe on all Rogers dreams.. either you were spectacularly unlucky with a bad flash, or it isn't actually bricked.. Remove the battery, hold the camera button, replace the battery and power on.. anything?
Click to expand...
Click to collapse
No dice. I didn't think it was possible for it to just brick on its own accord
AHH!
So I followed the turorial on updating the rogers HTC Dream to a T. I successfully changed the SPL to 1.33.2005 but the "system.img" file is no longers available on the HTC developer website. I tried using the system.img file from the Google I/O page (from the HTC developer website) but was left with a phone that pretty much was an HTC version of the iPod touch with no phone-related-applications working. does anyone have a backup of that system.img file for android 1.6 for the Htc DREAM??
Thanx
Meldon
@meldonlobo, are you looking for this?
http://forum.xda-developers.com/showthread.php?t=593626
I thought this was 100% safe. what happened?
my radio version was 3.22.20.17 and HBOOT-1.33.0009 (DREA21000). my friend told me to post that because it might help. Is that radio right for following the guide?? It also says 32B not A. The tutorial mentions something about 32A. Is that why?
i remember that if i went to recovery mode when it was stock it showd an exclamation mark
Please can someone tell?
I decided to get in on the Android experience and bought a used G1 off ebay. When I got it (supposedly unlocked, but it wasn't ) it was running Cupcake 1.5 with the CRC1 build. One oddity that was stated in the auction listing is that the phone would not do a Factory Reset. When I tried it, it would go to the rainbow boot screen, but I could restart it (both a battery pull or a Menu/Home/Power press) to get back to life. I read several pages, both here and at cyanogen's page to make sure I would do the root process correctly with the eventual goal of getting this thing to cyanogen's Froyo 2.2 version. Needless to say, it has failed ... at step 1 no less. I reformatted the SD card (a 2 GB SanDisk) to FAT32 with WinXP, loaded the DREAIMG.nbh file, and rebooted the phone. The gray screen with blue text came up for the reflashing process, so I hit Power to continue. The "Update in Progress..." text shows and the bar moves until completion. After pausing momentarily at the end of the progress bar, it shows:
00018003
DREAIMG.nbh - FAIL
BOOTLOADER - OK
RECOVERY - Fail
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_V2 -
Update Terminate
UPDATE FAIL
The rainbow boot screen says:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
The phone will now not boot past the rainbow screen. Note that if I have an SD Card with the flash image in the phone that it will go to the flash screen even if I do not hold the camera button (maybe that is normal). I searched Google for "00018003 "Recovery - FAIL"" and even it can not find any one who apparently is having the same problem.
I have repeated the update attempt several times with identical results. I downloaded the file multiple times from different locations, but the md5 has always matched regardless of where I get it from. I reformatted the card from Linux (Ubuntu) and I tried another SD Card (8 GB AData). Does anyone have any ideas on what to try? I am adept with Linux, but am a newbie to Android.
Thanks.
Code:
jeph36 said:
I decided to get in on the Android experience and bought a used G1 off ebay. When I got it (supposedly unlocked, but it wasn't ) it was running Cupcake 1.5 with the CRC1 build. One oddity that was stated in the auction listing is that the phone would not do a Factory Reset. When I tried it, it would go to the rainbow boot screen, but I could restart it (both a battery pull or a Menu/Home/Power press) to get back to life. I read several pages, both here and at cyanogen's page to make sure I would do the root process correctly with the eventual goal of getting this thing to cyanogen's Froyo 2.2 version. Needless to say, it has failed ... at step 1 no less. I reformatted the SD card (a 2 GB SanDisk) to FAT32 with WinXP, loaded the DREAIMG.nbh file, and rebooted the phone. The gray screen with blue text came up for the reflashing process, so I hit Power to continue. The "Update in Progress..." text shows and the bar moves until completion. After pausing momentarily at the end of the progress bar, it shows:
00018003
DREAIMG.nbh - FAIL
BOOTLOADER - OK
RECOVERY - Fail
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_V2 -
Update Terminate
UPDATE FAIL
The rainbow boot screen says:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
The phone will now not boot past the rainbow screen. Note that if I have an SD Card with the flash image in the phone that it will go to the flash screen even if I do not hold the camera button (maybe that is normal). I searched Google for "00018003 "Recovery - FAIL"" and even it can not find any one who apparently is having the same problem.
I have repeated the update attempt several times with identical results. I downloaded the file multiple times from different locations, but the md5 has always matched regardless of where I get it from. I reformatted the card from Linux (Ubuntu) and I tried another SD Card (8 GB AData). Does anyone have any ideas on what to try? I am adept with Linux, but am a newbie to Android.
Thanks.
Code:
Click to expand...
Click to collapse
How much is your phone charged...charge it full and then try again....
I obviously can no longer see the meter in Android. I charged it with the phone off to a green LED and still get the same result.
Possible other relevant information:
When charging from my computer with the phone off, the LED is red, not orange. I did not notice this at first as I have not had the phone long enough to know what is "normal".
If I power up with the USB connected to my computer, the rainbow screen looks almost identical except it does not have the text "Serial0". If I unplug USB then that text appears after a couple seconds. Does that mean I can get do some serial communication that would help with the problem?
Are you sure you have the right dreamimg.nbh file? There is 2 of them. Did you put .zip after it?
sent from my superfroyo dream
I used cyanogenmod's wiki (and other pages with identical or similar instructions) which indicates to name the file exactly DREAIMG.nbh, so that is what I did. Is there a different reason I should use .zip? I also chose to do RC29 as I am assuming this phone is a US phone (I purchased from a US seller). Is there an easy way to tell which phone I have (US or Europe)? Should I try RC7, or will that completely brick the phone if it is the wrong version?
Thanks.
No you won't brick the phone. I don't know what version you'd want. I'm in usa. Never had to deal with the other. The only way you'll brick your phone is by messing with danger spl 1.33.2005 just remember if you downgrade. It changes your spl and radio. The whole package. Then you want to flash radio back to 2.22.23.02. Or 26I in your case. Before flashing danger spl. But your not even there yet. Yeah make sure you have a .zip after dream nbh file on root of your sd card. Before flashing.
sent from my superfroyo dream
Well that answers that question. I tried the RC7 for Europe and after the "Loading..." and "Checking..." stages it shows:
0028002
Not allow
and drops back to the rainbow. So I definitely have a US phone as expected.
What is the .zip file that I should have on my SD card? I do not see that in the instructions to get to the state where my phone is rooted.
Just make sure before you flash the dream nbh you have a .zip after it before you flash it
sent from my superfroyo dream
I am still not sure what you mean by the .zip. I tried renaming DREAIMG.nbh to DREAIMG.nbh.zip, but that could not find a file for updating. Then I tried putting a .zip file on the sdcard at the same time as the DREAIMG.nbh file and that did not help. So if you could shed some light on that, maybe I can make some headway.
Thanks.
I have made no progress on this over the last 24 hours. I tried several more flashes to see if eventually one would take, but I always get the same result.
man where have you been or maby where have I been? That was a very good information on the dangers of danser spl. If I have seen this earlier I would not have bricked two G1's. I know know what I did wrong. Never heard it explained that way.
Thanks
I am not sure what you mean. I have only tried to downgrade to the RC29 image as the first step toward rooting the phone. I am beginning to wonder if the previous owner did some failed mod's prior to me owning it and that is why it is stuck in the state it is in. Has anyone ever seen anything like this before?
What's going on. Pm and let me know where you guys are at. Not gonna keep coming back to this thread.
sent from my superfroyo dream
this is intresting as i have similar mobo in same situation, though I had even recovery... the phone would stay fine in hboot, BUT when i tried to go and put the .nbh file it went about 2/3's then the screen turns off and thats it... i cant get into this mobo have to wait with battery out for a few min and then i can go back into hboot
is there a solution? some other nbh file to flash? or do i need to go the jtag/serial route :/ which i have but it takes almost few hours to do with slow wiggler jtag
I never got a solution. As that phone was mostly just a temporary Android experiment for me, I gave up and got myself a new Samsung Vibrant. I still have the G1, though, if anyone has a solution ... Otherwise it will probably go on eBay as a non-working/bricked/for-parts phone.
jeph36 said:
I have made no progress on this over the last 24 hours. I tried several more flashes to see if eventually one would take, but I always get the same result.
Click to expand...
Click to collapse
This should help:
http://theunlockr.com/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/
Follow instructions to the letter. Looks like the whole procedure was made easier.
(Rogers HTC Dream)
Ok, so, i know this sounds ridiculous, and you may find yourself asking "WTF Was He Thinking?!?!?" But, was a late night, and i was quite possibly half asleep lol...
Ok, so, long story short, i have tried possibly every rom for the Rogers Dream, and majority of them didn't work for me, or atleast, if they did, not that well.... Cyanogenmod 6 worked ok, although it started to get slow pretty fast :/ Anyways, i had previously rooted and flashed my dream with the steps provided on cyanogen's wiki, but i had never updated the kernel or anything, so, i came to the conclusion that it was possibly my kernel that was un-allowing me to run most roms, so i decided to update my kernel using the steps here
"http://forum.xda-developers.com/showthread.php?t=831139"
Everything went well, kernel updated, wiped everything, except i accidently deleted my recovery.....but thought, no problem, i'll just follow the instructions on the thread, no biggie.....it said to download the "orange-1.58.73.2.nbh" and flash that......BUT... I Should have known that the Orange one was the one for T-Mobile!! But out of stupidity i didn't realize it and flashed it!! Now my phone won't boot up or Anything :/ when i try to boot into recovery OR Hboot, it shows the t-mobile startup flash, then shows an error with a triangle and a yellow exclamation in the middle, with a phone on it's side beside it!! :S
Did i completely mess up my phone?.... Someone please help!! x.x
I got a Rogers dream and I just push amonRA with adb. As for the exclamation screen, I think there is a key combo to bypass it. Something like volume up and power at the same time. I can't remember now the exact combination. Took a lot of Googling to find it, and if I remember correctly the dream has a different combo than the tmo did. But with this nexus one my memory has faded.
Sent from my Nexus One using Tapatalk
The orange nbh is orange not t-mob..
But has a eng spl so recovery is easy.. head over to my 2708+ radio thread and flash that, a 2708+ rom (most new roms support it and older ones the kernel in that thread will fix it.
Rogers if they are your carrier may cut wireless data there is a e911 wavier form to get around this search for it or ask the support person if they cut your data for detasils.
The good thing about using the 2708+ radio/kernel is extra ram, and it works on the rogers dream the same way as the non rogers dream thus you can ask more people to help support you with 2708+
Thanks for the reply guys,
ezterry:
thanks for replying, would had posted in your thread but didn't want to jam it full of even more posts of someone needing help lol...
as for your reply, it was after i had flashed the orange nbh that i was getting the t-mobile splash :S thus i assumed it was t-mobile.... but, as for flashing anything, i can't....when i try to boot phone in hboot or recovery, i get the error i previously mentioned, and when i normal boot, i can only get to the screen that says to plz insert sim card, and it won't let me pass that screen :S....that's where im stuck.....i tried using the usb cord to access adb through it, but on the comp it says there are no adb devices, i'm assuming it's because i can't get past the "no sim card" screen to enable debugging ..... Any suggestions?
Thanks!!
I'm going to hope you are doing something silly since your description indicates no problem with the phone.
SpawnOfSatan said:
but, as for flashing anything, i can't....when i try to boot phone in hboot or recovery, i get the error i previously mentioned
Click to expand...
Click to collapse
That /!\ screen *is* recovery, alt+L will show you additional options.. but in its self its not that useful.
SpawnOfSatan said:
, and when i normal boot, i can only get to the screen that says to plz insert sim card, and it won't let me pass that screen :S....that's where im stuck..
Click to expand...
Click to collapse
I don't recall if adb is enabled by default on the orange rom; regardless this is the rom. (putting a sim card active or not in the phone may let you get further however ought not be necessary )
So either you got so anoyed at your phone you did phisical damage to it or you are attempting to enter HBOOT/Fastboot incorrectly.
Powering on when holding 'camera' is supposed to always bring you to the HBOOT screen; then pressing send or back as prompted will let you to the Fastboot screen (don't re-flash the orange NBH, say no if it asks)
Alternatively either booting with send or back will go directly to HBOOT.. (The rogers [2000 series] dream uses Send while the t-mobile (100 series) users Back but some SPL only provide the back options regardless of dream model.. I don't recall about 1.42.2000 so you will want to try both)
In theory Home is the only button to send you to recovery.
Once in fastboot it ought to be a full featured fastboot and the normal 2708+ install instructions will work using fastboot on your PC
That /!\ screen *is* recovery, alt+L will show you additional options.. but in its self its not that useful.
Click to expand...
Click to collapse
Ahh ok lol, i'd installed RA recovery when i first got the phone, so it was the only recovery screen i remembered ever seeing, thus why i was confused, but yah, hit alt+L and saw the options, but yah, not that many :/
So either you got so anoyed at your phone you did phisical damage to it or you are attempting to enter HBOOT/Fastboot incorrectly.
Click to expand...
Click to collapse
Apparently was entering it wrong, i was used to using Home+Cam+End to enter hboot.....so that's my fault....
Once in fastboot it ought to be a full featured fastboot and the normal 2708+ install instructions will work using fastboot on your PC
Click to expand...
Click to collapse
[/QUOTE]
When i enter hboot, it looks like a friggin rainbow now lol....red, green, blue, and white bars as the background :/ and once in hboot, it says "Serial0" in the middle of the screen :S and when i plug it into the computer, i tried hitting both back, and send, and it makes the "Serial0" dissapear, but seems no matter what i do, it won't show the phone as a connected device in fastboot :S
Thanks again for replying soo quickly and all the help u've been giving me, any advice on where to go from here or getting it to enter fastboot?
What you are describing is not 1.42.2000.. but 0.95.0000.. or that its likely the Dreaimg you flashed was the t-mobile rc29 and not the orange nbh..
Rc29 can be flaky.. but there are two options
1) go to recovery, alt+l and wipe, put a sim card into the phone and root via telnet.. assuming you have the 1.x radio of rc29 follow the link to my 1.33.2003 spl then with that install 2708+ normally
2) if you still can't boot you will need to use/make a goldcard (if you don't already have one this may require finding a friend's phone to help make one) and this time flash the orange nbh *not* rc29
0.95.0000 will not let you flash a rogers nbh so there is no way to re-flash with out a goldcard.. otherwise I'd just have you flash the roger 911 patch and re-root from there..
hey if you are still getting that screen with the yellow triangle and '!' that means you have stock tmobile recovery with no rom lol can you try to press (alt+L) hold alt and press L should make a list pop up.. if it does than maybe you can still re root it so than it will read your sim... but im not sure if the rogers G1 has and different software so it could possibly make it worse.. lol just a suggestion
ezterry said:
What you are describing is not 1.42.2000.. but 0.95.0000.. or that its likely the Dreaimg you flashed was the t-mobile rc29 and not the orange nbh..
Rc29 can be flaky.. but there are two options
1) go to recovery, alt+l and wipe, put a sim card into the phone and root via telnet.. assuming you have the 1.x radio of rc29 follow the link to my 1.33.2003 spl then with that install 2708+ normally
2) if you still can't boot you will need to use/make a goldcard (if you don't already have one this may require finding a friend's phone to help make one) and this time flash the orange nbh *not* rc29
0.95.0000 will not let you flash a rogers nbh so there is no way to re-flash with out a goldcard.. otherwise I'd just have you flash the roger 911 patch and re-root from there..
Click to expand...
Click to collapse
Hboot is 0.95.0000
Radio is 2.22.19.26I
So i'm guessing it is the rc29 And i'm not too sure what a gold card is? :S
SpawnOfSatan said:
Hboot is 0.95.0000
Radio is 2.22.19.26I
So i'm guessing it is the rc29 And i'm not too sure what a gold card is? :S
Click to expand...
Click to collapse
that sounds like stock 1.5 firmware to me
..Still have yet to find a solution....any help please?
info again is
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Background:
Accidently wiped rogers rom + flashed t-mobile rom, and since then,
Hboot says "Serial 0" and won't allow me to flash any images, phone doesnt have a recovery, will boot up now, but only to the android set-up process which i can't continue with because it won't accept my rogers sim card, despite the fact i unlocked the phone before all this happened :/ so i can't sign in to or create a google account. Have attempted every bypass to get past it with no success. Obviously since i can't get past it i have no access to adb...
Please help
Just out of my curiousity, got download the orange nbh file (make sure that it marked orange).
Format your SD card to FAT and put the nbh file in the root of your SD card.
put the SD card in your G1.
Boot up with camera+power and flash it.
See if that work.
BeenAndroidized said:
Just out of my curiousity, got download the orange nbh file (make sure that it marked orange).
Format your SD card to FAT and put the nbh file in the root of your SD card.
put the SD card in your G1.
Boot up with camera+power and flash it.
See if that work.
Click to expand...
Click to collapse
Thank you for your response, unfortunately i have tried that countless times with no luck it says it cannot read or flash or something, i forget what it says Exactly but it wouldn't allow it x.x any other suggestions?
I'm Really desperate x.x and i have been having the crappiest luck lately. I bought a phone off kijiji today, spent 3 hours trying to meet up with the guy to buy it, then when i did get it (after all the running around) i took it to "The Source" to get it activated in my name , and after 4 hours (5pm-9pm) they finally said they tried everything but couldn't do it because the phone is registered to someone with a contract that has a suspended account do to owing an outstanding amount of money!!
At this point, when you boot up the phone. What do you see?
BeenAndroidized said:
At this point, when you boot up the phone. What do you see?
Click to expand...
Click to collapse
It loads up to the setup screen, in which i cannot bypass...i have tried with another active (with data) rogers sim, telus sim, and virgin mobile sim card, but none of them will work....and like i previously mentioned, i unlocked the phone prior to all this happening :S
OK! I am not sure why it will not let you activate your phone. But don't worry about that ATM.
Let try activate your G1 over wifi. Follow the instruction from the link below.
http://theunlockr.com/2010/01/10/how-to-activate-the-g1-without-a-data-plan-or-sim-card/
Okay, so a few years ago I successfully rooted my boyfriend's G1 and swore never again to go anywhere near the process.
However, said phone has now been given to my boyfriend's dad, and he's managed to install a couple of custom roms. In the last week though, he's totally screwed it up. Didn't seem to follow any sort of backing up process, or can even tell me what tutorial he was following to get it in this state.
The phone hangs at the splash screen. I can get into fastboot/hboot but there are only a few options available.
SPL is 1.33.0006 which I can gather is bad from my reading.
Hboot info is:
Dream PVT 32B Ship S-on
Hboot - 1.33.0006 (Dream11000)
CPLD-4
Radio-2.22.19.261
I have tried:
Initially I just tried going into recovery mode (I think that's what it's called - home & power) and wiping the data to see if that stopped the screen hanging. It didn't.
Putting rc7 dreamimg.nbh on the phone and loading via hboot/fastboot. When I do this it fails saying 'Main version is older.'
After doing some searching, I see someone mentioned this would mean you need to use the goldcard method. I vaguely remember having to do this a few years back on the phone when I rooted it the first time.
I go through the process, following an unlockr tutorial (can't post the link - sorry).
However, I get the same response through fastboot - 'main version is older'.
At this point I decided to try flashing a recovery image via the adb. Go through the process of installing everything etc. but when it came to installing the usb drivers for the phone, it failed although it did install the htc bootloader. I checked using adb devices command to see if it was picking anything up and it was however, when I go into the command prompt and try to do anything I just get a <remote: not allow> message.
It's only after I look for <remote: not allow> message error that I understand that 1.33.0006 is a 'perfect' SPL, and explains why I can't really do anything.
I really didn't want to resort to forum posting (one of the reasons I swore never to go near the G1 again after rooting was because I *know* I'm not tech savvy enough to be messing around with this stuff), but after spending around 6 hours over two days on this I'm absolutely stumped. The problem is, I'm stubborn so I hate to give up after spending so much time on the stupid thing (bye bye flexi day), so if anyone has any suggestions, or if they could just tell me it's a lost cause then it might help.
Thanks for your time...
do you have the UK version of phone or the US version?
can you get into recovery?
Sorry, it's the UK version - I can get into recovery (if that's home and power ?) I think. Thanks.
What nbh file was flashed prior to this? (almost sounds like the states someone was in after flashing the sappimg on a dream with 1.33.0013d..
Well first thing is to make a gold card if you don't already have one.. Then we can try one of two things. (you can make it on another phone, its a property of the sd card not the phone)
1) (may have the same main version is older problem but easy if it works) place the Orange nbh:
orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0)
onto the root of the goldcard named DREAIMG.nbh
If this works (or at least flashes the s=off SPL) you are in the clear simply use fastboot to re-install the 2708+ recovery/radio/spl then install a rom as per here
2) If option 1 failed... well this is an annoying process.. and risky if you take shortcuts so don't ..
A -- This time put the rogers e911 patched nbh rogers_1.89.631.1.nbh MD5:25bfcc329679e4869b3d65f673e463ac
onto the root of the goldcard named DREAIMG.nbh
This is the larges "main version number" in an official nbh for the Dream we have.
If that fails to flash (try again) if it still fails.. well I'm not sure what to do if both boot/recovery are failing (short of jtag anyway)
B -- If it succeeded you now (despite any labels on your phone) have a rogers dream.. (I mention this because working with an ebi1 radio is a bit different than the ebi0 and you don't want to brick your phone)
Ok next step is re-root: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(Sections A-D inclusive)
C -- Before installing a rom.. now that an eng SPL is installed you can use fastboot (and only fastboot with the 3.22 radio) to install the 2708 radio and thus have a more commonly supported system:
per Follow this 2708+ install
remember do not install a 2.22 radio via recovery while a 3.22 radio is installed you will brick your phone
--
Best of luck.. really sounds like something happened that ought not have.
Thank you!
Option 1 didn't work - I still got the 'main title is older' message.
However, option 2 (after a small wobble) worked! First time I tried it, it failed stating 'partition update fail!' but after a reboot (which showed the rogers logo - a change from before) and a retry, it worked! I followed the rest of the provided instructions and installed the BIFFMOD V2.1-EZTerry 2708 port and all is well!
Thank you so much again for your help, it really is appreciated. I would not have been able to do this without your help - I've sent a small donation through as a token of thanks.
I've learnt more about G1s than I ever wanted to know, but thanks to you (and the information provided by the XDA community) it wasn't all wasted time!
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks