[ROOTED] Rogers 911 patched Dream

geerfear · Oct 1, 2010

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.

ezterry · Oct 1, 2010

geerfear said:
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.

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.

geerfear · Oct 2, 2010

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.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\David>adb devices
List of devices attached
HT96YNH01989 device

C:\Users\David>cd C:\Program FIles\ADB

C:\Program Files\adb>adb push recovery.img/data/local
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

C:\Program Files\adb>

ezterry · Oct 3, 2010

geerfear said:
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.

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)

geerfear · Oct 3, 2010

Thanks (told you it was a newbie mistake). I've got it all up and running now. Thanks again for all the help.

slaman · Dec 15, 2010

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?

slaman · Dec 15, 2010

slaman said:
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?

As a follow-up, when I shell in and manually try to chmod 777 /sqlite_stmt_journals, I get a "No such file, etc"...

slaman · Dec 15, 2010

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.

ezterry · Dec 15, 2010

slaman said:
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.

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.

slaman · Dec 16, 2010

I managed to figure out the issue... I wasn't using the Rogers version of Amon_RA's recovery image...

Thanks!

capncark · Dec 19, 2010

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

xdjneo · Dec 19, 2010

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

Biker1bob · Aug 30, 2011

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

ezterry · Aug 30, 2011

Biker1bob said:
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

You will need an ebi1 kernel with the 3.22 radio, or to follow the fastboot instructions (ie my insructions) to install the 2708 radio/spl .. and the find a rom with the 2708+ kernel..

Topics

Topics

[ROOTED] Rogers 911 patched Dream

geerfear

New member

ezterry

Retired Recognized Developer

geerfear

New member

ezterry

Retired Recognized Developer

geerfear

New member

slaman

Senior Member

slaman

Senior Member

slaman

Senior Member

ezterry

Retired Recognized Developer

slaman

Senior Member

capncark

Senior Member

xdjneo

Senior Member

Biker1bob

Senior Member

ezterry

Retired Recognized Developer

Similar threads

New posts