yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] 12pollej:
What do you mean remove the space? Can I have an example?

I have also tried starting a connection with my HTC Device.

I successfully make the connection and then I try to excute the commands and it says this:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>adb devices
List of devices attached
HT95TNH03803 device

C:\Windows\system32>adb -s HT95TNH03803 shell
$ adb push spl-signed.zip/sdcard/1_33_2005_spl.zip
adb push spl-signed.zip/sdcard/1_33_2005_spl.zip
adb: permission denied
$
[G1 Android Development] cecilkorik:
Like ezterry said, you need a space between the file you are "pushing", and the path (on the phone) you are pushing it to.

The commands you are typing should look like this (added extra spaces to make it clear):

adb push spl-signed.zip /sdcard/1_33_2005_spl.zip

Also, it doesn't look like you're in the right directory. Your path says you are in C:\Users\Jess, but earlier in the post you said you downloaded the files to c:\AndroidSDK\tools\ ... if so, you should switch to that directory first before you run any of these ADB commands. The following command will switch directories for you.

cd c:\AndroidSDK\tools\
[G1 Android Development] 12pollej:
Okay I have got the first three commands to be pushed using ABD

How do I space this command?

adb shell chmod 777/sqlite_stmt_journals/exploid

Edit: Okay I typed it like this, and does it mean it worked?

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd c:\AndroidSDK\tools\

c:\AndroidSDK\tools>adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
919 KB/s (188246 bytes in 0.200s)

c:\AndroidSDK\tools>adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
569 KB/s (4712448 bytes in 8.086s)

c:\AndroidSDK\tools>
c:\AndroidSDK\tools>adb push exploid /sqlite_stmt_journals
969 KB/s (11917 bytes in 0.012s)

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals /exploid
Unable to chmod /sqlite_stmt_journals: Operation not permitted

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>
[G1 Android Development] 12pollej:
Next Step

Okay this is what I have got so far:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd c:\AndroidSDK\tools\

c:\AndroidSDK\tools>adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
919 KB/s (188246 bytes in 0.200s)

c:\AndroidSDK\tools>adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
569 KB/s (4712448 bytes in 8.086s)

c:\AndroidSDK\tools>adb push exploid /sqlite_stmt_journals
969 KB/s (11917 bytes in 0.012s)

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals /exploid
Unable to chmod /sqlite_stmt_journals: Operation not permitted

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>
c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>adb devices
List of devices attached
HT95TNH03803 device

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>adb shell chmod 777/sqlite_stmt_journals/exploid
Usage: chmod <MODE> <FILE>

c:\AndroidSDK\tools>adb shell chomd 777 /sqlite_stmt_journals/exploid
chomd: permission denied

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.

c:\AndroidSDK\tools>adb shell
$ rootshell
rootshell
Password (echoed):secretlol
secretlol
# chmod 666 /dev/mtd/mtd1
chmod 666 /dev/mtd/mtd1
# exit
exit
$ flash image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash: permission denied
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
$ exit
exit

c:\AndroidSDK\tools>

Does this mean I can continue onto the next step because when I tried to "flash_image recovery" and "adb shell chmod 777" there was no response from SDK
[G1 Android Development] 12pollej:
After this part of the rooting, my Rogers HTC Dream still works. Is that supposed to happen?

The next step is to boot into recovery mode and flash zip from sd card.

Here I perfected my steps and I think it is all good to proceed to the next step of flashing the zip from sd card:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd c:\AndroidSDK\tools\

c:\AndroidSDK\tools>adb devices
List of devices attached
HT95TNH03803 device

c:\AndroidSDK\tools>adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
905 KB/s (188246 bytes in 0.203s)

c:\AndroidSDK\tools>adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
437 KB/s (4712448 bytes in 10.507s)

c:\AndroidSDK\tools>adb push exploid /sqlite_stmt_journals
895 KB/s (11917 bytes in 0.013s)

c:\AndroidSDK\tools>adb shell chmod 777 /sqlite_stmt_journals/exploid

c:\AndroidSDK\tools>adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.

c:\AndroidSDK\tools>adb shell
$ rootshell
rootshell
Password (echoed):secretlol
secretlol
# chmod 666 /dev/mtd/mtd1
chmod 666 /dev/mtd/mtd1
# exit
exit
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
$ exit
exit

c:\AndroidSDK\tools>

Okay I flashed 1_33_2005_spl.zip from SD Card.

I know have HBOOT 1.33.2005 and radio 3.22.26.17

I now begin to place the appropriate files on my SD Card and I start my phone up normally. The screen is stuck on the rogers screen with FASTBOOT USB at the top left in red highlighted box.

PLEASE HELP!!!!
[G1 Android Development] canuckkat:
You didn't do anything to the OS itself per se. Basically, you went from a phone that you couldn't manually have root or "administrative" access to one that can.

@ezterry: Can you think of any reason why my phone won't flash the engineering SPL? I have root access from the exploid exploit and RA-dream-v1.7.OR as my recovery. It seemed pretty idiotproof...
[G1 Android Development] 12pollej:
I start my phone up normally now with HBOOT: 1.33.2005 and RADIO: 3.22.26.17but my phone is stuck on the rogers starting screen!!!!

WHAT DO I DO!!!!!
[G1 Android Development] ezterry:
good you erased system/boot via fastboot properly I assume.. now boot recovery and flash a rom so your phone has something to boot.. you can always use the "USB-MS toggle" option in ra-recovery to mount the SD card on your computer if you require to transfer update.zip files.

For more information follow the link (after reading the note) in section 'E' to the CM5.x upgrade instructions.. could use cleaning the last I looked (odd as it was cleaner when I created the rogers root instructions) but it will find you what you need to know.

-------------------------

FYI:If you do decide to install cm5.0.8 I recommend the following patches:

> garbled text patch to fix issues with connection bot/kindle and other applications

> exploid security patch to ensure no malware (Trojan) can access additional data or root without advertising it to you; with the exploit you just used to root the phone.

In both cases get the relevant update.zip (the DS version in the case of the garbled test); place it on the root of the SD card and apply from recovery after flashing cm5.0.8 normally)

You may also want to look into AWD1.0.1 with the system persistent option the rom works much smoother.

If you opt for CM6 rc3 has all of the above patches included.
[G1 Android Development] 12pollej:
I need to flash CyanogenMod 5.08, and the Google Apps and also the EBI1 kernel port to the root of your SD card but how do I do that without being able to transfer files to my SD?

Cause I can only access fastboot and recovery mode

Okay I did what you said and put the files on my phone. I wiped data/factory reset. Should I also wipe Dalvik-cache?
[G1 Android Development] ezterry:
You are appling the 1.33.2005 zip file; then rebooting with home+back?

after pressing home+back what text is added to the output?

also do you boot back into recovery? after the reboot I think there is also a log in /tmp can you get that?

unless I see an error I really can't tell you what is wrong.. There are other ways but they are not as idiotproof.. or as common.. or as easy

Maybe try installing recovery 1.6.2 via flash image in recovery (place the file on the root of your sd card boot into recovery and from adb shell or console run 'flash_image recovery /sdcard/recovery-RA-dream-v1.6.2R.img')

Its the older version of recovery but if something got corrupted with the current version may let you flash the hboot image... then you can resore 1.7.0 again with fastboot (after the fastboot erase commands in the process run 'fastboot flash recovery <path to 1.7.0-r recovery on your computer>'
[G1 Android Development] ezterry:
'fastboot erase system -w' already did all the wipes for you..

thus the note:

So no you just need to flash the rom, ebi1 port, and optionally patches.
[G1 Android Development] 12pollej:
Finally!!!!

Thanks so much for the support. I finally have a rooted G1 with Cyanogen 5.0.8.

After a lot of trouble, research and few heartattacks its all good.

Thank you, thank you and thank you!!!!! :) :) :) :) :)
[G1 Android Development] canuckkat:
Yeah. The output after the reboot is

Build: RA-dream-v1.7.0R
Formatting CACHE:...

Yes. Here's the log: http://pastebin.ca/1917086

I'll try the other ways you suggested in the meanwhile. :)

ETA: Still didn't work *sigh*

ETA2: Wow, I just noticed the "I:Boot status: invalid-update" in recovery.log
[G1 Android Development] ezterry:
Yes that and the error on the first block of cache when formatting it..

I think a bad block has it confused..

Ok 2 options.. first is simple:

1) Enter fastboot (turn on while holding camera, and press send when prompted)

2) run 'fastboot oem rebootRUU' .. phone will reboot from fastboot to ruu mode

3) run 'fastboot erase cache' (unlike erasing recovery this works)

4) run 'fastboot oem powerdown' this will exit ruu and powerdown

5) boot recovery and try to flash 1.33.2005 again..

If that fails we have to go to option 2.. using custom mtd to flash hboot.. but I'd rather avoid that
[G1 Android Development] canuckkat:
Bad news, it didn't work :(

recovery.log: http://pastebin.ca/1917142

Too bad we can't chmod the mtd block like we did for the recovery partition, or fsck the bad block.

ETA: Here's the fastboot stuff I did following your instructions.

D:\android-sdk-windows\tools>adb shell reboot bootloader

D:\android-sdk-windows\tools>fastboot oem rebootRUU
... OKAY [ 0.010s]
finished. total time: 0.012s

D:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 0.355s]
finished. total time: 0.356s

D:\android-sdk-windows\tools>fastboot oem powerdown
... INFOARM11->ARM9: powerdown
FAILED (status read failed (No such file or directory))
finished. total time: 0.008s
[G1 Android Development] ezterry:
The last option is using custom MTD to flash.. now I've simplified the process but there is some risk of bricking with this (So please only use this process as a last resort). The main process I've outlined on the wiki won't brick your phone unless its really the phone's time.

Please ensure you do not diverge from these steps or I will laugh at you if you brick your phone

Note: there is always a risk of bricking your phone with this process, so please try to avoid it. and READ ALL OF IT before starting.

Ok.. hopefully scared most people off.. so if you are still here I take it you really need the process and understand the risks.

==HOW IT WORKS

First you apply an update.zip that re-writes RA-dream-v1.7.0R (either CM version or normal version) to expose the hboot partition to recovery

In addition some utilities are installed in /cache (your current recovery, danger spl, and a script to finish the task)

Then we automatically reboot

You then call via adb the script; this (if all works correctly) restores your original unmodified recovery and flashes directly to hboot danger spl (1.33.2005)

on completion it boots into the bootloader for you to verify your status.

While it is proven to work this is an experimental process and needs to be treated with care.

==STEPS

1) Download: http://rapidshare.com/files/413181366/mtd_danger_flash_rogers_S.zip (MD5: 9a05fc70c68a5a1cf47a3e391ecc4d87)

2) put on the root of you SD card

3) ensure you are running a version of 'RA-dream-v1.7.0R' or this particular update.zip will fail

4) boot into recovery

5) flash mtd_danger_flash_rogers_S.zip from recovery (this will cause your phone to reboot back into recovery) After the reboot you can cause serious damage to your phone if you flash anything; so do not flash anything

6) once recovery is fully loaded run the following adb command:

adb shell /cache/hboot/extract.sh

The output if everything works will just be "all well" then the phone will reboot into danger SPL

ezterry$ adb shell /cache/hboot/extract.sh
all well
ezterry$

7) if in danger run 'fastboot erase cache' and you are done.. if the output contained anything other than just "all well" please also re-flash the recovery from fastboot, as the MTD table may be incorrect.

8) if you are not in danger it may be a good idea to re-flash the rogers 911 patched rom via nbh file; as recovery may have not been correctly updated with the normal partitions.

----

Good luck (any bricks that wont start the bootloader will require JTAG to revive.)
[G1 Android Development] 12pollej:
2.1 vs. 2.2

What is faster on the Rogers Dream? Android 2.1 or 2.2?
[G1 Android Development] ekramsam:
So far CM6 RC3 has been really fast and stable.
[G1 Android Development] ekramsam:
OVERCLOCK Rogers Dream

Can anyone tell me what kernel to use for overclocking my rogers dream (3.22) CM6 RC3?
[G1 Android Development] 12pollej:
Are you running CM6 RC3 on your Dream?

Would you recommend upgrading?
[G1 Android Development] ekramsam:
Yes on my rogers dream (3.22). I'm loving it, make sure you enable JIT, Compcache and lock home in memory.
[G1 Android Development] beav_35:
You can find overclock kernels here:

http://droidbasement.com/db-blog/

You want the ds_32a one.
[G1 Android Development] ekramsam:
Are you sure? I think dream is 32b and magic is 32a?
[G1 Android Development] ezterry:
3.x radios are most common on magic 32a.. but if its installed on a dream (as is common on HTC branded non-sense cupcake roms), or installed on a magic 32b: you still need the ebi1 kernel that some devs insist on calling 32a.
[G1 Android Development] lbcoder:
To clarify all that about the EBIx 32y.....

EBI0/EBI1 refers to the MEMORY LAYOUT.

Big memory devices, referred to as 32A (like HERO and MAGIC/32A) require the EBI1 kernel in order to address the full memory.

Small memory devices, referred to as 32B (like DREAM and MAGIC/32B) can run EITHER kernel, depending on the radio firmware installed, and it really makes no difference which is selected since an EBI1 kernel doesn't add much to the memory.

I *think* that 32A's are able to run with EBI0 radio and kernel... just that you have to give up 128 MB of RAM to do so... which is a pointless trade-off.

The ONLY REASON for ANY DREAM to run an EBI1 radio and kernel is if the service provider is a douche that turns off service if they detect the wrong radio version. I believe that there is still an opt-out form available, or they may have given this up by now if they feel that the BS has been fulfilled.... if the device doesn't BENEFIT from the EBI1 stack, you are probably better off with EBI0 since most dream ROMs are built for EBI0.
[G1 Android Development] Super S:
Have you been able to get MMS working? I have not been able to on either my Dream nor my Magic when running CM6 RC1,2 or 3. CM5 it works fine.
[G1 Android Development] ezterry:
Please take note that the lattest version on CM wiki will either

1) may lead you to inadvertently brick your phone by linking to many external guides rather that a more contained process

2) asks you to re-flash the radio when there is no reason to (and with stock SPL?)

3) omits many steps in my process that may very likely prevent CM5/CM6 from cleanly booting on your rogers phone or cause additional future issues.

I highly recommend the older version:

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

Please take note; I will be moving the guide to XDA and leading people away from CM-wiki until some things are sorted out there for all Android related guides

Edit:

Just moved the guide here: http://xdaforums.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams

And now I think we can change some of it to have screen shots
[G1 Android Development] canuckkat:
ezterry$ adb shell /cache/hboot/extract.sh
all well
ezterry$

I get "bad hboot" here. *sigh*

I just followed the new Cyanogen Mod install guide thing and CM 5 seems to work fine so... bleh.

This is my warning to stop dropping my phone >.<

ETA: I just rebooted and now it just hangs on the rogers logo, but it's not bricked since I can get into hboot and recovery. Heh.

ETA2: Installed the mandatory update rom and phone is fine again. Grrr... *shakes fist* I guess it really doesn't want to have CM on it.
[G1 Android Development] ezterry:
Hrmm.. that means the hboot.img got corrupted there is something odd about your cache partition ... in a very scary way

Don't worry just means you need to run 'fastboot erase system -w' and 'fastboot erase boot' oh wait you need 1.33.2005 for that;

(don't think the new guide is right. I say it because it will either make the process harder now or at some point in the future)
[G1 Android Development] canuckkat:
I wish it was possible for me to RMA my phone, but it's definitely past the one year mark from when the original person bought it.

Plus, even if I could, what would I say? I was being a dev and poking around with the partitions and found out that my cache partition is broken? Hmmm... I guess I could call tech support and ask.
[G1 Android Development] geerfear:
I've been trying to follow the guides (both here and at Cyanogen Mod) for rooting my Dream, but can't seem to get it to work. I'm sure I'm making a newbie mistake, but not sure what it is. When I try to run the step chmod 777 exploid I get a message saying there's "No such file or directory". I was also unable to move the files onto the SD card using the push command, so I just moved them into the folders manually. I've been assuming that the references to running the terminal meant cmd.exe, so that's what I've been using, as well as trying powershell. Any ideas what I may be doing wrong? Thanks.
[G1 Android Development] ezterry:
Um... only one file was on the SD card... so this is likely the issue..

Do not mount the SD card on your computer

> Make sure ADB/Fastboot is installed;

> put all the files to adb push in the same directory as adb;

> cd to that directory in cmd.exe

> last run the commands as listed in the xda wiki (no edits please unless you renamed something)

If adb push fails or any other errors happens copy it out of the cmd.exe window and add it to a post.
[G1 Android Development] geerfear:
I figured out part of the problem (I hadn't navigated to the ADB folder correctly) and succeeded in pushing the exploid file. However, when I try to push the recovery image, I just get the ADB directions (see below). Does this file just go to the data\local folder on the SD card (i.e. can I move it manually)? Thanks again for the help.
[G1 Android Development] ezterry:
1) They don't go on the sdcard, they go to the internal phone nand memory.

2) you removed a space from all those adb commands (its 'adb[space]push[space]<file on pc>[space]<location on phone>') since adb didn't know what you wanted it kindly printed a help message explaining how to use adb

(if you are still confused read this thread starting here)
[G1 Android Development] geerfear:
Thanks (told you it was a newbie mistake). I've got it all up and running now. Thanks again for all the help.
[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://xdaforums.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams

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... I don't even see the /sqlite_stmt_journals folder on the phone...

Ideas?
[G1 Android Development] slaman:
As a follow-up, when I shell in and manually try to chmod 777 /sqlite_stmt_journals, I get a "No such file, etc"...
[G1 Android Development] slaman:
Ok, so I skipped the exploid step and just flash_image using Amon_RA's recovery file... powered down.... then when I tried to boot into recovery mode (Home+Power on), I just get the Rogers screen...

same problem I was facing before... just can't get into Recovery.
[G1 Android Development] ezterry:
Your mistake is taking steps for going from the rogers stok firmware to root... when you are not running said firmware.

All dream firmwares can run on all dream devices so I've got no clue whewre you are or are going to.. just that there is a rogers silk screen on the back of the battery case.
[G1 Android Development] slaman:
I managed to figure out the issue... I wasn't using the Rogers version of Amon_RA's recovery image...

Thanks!
[G1 Android Development] capncark:
I can't seem to get the recovery file to install. I'm not sure if I was able to push the files. My device is recognized in adb devices but I am getting this back when I try pushing the rooting files

adb push spl-signed.zip /sdcard/1_33_2005_spl.zip

980kb/s (0 bytes in 188246.000s)

adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local

887 kb/s (0 bytes in 4712448.005s)

adb push exploid /sqlite_stmt_journals

744 kb/s (0 bytes in 11917.000s)

xploid seemed to run and exit fine but I get permission denied at

"flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img". I would think that it is due to the whole 0 bytes being pushed but I am a total Android newb. I'm sure it is probably a bonehead mistake on my part. Any suggestions on what I might be doing wrong?

I have a rogers dream

build #1.89.631.1 146733

firmware 1.5

dream pvt 32B ship s-on d

hboot1.33.0010 (drea21000)cpld-4

radio 3.22.26.17
[G1 Android Development] xdjneo:
Maybe your missing these steps

Rename Amon_Ra's Recovery Image to simply recovery.img

Turn on USB Debugging (Settings » Applications » Development) > Did you do this on the phone?

adb push recovery.img /data/local

adb push exploid /sqlite_stmt_journals

adb shell

cd /sqlite_stmt_journals

chmod 777 exploid >>> missing this most likely

./exploid
[G1 Android Development] Biker1bob:
Anyone still looking at this topic..

NEED help

successfully rooted using guide from XDA..

but now I cant get any rom image to load? I am stuck on my Rogers screen.

help??

James