yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] zeeshanzc:
i have the old rogers update RUU file which has the old rogers SPL and bootloader and other crap.... i dont know if it could come to any help but what i think is that some1 could try extracting the nbh and then modifying the update version to make it look like its higher and then flash this since it already has signatures by HTC ... i think... :confused:

http://www.megaupload.com/?d=0GYAL5AE
[G1 Android Development] bt1980:
I think the signing uses a hash or CRC from the file itself... which you would be modifying to change the version... which means signing has to take place again, afterwards.
[G1 Android Development] n64_ali:
Here's what I got when I tried that method with the 1.33.2005 spl in my sd card's root:

E: Can't open /cache/recovery/command

-- Install from sdcard...

Finding update package...

E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)

(No such file or directory)

E:Can't mount SDCARD:update.zip

Installation aborted.
[G1 Android Development] boostnek9:
do you have a gold card? or is it just a regular sd card?
[G1 Android Development] boostnek9:
sorry for posting again..but if it asks to put the update.zip file on my SD card... what is that ? the radio ? the SPL ? I want to try this..
[G1 Android Development] n64_ali:
I just used a regular SD card. I wasn't aware I had to perform this method with a gold card...can any experienced user confirm?
[G1 Android Development] boostnek9:
ok well I did it with a gold card and this is what I get..

=======================

-- Install from sdcard...

Finding update package...

Opening update package...

verifying update package...

E:No Signature (5 files)

E:Verification Failed

Installation aborted.

=======================
[G1 Android Development] TrainAss:
Sorry to derail the thread slightly, but has there been any discoveries on rooting a non-rooted, already updated Rogers HTC Dream? So far, everywhere I've looked, there's either old information, updates for an already rooted phone, or nothing...
[G1 Android Development] enomther:
Nope ... not rooted yet ... thought I had something the other day (turns out it was old news just like the other attempts) ... so lotsa people still plugging away at it.

~enom~
[G1 Android Development] TrainAss:
Well, I'm getting an HTC Magic (Free upgrade that I got AFTER the promo ended). my HTC Dream is un-rooted and has the update. It's also in excellent condition. Once I get my Magic, and should I like it, I'm willing to work something out with someone who is trying to root an updated Dream.
[G1 Android Development] boostnek9:
I just received my HTC Magic today! however I'm still patiently waiting for a solution to this..I'm willing to donate/help and do what I can for this ! :) keep trying guys and thanks for your efforts!
[G1 Android Development] xaueious:
Just wondering:

What happens when you load the DREAIMG.nbh from the post 911 update onto the phone to bypass the first signature check, and when it asks it to flash, take the sdcard out and swap the DREAIMG.nbh file with the old one?

NAME OF FILE MUST BE DREAIMG.nbh

I tried this with the Magic and this did nothing even though the progress actually seemed to finish. Anyone want to confirm this?

1) move post 911 DREAMH.NBH rom to sd card and put into phone root directory

2) boot to hboot and wait till the spl detects the ROM and asks you to flash it

3) swap the file and proceed to try to flash

Post 911 update: http://www.rogers.com/dream-zip

Pre 911 update: http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip

Extract the roms

I guess I should repeat this information because I see a lot of newbies posting.

The Rogers stock recovery requires specially signed update.zip files, or they wont flash. If you were using Amon_RA recovery, it was a modified recovery that accepts what is known as test keys. We can create update.zip files signed with test keys ourselves, but we do not have the keys accepted by the stock recovery.

Then there is also a signature check in the Hboot/spl for the roms you try to flash. The encryption itself is almost impossible to crack by brute force, and we have no access to this. Most of the .nbh or ROMs you see are those directly from HTC. ENG SPLs allow for nbh and other phone image files to be flashed without being signed.

The problem with the new Rogers SPL is that it checks for main version in the ROM you flash. There is no known method to bypass this check. We cannot just change the ROM header because it modifies the signature of the file once you do that. As I said before, we cannot sign our own phone image files. You can normally flash any ROM with a higher or same main version as long as you had a gold card and the ROM matches your phone's model ID.

Regarding the model ID, the it is hard to find a compatible phone image for the dream because the Dream model id is very specific to the region. All Magics have the same model id (SAPP10000), but there's a mess of them for the Dream. Rogers Dreams are DREA21000. I've seen DREA20000, DREA10000 and DREA11000. This makes cross flashing ROMs using the phone ROM method next to impossible, because we need an official phone ROM (RUU) release from Rogers with an unlocked RUU. So this makes waiting for a ROM with a higher version useless for Rogers Dream user.

The best bet right now is a kernel exploit of some sort. In this case, people to go into the source code to look for exploits. I am not a dev myself, but most of the devs have moved on to more advanced platforms. But probably we need HTC to release the source code for our Dreams.

If you have a Magic, you can probably get rooted someday. If you have a Dream, your root isn't coming any time soon or at all. It's a matter of time for the Magic to be rooted. There are a lot of Magic users all over the world, and the model ID doesn't clash, meaning that you can root the moment any 32A Magic from any region is rooted (non 3.5 mm jack version)
[G1 Android Development] boostnek9:
I havent tried that yet... I will tonight.. it's kinda like the swap trick for the ps2 back in the day...
[G1 Android Development] xaueious:
Ya except I don't think it's going to work. Worth a shot anyways.
[G1 Android Development] boostnek9:
meh... neither did the swap trick really lol
[G1 Android Development] boostnek9:
sooooo..... it doesnt work...it tells me update failed right away, it doesnt even start loading it on... thanks though...anyways...i'm willing to pay some good money if a root comes through that's for sure! I'm a Dream and a magic owner and both are unrooted sadly...
[G1 Android Development] Rebellion_CA:
Enom,

Will you be updating your AOSP build to have EBI1 support?

Rebellion
[G1 Android Development] xxxchargerxxx:
ahhh...the indignity...

Thanks to enom for the fine guide.

So I followed it and everything went nice and smooth, now my dream is a dream again with cyanogen 4.2.14.1+ebi1 kernel. Runs fine...my data connection has come back (cool!).

Anyhoo...I went to the rogers "waiver" page and requested my data be turned back on regardless of my update status. So I'm not completely sure whether that was the catalyst for my restored data or not (thought this would be a good way to double my chances)...why ask why.

So now, being the **** that I am, I want to go back to being a G1...see if my data connection stays (+be able to use any damn rom I want)...

I bricked my first dream by flashing a radio before the SPL and am a little gun-shy about trying things that involve radio+SPL. Sooo....any help on the correct (safest) method to return my dream to G1 goodness?

Thanks

M
[G1 Android Development] enomther:
Hey Rebellion! Been a long time my friend!

I will do this for you and any others for sure.

It will likely be later next week (waiting on my rooted dream to return to me), but I will definitely do this ... just a matter of a little time.

~enom~
[G1 Android Development] enomther:
Welcome.

And we do have confirmation from several sources that soon after (within 24hours) of flashing the latest RogersRadio data returns regardless of waver, etc.

Now, if you mean to say (by g1 goodness) ... that you wish to return to an EBI0 setup?

The absolute safest method (in my humble opinion) ... is to make sure you have a fully charged battery and then flash the RC29 US DREAIMG.nbh file in the bootloader, it's a sure fire safe method to return to EBI0. Then use flashrec or the like to get root again.

The only stipulation there would be, if your data plan is currently dependent on the newer RogersRadio, you'll have signin issues with RC29. JesusFreke has a post in regards to by passing the google signin in that setup, but it's a little hectic. (search and you'll find it).

Once you're rooted with RC29, install amon_ra's recovery, flash the latest g1 radio (2.22.19.26I), and then flash a good SPL, Haykuro's or the Hard.

If you meant something else, please advise.

~enom~
[G1 Android Development] xaueious:
Hey there's a kernel exploit that works right now for the Tattoo: http://xdaforums.com/showthread.php?t=635961

Someone with knowledge of kernel exploits should be able to get this to work on the Dream as well.

I just flashed my radio and back the other day. One procedure is:

1) flash the non R Amon_RA recovery (do this in recovery using flash_image command), and don't restart your phone

2) flash the ota radio update.zip from recovery

3) after your radio flashes (goes past the htc radio flashing screen), immediately hold the home button to get into recovery. if that doesn't work pull your battery until you get in.

You can do the same procedure in fastboot if that's easier for you.

If you are scared about not flashing the correct recovery, you can just check by flashing it first and trying to boot to it. If you flashed the EBI0 kernel recovery, your phone will get stuck at the Rogers screen when trying to boot to the recovery if you are still on the EBI1 kernel radio (3.x).

As long as your have a recovery that works with the radio you are going to flash, you are 100% safe.

This method also means flashing 2 files in 10 minutes instead of reflashing your whole phone in 30 minutes.
[G1 Android Development] n64_ali:
That looks really interesting. I'd love to try the same exploit but will wait until someone ports it to the Dream. Really looks promising though. Nice find!
[G1 Android Development] xaueious:
Edit: doesn't work

Someone already packaged this for easy use under windows:

Attachment link: http://xdaforums.com/attachment.php?attachmentid=283620&d=1266681855

I'm not completely sure what you can do after you get root and remounted partitions, but I think you need to do something like this:

If you have root, you can probably push flash_image onto the rom, then flash recovery. Once you have recovery you can flash over the SPL and everything else as you wish!

flash_image script to push after you get root

http://wiki.cyanogenmod.com/index.php/RE-recovery-img#flash_image.zip

Amon_RA Recovery for Dream:

http://xdaforums.com/showthread.php?t=566669

If you can get the recovery on, you just need to flash an engineering SPL to get fastboot access:

http://sapphire-port-dream.googlecode.com/files/spl-signed.zip

I am not making this a tutorial for newbies until we get some sort of confirmation that this script actually works.adb chmod 755 /data/local/bin/m6
[G1 Android Development] Rebellion_CA:
Excellent, I appreciate it Enom! Being a Fido user we get shafted with this update as our phones go into roaming. I'm already using your TMO versions now and liking it alot! Only thing is Fido is now disconnecting my data daily.

Looking forward to the update! Hopefully you'll have docs like this for the radio too.
[G1 Android Development] naack:
if i flash the radio and only the radio on the dream.. will it kill it?

why would i want to do that? i want the umts 850 that the rogers has. where i am the frequency is such as the rogers and AT&t.

any help on this would be appreciated.
[G1 Android Development] thorinside:
I messed with the m6 rooting program mentioned above (for the tattoo). The binary runs on my Dream, and eventually it will come up saying 'WIN!'... but then nothing happens beyond that. It just hangs. I suspect that HTC patched the kernel in the Rogers RUU to avoid this particular race condition.

I even changed the code, mentioned later in the Tattoo root thread to chmod a binary of my choosing... but no matter what I did, the binary never got chmodded even though the program output said 'WIN'. So, I'm skeptical that this hack is actually going to work for us. Bummer.
[G1 Android Development] enomther:
Yea sry guys ... I shoulda weighed in on this one ...

that exploit is specific to 2.6.29 kernels .... our beloved rogers dream is 2.6.27 ... so HUGE likelihood it won't work..

~enom~
[G1 Android Development] Paulska:
from the looks of it.

this is a guide to updating to the "updated" rogers radio/spl. but it looks like you already need to be on a EBI1 radio to begin with.

does dreaming.nbh converts all spl+radio+software to original rogers stock? EBI1???

**** If so no need to read the rest****

So lets say I have EBI0 radio installed and with that I have to use "RA 1.5.2" w/o "R"

once we flash the new radio my recovery wont work, which then im guessing id have to flash the "R" version of it.

so am i allowed to do....

d) It will flash through quickly with a message indicating "Extracting radio image ..." and then a message saying "Reboot via home+back or menu to complete installation".

** then fastboot flash v. "R" of Recovery???

will this complete the ". You should see "writing radio image ..." on the bottom ... followed by a reboot showing an "HTC" logo for a few moments ... followed by another reboot which returns to Amon_RA's recovery. Proceed to section-#8."

or am i gonna be stuck 1/2 way through the radio update?

can i extract the radio.img from the zip and just do all through fastboot?

* fastboot flash radio radio.img

* fastboot erase system -w

* fastboot erase boot

* fastboot erase recovery

* fastboot flash recovery 1.5.2R.img

or r the other files necessary in the radio_update.zip

sorry noob at all this stuff, dont have much time to read thousands of threads to become a pro just yet ;)
[G1 Android Development] XBrav:
So I'm doing directory browsing in ADB, came across this command:

flash_image

When I ran it, I got this:

usage: flash_image partition file.img

Can this be of any use?
[G1 Android Development] xaueious:
Try it.

Download the Amon_RA 1.5.2R recovery to your phone somehow and run that flash_image command. Replace with that filename.

Usage is: flash_image recovery A****1.5.2R.img

Doubt it'll work.
[G1 Android Development] XBrav:
Well I tried :(

I guess that's to be expected.
[G1 Android Development] H2O37:
I got a Dream here that I can brick if needed to find a solution, I got a refurbished Dream, in hopes of it not having the update applied. So if anyone wants to tell me what to do to it....or something,
[G1 Android Development] VGMStudios:
HI I just want to make absolutly sure I am doing this right.

I am a rojerks customer. I have not had data connection since they took it away.

my phone has been rooted and I am running Cyanogens ROM 4.0.4

my radio is 2.22.19.26I and HBOOT is 1.33.2005.

Is this guide for me?

now if it is and I install this new ROM will these theme work? I am running TED HERO Theme and really dont want to loose it.

please advise.

VGM out...
[G1 Android Development] enomther:
Hi VGM.

I've tried asking around about cyanogen's ROM's.

Since you're a Rogers customer, you definitely want to update your radio to avoid trouble with loosing your data connections.

Then please see here ...http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod

That cyanogenmod's wiki for Rogers users ... to get you on the latest CMMod ... browse through that ... it contains much of the same information in this thread ... with some different methods of deployment.

I tried asking cyanogen about the status of his ROM's on Rogers with EBI1/Radio-update ... never heard back (shrug).

As far as the TED theme ... you'll have to search the theme forums to see if one exists for the updated CM mod ... I don't really know.

Or ... you could flash my AOSP Donut based ROM here ...

http://xdaforums.com/showthread.php?t=538456

Which is kinda like a CMMod, but not really. Has *most* of the noticable feature sets anyways.

(Check out POST #3 for the themes I've ported to it)

....... and finally, if you're not experiencing any data disconnect issues, you may want to just leave your phone alone :) ... if you have Internet w/ your CM404 and are happy, why change right?

~enom~
[G1 Android Development] VGMStudios:
thank you so much for the reply. I really do appriciate all your help.

Thing is I do not have any internet connection on my phone case of my radio and version. :\

they cut me off and I refuse to use their crappy ROM.

I will take a look see from the links you have posted to what I can do.

thank you again.

I just needed confiration if I should go ahead with your upgrade to get my data connection back.

VGM out...
[G1 Android Development] Ninzoku:
So I've gone through all the steps in this thread. This is what I see in HBOOT now.

DREAM PVT 32B ENG S-OFF

HBOOT-1.33.2005 (DREA21000)

CPLD-4

RADIO-3.22.26.17

However, when I flash either theofficial rogers EBI1 rom posted here, or flash cyanogen and then flash the EBI1 kernel on top of it, (I used the one provided by briancrook.ca) I get stuck at the rogers screen when the phone tries to boot.

The furthest I've been able to get is by flashing openeclair, and then openeclair's EBI1 kernel. When I do this, the phone will boot into eclair, but it is missing the phone, contacts, settings and a bunch of other core apps are missing.

What can I do to fix this? I tried just re-flashing the radio again but that didn't do anything. Is it safe to try the whole procedure again? Pretty lost here.
[G1 Android Development] beav_35:
Did you wipe before flashing your rom?
[G1 Android Development] Ninzoku:
Yes, using amon ra's 1.5.2R recovery, wiped the phone, ext3, dalvik cache, battery settings and rotation settings. everything. And wiped all of these things between each attempt at flashing.
[G1 Android Development] beav_35:
That is very strange. First take out your sd card so we can eliminate that as a problem. Then go to fastboot and type the following commands:

fastboot erase system -w

fastboot flash system system.img

fastboot update <name of cm update.zip>

fastboot update <name of EBI1 port update.zip>

You will of course need to place the cm rom, port and this file in a place where fastboot can find it.

http://www.canadianandroid.com/d/cyanogen/htc_system_img_14721.zip
[G1 Android Development] Ninzoku:
Alright. I'll give that a shot when I get home, can't install the SDK on my work PC :(.

Will report back with results in a few hours!

Results:

fastboot erase system -w = OK

fastboot flash system system.img = OK

fastboot update update.zip however, returns:

Its right too, I opened the zip and no such txt files to be found. Feels like progress tho, do you know anything about these files?

Update:

Found info on another thread saying you can't use fastboot to flash a ROM. But I borrowed my roomate's SD card, tossed CM and the EBI port on it, and flashed. Phone booted clean! New SD card is in the mail.
[G1 Android Development] beav_35:
I thought something might have been funky with your sd card.

Glad u found the problem :)
[G1 Android Development] xaueious:
The update function in fastboot is a little different. It's not the same as the ones you flash in recovery. I haven't used it before. Not sure what it does.
[G1 Android Development] Ninzoku:
You should be fine, this was the setup I came from, just make sure you don't try to flash a ROM other than cyanogen before you do this, part of the reason I was having issues I think is because other roms include the proprietary google software that cyanogen got in trouble about. So when I was trying to go from OpenEclair to cyanogen it wouldn't work as I didnt have that base HTC system.img installed.

So if you're going from Cyanogenmod to Cyanogenmod, you shouldn't have any problems. (unless of course your SD card is pooched)

Also, sign the waiver. It works regardless if you update or not.
[G1 Android Development] LinK627:
Hello, would this guide work if i am a Rogers customer but with a T-Mobile G1? Please advise.
[G1 Android Development] LinK627:
I am getting an ID Model Incorrect! Update Failed. Please advise.
[G1 Android Development] TrainAss:
No, you would need a rooting guide for the T-Mobile G1. This guide is only for a Rogers provided HTC Dream. Not a T-Mobile G1.
[G1 Android Development] LinK627:
Thanks for the quick reply. Do you have a link for it? Btw, I have a T-Mobile G1 with the Rogers patch installed.
[G1 Android Development] beav_35:
If you have the Rogers firmware installed then you need to follow the guide to root the Rogers Dream.

http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
[G1 Android Development] slaman:
Just bought a Dream as a backup while I wait for my Galaxy S to be returned from Samsung... I bought it used and it was already running Cyanogen, but it keeps freezing at the Rogers logo on bootup... so just going to do everything myself from scratch.

I tried to push the files listed here:

http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched

but get stuck at this stage:

# adb push exploid /sqlite_stmt_journals

The error I get is "Read-only file system".. when I adb shell and navigate...there is no such file or directory...

Ideas?
[G1 Android Development] XBrav:
Can you get into recovery? Hold down Home+Power. You shouldn't need the exploid if you're already rooted...

As well, if you have the "#" when you use su on the shell, then you can skip to the "adb shell flash_image recovery /sdcard/recovery.img" or w/e
[G1 Android Development] slaman:
Would really appreciate any help... I'm essentially stuck... I can't reboot the phone, I can't get into recovery, and I can't get into any mode other than regular boot and fastboot...

Really need to fix this!
[G1 Android Development] XBrav:
Ok, if you can get into fastboot, which version of HBOOT does it say at the top? If it says 1.33.2005, do this:

1) Copy Amon RA's recovery image to the folder where you keep the fastboot program. Make sure it's the 1.7.0R one if you're putting it on a Rogers Dream, otherwise it won't work.

2) Rename the recovery image "recovery.img", makes it easier to type :)

3) In a command prompt, type "fastboot flash recovery recovery.img"

If it says something like 1.33.0010, then we'll have to reflash the device with the Rogers Stock 1.89.631.1 ROM, then root using the method you linked above.
[G1 Android Development] slaman:
HBOOT is 1.33.2005...

I think this is the problem... I'm not using the 1.7.0R version! I'm having problems finding it, but will look for it and retry...

EDIT: WORKED!!! Thanks!
[G1 Android Development] XBrav:
http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-dream-v1.7.0R.img
[HD2 Windows Mobile 6.5 Themes and Apps] mazzarin:
As a long time user of Dropbox, I wish there was an easier way to access my files instead of having to go on the web interface. I detest having to plug my phone into my computer, and actually as of recently, my computer locks up when I plug it in while the WM OS is running (go figure.) No mention of anything in the event log, just nothing. Bootloader works fine so my flash addiction is still valid :)

Anyways, I see options like Sugarsync (2 computer limit) or Live Mesh (no idea) as possible alternatives that have a WinMo client. Does anyone have any recommendations?
[HD2 Windows Mobile 6.5 Themes and Apps] Hojlind:
Do you find the m.dropbox.com solution bad? I personally think it works fine, but then again I havent used it very much :)
[HD2 Windows Mobile 6.5 Themes and Apps] mazzarin:
Don't get me wrong - it works, but a native app is better no?
[HD2 Windows Mobile 6.5 Themes and Apps] loquillo_rojo:
I've been using LiveMesh to sync severals folders in 4 computer and the Winmo and it works great.