yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] FlyingToilets:
@lbcoder and exterry, Yeah I had a feeling it might be the radio, but this is the first time I've touched my dream in seven months so I've forgot a lot and wasn't completely sure haha. Thanks for your quick replies though, I'll probably just downgrade my radio then. Is there any advantage to the new radio? Or was it made just so rogers could keep track of who did and didn't do the 911 update?
[G1 Android Development] Theros:
Just successfully got a oem replacement dream that had the e911 fix applied at the factory rooted with this. Huzzah!

EDIT: Now, while this is great for our needs, it should most likely be patched _immediately_. I get the feeling that it could be utilized to create all sorts of malicious applications.
[G1 Android Development] songoku2:
Thanks I was about to JTAG

Works great!!!! :D
[G1 Android Development] Super S:
I'm so happy I could cry. Donations to those who made this possible will be on there way :D :D :D
[G1 Android Development] eEKBAh:
Ok, so I downloaded everything got started and all is well until I get to the part when it reboots back into recovery and the next step says to type "adb reboot bootloader" so I do that and I keep getting "error: closed". In the instructions it says it may take a moment, but I waited over 10 mins and still the same message. I rebooted and restarted the process from the point of going into the shell, log in chmod, flash_image recovery, and rebooting and flashing the 1_33_2005_spl.zip which again all goes perfect but still the same "error: closed" message every time I try to adb reboot bootloader ...

Has anyone else come across this and if so have you fixed it and how?

What am I missing?

Probably doesnt help that its 5:30 am and I am still up because I am excited about this.
[G1 Android Development] raymar23:
WOW!!!!!

OMG AWESOME..Been waiting FOREVER, Thanks all who made this happen/possible

:eek:

WOOT we have ROOT again
[G1 Android Development] ezterry:
The command is 'adb shell reboot bootloader'

Don't get stuck here we are just looking to get to the fastboot screen.. The commandline simplifies needing to hold camera after pressing reboot to try to catch it before the rogers rom boots again..

If its failing for you turn on the phone while holding camera to get to the bootloader then press send as prompted to enter fastboot.. then continue with the steps after the reboot bootloader.

Yes hack the phone while at least half awake :-P
[G1 Android Development] eEKBAh:
Thanks ezterry... lol it was definitely a 5 am issue.

Slept, then typed "shell" in between the command and all is well.

Now running CM5!
[G1 Android Development] asb123:
Will this work on 911 patched magic phones? what changes would I make?
[G1 Android Development] ezterry:
Yes I agree..

http://code.google.com/p/cyanogenmod/issues/detail?id=1923

exploid .. almost certainly will work..

However the steps remain nearly the same as the goldcard method in use today (hero recovery/1.76.2007 SPL then use fastboot to flash 3.x radio + 1.33.20** SPL)
[G1 Android Development] Suilad:
Hey Terry. I was one of the people who PM'd you about a jtag, but I am much happier than you discovered this method to softroot the phone. The root & installing CM5 worked perfect for me with no problems! It's like my Dream is a new phone now.

Thanks a lot for doing this! You rock
[G1 Android Development] idreamz:
Root error.

congrats to ezterry for finally figuring this out! i no longer have to find someone to jtag! :D

i have dled all the components and have the sdk mgr.

i was in the middle of pushing adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local and and DAEMON Tools Lite error in command line. error appeared.

Is there anyone that can help me finishing rooting my phone?!

Thanks and much appreciated!
[G1 Android Development] idreamz:
root

im stuck at the $ rootshell it keeps sayin rootshell: permission denid

any help?
[G1 Android Development] XBrav:
Did you type cdmod, or chmod? They reprogrammed their command line error to read "Permission Denied" instead of "File not found"
[G1 Android Development] idreamz:
stuck again -_-

im past that now im stuck at # enter the shell: adb shell (will return a '$' prompt)

# in the shell run rootshell it shows permission denied when i type rootshell
[G1 Android Development] ezterry:
Then you did not trigger a hotplug event (the unplug/replug of the USB wire) after running exploid, or forgot to run it..

Start from the beginning (anything duplicated wont cause any harm)
[G1 Android Development] cphil:
Hello,

I am new to rooting, and was finally able to root my rogers htc dream after about 5 hours yesterday *thanks Terry!*. I was running the newest stable cyanogen with no problems, until last night it started to force close non-stop. I was unable to exit the force close screen, so I powered off the phone. As a result, powering it back it on, only leaves it hanging on the rogers logo. I have left it on for 6+ hours, and nothing happens.

Can someone please help me. Thank You.
[G1 Android Development] ezterry:
We will need more details than that to fix the root cause and its likely a generic cm issues (many better threads, or the cm wiki may provided better responses than only those rooting a e911 patched dream)

That said when rooting did you run those fast boot erase commands? Regardless I recommend running them now and reinstalling cyanogen mod (5.0.8 update, garbaled text patch see my sig, gapps, ebi1 port file in that order)

Questions are you running apps2sd if so did you take out the sd card (this can cause issues)

or are using old ext from prior to the 911 patch.. if its an old ext partition wipe it (ra recovery has a wipe ext option)
[G1 Android Development] lbcoder:
Try booting it into RECOVERY or FASTBOOT.

There's no point in just leaving it bootlooping for 6 hours.
[G1 Android Development] cphil:
Hello, Thanks for replying.

I forgot to mention, I have tried and pressed menu and power, and did a nandriod recovery, said it was finished. Went back to rogers logo for 30+ minutes. I have tried it again, and now it says "error: run' nandroid-mobile.shrestore' via console. I do not know what that means.

Also in fastboot, it says dreadiag.zip, no image found. Could that be the problem?

Thanks
[G1 Android Development] lbcoder:
It all means that you should quit screwing around and install an EBI1 ROM or a 2.x radio and an EBI0 ROM.
[G1 Android Development] cphil:
Okay I have reflashed the rom and it works for now. Thank You

I guess that is what you mean by installing an EBI1 ROM or a 2.x radio and an EBI0 ROM?

Is there something I can do to prevent this from happening again in the future?
[G1 Android Development] lbcoder:
Sure... any time you change the firmware to be incompatible with the image on the device, you need to reinstall something that is compatible.
[G1 Android Development] steve1326:
Stuck on "Install Recovery" step

I have tried this now a couple times, and always with the same result: Everything goes fine up to Step C.4.

But at step C.5 (where you flash the image), it gives me read errors just like the article indicated, but it does so when I try it the second time as well. And it doesn't just throw a 3 lines of errors. It throws 350 lines of errors. Some of them are read errors, some are write errors, and some of them are re-read errors. The process ultimately finishes with a "error writing recovery: No space left on device" error, and I am back at the $ prompt.

It is the same thing both times. Anybody experience similar? Any ideas? This is on a Rogers HTC Dream
[G1 Android Development] ezterry:
Yuck.. I assume recovery fails to boot as well?

If so we can try erasing recovery with fastboot (one of the few things the perfected spl can do)

1) Enter fastboot (boot+camera press send when prompted on screen)

2) run 'fastboot oem rebootRUU'

3) the phone will now enter ruu mode: run 'fastboot erase recovery'

4) last run 'fastboot oem boot'

When you are back in the rogers rom 'rootshell' and the recovery image ought to still exist so just pickup the process at flashing recovery.

EDIT: Note apparently fastboot erase recovery fails... fastboot erase cache works... sigh

If this fails again try running the official ruu or nbh for the rogers rom and start from the beginning.
[G1 Android Development] steve1326:
Tried what you said, but once I got to step 3 ("fastboot erase recovery"), it errored as follows:

And it is true: I cannot get to recovery (although the phone does boot up normally if I let it)

I guess the next step is to try re-applying the Rogers patch and try your routine from the top
[G1 Android Development] ghyslainlafleur:
:)

Thank you everyone, i now have two rooted HTC Dream to mess with :)

Is there a tip jar for everyone involved ?
[G1 Android Development] ezterry:
No but please redirect any part of the donations for the root you are thinking ought to go to me to the one who patches this exploit. {issue 1923 on the CM tracker}
[G1 Android Development] asb123:
you want this exploit to be gone?
[G1 Android Development] ezterry:
on my rooted phone yes please make it go away...

I want to be able to access root.. maybe I want a trusted app (currently only setCPU) to have root.. but your silly game with a rootkit hidden in it ought not be allowed into root on my phone.. worse it wont even ask me permission.
[G1 Android Development] ayrokid:
Hey,

I havent tried rooting yet but I AM VERY TEMPTED.....

@ezterry: I read about the exploit thingi but I couldnt figure out what is all this about !!

so what is this exploit thingi? Please explaing the risks and stuff...Thanks :)
[G1 Android Development] tbone14:
Noobie needs lots of help

I am trying to root the HTC Dream on an old Windows XP laptop (my primary computer is a non-Intel Apple). So, my knowledge and expertise is fairly limited. However, I can follow directions well, and have read multiple websites exploiting the Rogers 911 patched update, including the wiki page.

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

I have downloaded all the files, and then moved them into the "tools" directory folder. I have also installed the necessary USB drivers, as my computer is able to view my phone as "Android Composite ADB Interface" via USB. I have also enabled USB debugging on the phone. Finally, my phone appears in the command shell as "HTXXSNHXXXXX" after typing "adb devices".

My command line is listed as:

C:\android-sdk_r06-windows\android-sdk-windows\tools>

When I try to push the files via the command:

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

I get the error:

cannot stat 'spl.signed.zip': No such file or directory

Can someone help me out and point me in the right direction? I think I'm missing something simple, but I can't figure it out. I've spent a few hours and can't get past one of the first steps. :( Hopefully after getting past this, it will go much smoother....
[G1 Android Development] ayrokid:
Re:Noobie needs lots of help

I am no root expert...but try this....when u r at the C:\android-sdk_r06-windows\android-sdk-windows\tools> then type "dir" without quotes. This should show you all the files you have in that directory. If you can't see the "spl-signed.zip" in there then find where that file is and put it in tools directory. If you can, then I dont knw :confused:

I hope this helps ! !
[G1 Android Development] ezterry:
I think you are confusing things.. the exploit is a flaw in the system that allows a regular Linux user to esculate to root without permission. This flaw exists is all roms for the HTC dream (and most if not all other android devices) so it's hardly more of a risk in a custom rom than in a outdated stock one.

Think of it this way you have a large solid steel door blocking unwanted people (non root users) from accessing your home (root) and you lock yourself out.

In the process of breaking back in you notice your back door to your house has no lock besides a hook on a already partly ripped screen door.. that you, or anyone else, can squeeze through.

The risk of pushing into the screen door to your own house and redecorating (installing a custom mod) is fairly safe.. as long as the piano doesn't fall on your head (install a radio/spl other than the one I specified via recovery) but at this point in time you can't secure that back door while redecorating (the thief can steel things from the cyan painted house just as easy as the original red one).
[G1 Android Development] steve1326:
Wow! That worked! I re-applied the Rogers patch (which brought the phone back to a pristine state), and then went through your process again, which worked exactly as described. Outstanding!
[G1 Android Development] ezterry:
Most important for all the partitions (including recovery) the ruu flashes it is the equivalent of 'fastboot erase <partition>' and 'fastboot flash <partition> <partition>.img' meaning it fully reformatted recovery for you cleaning the out of status blocks causing the issue.

glad all worked out
[G1 Android Development] nemesishaven:
Phenomenal news. Thanks ezterry for doing the legwork on this one! I know what I'm doing tonight!
[G1 Android Development] zoltrix:
Why does Section D Step 7 say the following?

Verify the following:

* HBOOT: 1.33.2005

* RADIO: 3.22.26.17

Arn't Rogers Magic's 6.X radio?
[G1 Android Development] ezterry:
Good thing the process is for the DREAM not the magic.. because otherwise I'd be doing something really risky installing a 1.33.* SPL with the 6.x radio..

If you want to root the magic either use the signed leaked rom with a gold card like every one else:

http://xdaforums.com/showpost.php?p=5526163&postcount=1

Or be a dare devil and risk the Magic (w/ 6.x radio) version of the exploid hack:

http://xdaforums.com/showpost.php?p=7340733&postcount=306

(In theory it will get root.. the question is did I miss something in the process having not used a rogers magic myself.
[G1 Android Development] zoltrix:
oops lol

someone linked me to it and i just assumed dream and magic were so similar that it worked. Thanks
[G1 Android Development] nemesishaven:
I ran into the same issue as steve1326, and reapplying the Rogers Update then going through the whole process again worked for me. Now rockin' CM5.0.8. I love my phone again.
[G1 Android Development] ayrokid:
@ezterry...Thank you for the explaination :)

So when you said "theif can steal through back door"....what sort of risk do I take, I mean what data can they steal? :S Also can they access any service in my device without any/my aproval? ! I may sound like a freak I have few stuff on the phone I dont want other ppl so have...but I WANT TO ROOT SO BADLYYY lol...

Thank you again :)
[G1 Android Development] XBrav:
Ayrokid,

Basically, think of it this way:

Your phone is your house. Root is your key. If you don't have your key, you can still play with the stuff on your front lawn. If you root, no more lock on the doors! You can go in and out.

However, if someone else can enter the property, say, through a backdoor trojan app or something (none yet, but may come up in the future), they can also enter the house, and mess with your stuff.

Basically, if you give an app root access, you just invited them in, said "Have fun", and are hoping everything is still there once you leave.

So be careful which apps get superuser status.
[G1 Android Development] ayrokid:
OMG YOU ROCK XBrav :)

So I can choose which app gets root access and which one does not?

So say I install custom mod...then I can select which apps should have root access...or any app that is installed (Apps already in the rom) with custom mod already has an root access?
[G1 Android Development] :
man i have g1 i have installed 1.7.0 recovery,spl is 1.33.2010,was having 2.22.23.02 radio i have installed this 3.22.26.17 radio but it get stuck on slash screen plz i need help
[G1 Android Development] beav_35:
You need to flash the 1.7.0R recovery from fastboot then an EBI1/32A port for your rom. Why are you trying to flash a EBI1 radio on your G1 anyways?
[G1 Android Development] -Maverick-:
I was wondering the same, wouldn't it make more sense if you have a G1 to stay with the original EBI0 radio? Unless you live in Canada, but then again why not use a Rogers DREAM and save yourself the trouble????
[G1 Android Development] canuckkat:
So I'm following the guide and when I get to "adb shell reboot bootloader" the info says:

DREAM PVT 32B SHIP S-ON d

HBOOT-1.33.0010 (DREA21000)

CPLD-4

RADIO-3.22.26.17

Jun 2 2009,21:33:16

which seems to indicate that the SPL didn't get flashed properly or something?

@lbcoder: The Robbers Dream should on Wind Mobile. What's the difference between the G1 and the Dream anyways?
[G1 Android Development] beav_35:
Yes, it looks like your SPL didn't get flashed. Reboot back into the recovery and try flashing it again.
[G1 Android Development] canuckkat:
I've already tried 3 times. Haven't gotten any errors (besides the initial mtd ones).

And yes, the md5sums match.

I wish commands could be verbose *sigh*
[G1 Android Development] canuckkat:
Wow. Thanks for clearing that up. Good thing that $100 prepaid card is more than enough for me for the year.

I guess I really do need to get that Nokia N900 I have my eye on. *rolls eyes*

Anyways, any idea on my problem? Should I try flashing the rom? (although I suspect that will brick my phone)
[G1 Android Development] ezterry:
You are in ra-recovery? How are you restarting after flashing the 1_33_2005 spl? What is said on the screen after applying the zip? Is anything in /cache/recovery/log before restarting?
[G1 Android Development] steve1326:
I had issues at first as well. What I needed to do was re-apply the Rogers update, which essentially brought the phone back to square one.

This resulted in a squeaky clean phone.

Once I had done that, the procedure worked exactly as described
[G1 Android Development] raymar23:
Was wondering if this same process might work on a Relish GSM Hero. With the hero recovery and NOT installing the SPL.

If I'm not mistaken the Dream, Magic, and Hero should have the same files of the OS in same places (if that makes sense?)

Thanks in advance for help. :)
[G1 Android Development] lbcoder:
It *should* work on virtually *EVERY* (i.e. most or all) android phones with ARM cpu.
[G1 Android Development] calgore:
Heya

to get too the point there seems too have been a problem along the line somewhere not quite sure I followed the guide and it was all gravy till the end after I powered down through fastboot and everything was grand but when i tried too turn the phone back on it wont go past the rogers screen =/ attempting the whole reinstall the rogers update and its just finished annnddddd no dice.... woo its on but slow good sign I shall try they whole process again then... in the morning...

my radio seems too be correct still but the hboot is wrong bah
[G1 Android Development] ezterry:
You need to apply the 1.33.2005 spl, look at the bottom of the screen: It will tell you an error or to reboot with home + back to complete the installation. You must then reboot with home + back or the top reboot option in the recovery menu.

If you skip the home + back reboot and skip to 'adb shell reboot bootloader' the phone will not flash the spl.

Also when flashing the cm or other rom make sure its a ebi1 kernel/port file (some call it a 32a kernel) or it will get stuck on the splash screen (rogers logo unless you changed it)
[G1 Android Development] xaueious:
From a Taiwanese dev. Reports to work on various Android phones. If it works, great. If not, oh well.

1 click root APK:

http://bit.ly/aa4jxJ

Is this the same exploit? Might make life easier for some

Dev blog (down?)

http://blog.23corner.com/2010/08/04/夏日-android-小品-按一下-root-手機-universalandroot/

Exploit based on this

http://xdaforums.com/showthread.php?t=736271
[G1 Android Development] canuckkat:
Yes, yes, the whole printout is

The log is here: http://pastebin.ca/1912954

I'm gonna try applying the Rogers update and see if it'll help.

ARGH! NO WORKIES! *headdesk*
[G1 Android Development] calgore:
I'm pretty sure it did work properly before i reinstalled the rogers update orginally the hboot was correct

should I already have the files for the cm rom on the phone well doing this?
[G1 Android Development] calgore:
SUCCESS! yes it would appear I missed the line "This will install the engineering SPL and prepare the phone for a custom rom" ^^; my bad it is perfect and awesome been waiting a looonnngggg time for this heh
[G1 Android Development] xdjneo:
Works like a charm, thanks everybody

Works like a charm, u guyz rock, I am the happiest campless camper in town!

One thing I got consfused was the the ebi1 32A kernel even though I have a 32B, when I flashed it without the kernel, it didn't boot and froze at the rogers screen, so then I flashed it with the 32A kernel and it worked.

Can somebody shed a little light on this.

Thanks again everybody
[G1 Android Development] ezterry:
Ebi1 = 3.x radio

Ebi0 = 2.x or 1.x radio

There is no such thing as a 32a kernel (even if sometimes called it: as 32a magics are the first devices they shipped on)

Also note there is no such thing as a 32a dream
[G1 Android Development] Dhruv94:
hi guys, i was wondering if anyone of you could help me out.. im a complete noob at android, (ex-WinMo) and i was just wondering how i am to root my device.

i have a htc dream and it is on that new 911 patched firmware, i downloaded all the files and saved them all in a folder call ' Dream hacking"

inside this folder i also have the fastboot.exe and the adb.exe with its .dll files

i places the folder in the root of my c drive so with the windows folders etc.

now when i open the cmd promt window and change it to the directory etc.. i try to run the first command: adb push spl-signed.zip /sdcard/1_33_2005_spl.zip and i get the out put of "error:device not found'

on the phone i have enabled debugging mode and its showing "Removable Disk(d:)" in my computer , which i know for a fact is the microsd card of my phone..

so my question is.. what am i doing wrong guys..

id really appreciate the help...

thank you
[G1 Android Development] xdjneo:
What your probably missing is the Android SDK + Drivers

http://wiki.cyanogenmod.com/index.php?title=Install_the_Latest_Android_SDK

Give this a read and follow the instructions at the bottom of the page for windows
[G1 Android Development] Dhruv94:
oh man thank you SO much..

i was wondering about this aswell.. gonna try it now (:
[G1 Android Development] Dhruv94:
ok so i tried what you suggested.. and now it says.. : " failed to copy **************************" Permission denied"

im so confused.
[G1 Android Development] ezterry:
If you are using adb to push something to the sdcard, the sdcard must not be mounted on the computer, (ie don't select the options to copy files to/from the computer on your phone)
[G1 Android Development] Dhruv94:
thhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhaaaaaaaankkkk yooou =d
[G1 Android Development] 12pollej:
Chmod

When I get to the step:

adb shell chmod 777 /sqlite_stmt_journals/exploid

It says:

unable to chmode adb shell chmod /sqlite_stmt_journals/exploid: no such file or directory

HELP!!!???

And for the previous steps:

adb push .... and etc

it comes up with all this information on how to use SDK

Is that whats supposed to happen????
[G1 Android Development] ezterry:
If you are getting the help statement something is not correct with the command line..

Try from the top.. if it fails again copy the contents of the console window into pastebin for us to verify..

However first you may do well by reading the help statement and making sure the commands you are issuing make sense.
[G1 Android Development] ezterry:
Check that you didn't remove the space between local and remote file name/path on your adb push commands..