Database Users

Boot from SDcard

Hello everyone. I would first like to apologize for my not so good English. I do not know whether it is the right forum, I write in? but now I'm trying
My problem is that my mobile becomes to restart again and again, I have tried to update from SDcard. but when I hold "Home" and "power" key and enter the menu, type the following at the bottom with yellow lettering:
E: Cant't open / cache/recovery/command.
When I try to press apply sdcard: update.zip writes the following:
- Install from sdcard ..
Finding update package ...
Opening update package ..
Vertifying update package ...
E: No signature (769 files)
E: vertification failed
Installation aborted.
Hope some can help me.
flapz

can you provide more info such as spl, what kind of pvt board you have??? by going into fastboot
End key + Back

minogue said:
can you provide more info such as spl, what kind of pvt board you have??? by going into fastboot
End key + Back
Click to expand...
Click to collapse
Excuse me, but I am totally new in this.
When I press SDF and look where it says pvt: 32A ship S-on H.
what do you mean by pvt board?
anything green in the top are:
SAPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
thanks for quick response
flapz

is your phone rooted by any chance???
ok well. you need to download a 32A rom for your Phone here is a link to one:
http://rapidshare.com/files/258127559/JACHeroski2.7.3-Magic32A_signed.zip
place that on your sdcard and name it "update.zip" without parenthesis.
you need to find a way to put it on your sdcard using a memory card reader or something since your phone is not bootable. i think you can also do it using adb??? but you will need to download the sdk in order to do so.

better explain from the beginning!
I put Fatal1ty_Hero-Full_v1.4-Rogers-signed into my mobile, thought it was a bit slow, I would like to start from 0 I went into options and would "restore factory settings".
So it began the just reboot up to several times, the problem is that I can not come to the "desktop". Has the SDK on my computer.
I try just to get the ROM you linked to, and try again, so I write when I've tried. Thanks again.

flapz said:
better explain from the beginning!
I put Fatal1ty_Hero-Full_v1.4-Rogers-signed into my mobile, thought it was a bit slow, I would like to start from 0 I went into options and would "restore factory settings".
So it began the just reboot up to several times, the problem is that I can not come to the "desktop". Has the SDK on my computer.
I try just to get the ROM you linked to, and try again, so I write when I've tried. Thanks again.
Click to expand...
Click to collapse
hmm didnt quite get the last part.....but if you download the rom i linked you to..
just flash it using the same steps you followed to flash the Fatality-Hero Rom

rename the downloaded rom as update.zip and place it in the tools folder of your sdk
now boot into fastboot and do:
fastboot push update.zip /sdcard/update.zip

How can I use the SDK when I can not start my mobile? When it comes to the "hero" start screen it just restarts.

How do I contact the phone in comd promt? when I write adb devices can not I see my HTC. I can not push it on SDkort. But I can not do it in my card reader?

When I rename the ROM you just have linked to update.zip and apply SDcard: update.zip it write now:
- Install from sdcard ..
Finding update package ...
Opening update package ..
Vertifying update package ...
E: No signature (739 files)
E: vertification failed
Installation aborted.
But write it first:
E: Cant't open /cache/recovery/command. <--- What does this mean?

flapz said:
When I rename the ROM you just have linked to update.zip and apply SDcard: update.zip it write now:
- Install from sdcard ..
Finding update package ...
Opening update package ..
Vertifying update package ...
E: No signature (739 files)
E: vertification failed
Installation aborted.
But write it first:
E: Cant't open /cache/recovery/command. <--- What does this mean?
Click to expand...
Click to collapse
what recovery image are you using to do this???

minogue said:
what recovery image are you using to do this???
Click to expand...
Click to collapse
daldroid-recovery.img - but it is in the SDK and I can use it when I can not start my mobile?
1000 thanks for your patience

download this recovery image
http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
make sure your phone is off and then turn it on by pressing and holding End + back key,
connect your phone to your computer and do this:
fastboot boot recovery-RAv1.0H.img
after that you apply sdcard:update.zip" from the menu
--------------------------------------------
again in orer to run the fast boot command you need to have the sdk and cd into the tools folder of the sdk....
go to Start>Run - Type in cmd:
then do "cd C:\path to android sdk tools folder
for example mine would be
cd F:\android-sdk-windows-1.5_r3\android-sdk-windows-1.5_r3\tools

flapz said:
daldroid-recovery.img - but it is in the SDK and I can use it when I can not start my mobile?
1000 thanks for your patience
Click to expand...
Click to collapse
your phone turns on right??? so by start im guesing you mean not load completely...
then just follow the steps from my above post... and place the new recovery image in the tools floder of your sdk..

Now I understood you. MANY MANY thanks
I think my mobile is running now

I owe you a BIG favor now, would like to give a cold beer, but I am in Denmark

flapz said:
Yes i turns on.
My SDK is : android-sdk-windows-1.5_r2 . does it matter that it is r2 and r3
When i turn it on by pressing and holding End + back key, and connect my fone.
there is a red box that says fastboot usb, and then there are the following:
<vol down> Hboot mode
<send> Reset device
<action> Restart to Hboot
<menu> power down
how do I use : fastboot boot recovery-RAv1.0H.img
I am really glad you want to help me.
Click to expand...
Click to collapse
ok see. now your very close...
well since it says Fastboot Usb - it means the phone is connected which is good. just leave that as it is. now lets move on
r2 and r3 dont matter its just different version. mine is a newer one.
do you know the location of the sdk / where it is installed???
if you do all you need to do is the following:
download this recovery image
http://rapidshare.com/files/24898357...ry-RAv1.0H.img
and make sure you save it in the tools folder of your sdk.
go to Start> then Run - Type cmd and then click enter
then type "cd C:\path to android sdk tools folder
for example mine would be
cd F:\android-sdk-windows-1.5_r3\android-sdk-windows-1.5_r3\tools
then after that type:
fastboot boot recovery-RAv1.0H.img
you should get downloading..Okay
blah blah blah.. Okay
then the Last Step
after that you apply sdcard:update.zip" from the menu

flapz said:
Now I understood you. MANY MANY thanks
I think my mobile is running now
Click to expand...
Click to collapse
lol. i posted an even easier to follow steps just now.. haha. but glad to know you got it working....
And no problem! Im here to help..

[Q] How is CM5.0.8 on HTC Magic?

Hi guys,
I'm getting ready to root my HTC Magic 32A from Rogers and I was wondering what type of experience people had switching from stock ROM with Android 1.5, rooting and running CM5.0.8.
Is the the phone going to be any slower or faster?
Battery life is going to be affected or not?
The whole phone is stable or will crash from time to time...
Thanks,
Alex

Felt slightly faster on my mt3g... Though cyano6 rc2 or 3 will give you 2.2 and jit... Food for thought
Sent from my SAMSUNG-SGH-I897 using XDA App

thanks for your comment, I decided to start conservative and try CM5.0.8 because everybody says it's stable
don't know about CM6 RC3...
but I care about how snappy the phone is, battery life and application support

I found 5.0.8 to be very stable on my Rogers Magic. Never a lock or a crash. Very snappy performance.
After reading about the performance boost with 2.2 and JIT I loaded Froyo Redux 1.7 (CM6RC3).
So far I am very happy with what I've seen. Not enough time on this ROM yet to judge battery performance but so far it appears very good.

I like to hear that because the stock ROM is ancient
Just wanted to make sure battery life is at least on par and menu & apps are reasonable performance
Where can I get Froyo Redux 1.7 from officially?
...also I keep having this thought, is is possible to backup my current phone state (with the stock Rogers ROM) before I start rooting and switching to custom ROMs?

alex_canada said:
I like to hear that because the stock ROM is ancient
Just wanted to make sure battery life is at least on par and menu & apps are reasonable performance
Where can I get Froyo Redux 1.7 from officially?
...also I keep having this thought, is is possible to backup my current phone state (with the stock Rogers ROM) before I start rooting and switching to custom ROMs?
Click to expand...
Click to collapse
AMON_RA's recovery ROM has a backup option.
here is the Redux 1.7 thread over in the dev forum.
http://forum.xda-developers.com/showthread.php?t=723520

Thanks for the Redux 1.7 thread link...looks very interesting!
I think I understand your comment about AMON_RA's recovery ROM, but I wanted to backup also my stock ROM which at that time will be already overwritten I think...
Is there a way I can root my phone, install a good backup application that can backup the current state of my phone before I start installing AMON_RA and Redux 1.7?
Sorry if my questions don't make sense...beginner with these things.

I think the backup has to be done from Recovery. There is a very nice app called Titanium Backup but that doesn't do the "image" backup you're talking about.
The first thing to do is power off your phone (remove battery?) then power it on while holding the VOLUME DOWN button.
The Radio, HBOOT, SPL version numbers that show up in the first 4 lines are important and will dictate what steps you must take to root etc.
post that data here.

This is all the data I get in that screen:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.76.0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58

This link heleped me out it is well explained how you should do your rooting.
it is on wiki.cyanogen do the googleing

Thanks for the cyanogen wiki...I check it out and they have some good information there.
Well I have the links to a few 1-button scripts that take my phone from the Rogers stock ROM to CM5.0.8 taking care of all the quirks introduced by the nice provider I am with...but I wanted to know if there's a way back if I want to

THere is always way back just make nandroid backup with Amon ra recovery because it is like changin OS on you computer and there is also somewhere thread with original roms i saw it just search it enjoy your new CM android

alex_canada said:
This is all the data I get in that screen:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.76.0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
Click to expand...
Click to collapse
you have what is known as the perfected SPL (HBOOT-1.76.0010) which requires a gold card to replace.
You also have the "newer" radio so you should take note when flashing recoverys.
Until you replace the SPL via a gold card none of that matters as your current version will not allow you to flash anything.

Hey Freyder,
I used the guide that I posted below and worked like a charm with my phone
no gold card needed
MANUAL PROCEDURE FOR ROGERS MAGIC
Status of script will be written at bottom of file
.
You must have ADB working to connect to your magic before this procedure will work.
On XP machines, you can install HTC sync on your PC, put the phone into USB-debugging
and connect it to the PC. The correct drivers should install automaticly, if not, Google will
be your friend.
.
1. Make sure that the listed files are present in the folder with the Rootme.bat file
.
a) update-cm-5.0.8-DS-signed.zip
b) bc-5.0.8-ebi1-signed.zip
c) gapps-ds-ERE36B-signed.zip
d) exploid
e) Radio_HTC_PVT_32A_3.22.26.17.img
f) hboot-1.33.2010.img
g) recovery-RA-sapphire-v1.7.0H.img
h) update-hboot-1.76.2007-signed.zip
i) recovery-RA-hero-v1.6.2.img
.
2. Connect your magic to your PC and enable USB debugging on your phone.
.
3. Open up a command window and navigate to the directory containg the data
files that need to be sent to your phone.
.
4. Using the syntax "ADB PUSH {file name} {location}" push the following files to
phone. Pay attention to the "/" and make sure you don't miss or add any
a) update-cm-5.0.8-DS-signed.zip to folder /sdcard/
b) bc-5.0.8-ebi1-signed.zip to folder /sdcard/
c) gapps-ds-ERE36B-signed.zip to folder /sdcard/
d) exploid to folder /sqlite_stmt_journals
e) recovery-RA-hero-v1.6.2.img to folder /data/local
f) update-hboot-1.76.2007-signed.zip to folder /sdcard/
.
Eg: adb push update-cm-5.0.8-DS-signed.zip /sdcard/
.
5. Run the following commands in the command window
a) adb shell chmod 777 /sqlite_stmt_journals/exploid
b) adb shell /sqlite_stmt_journals/exploid
.
6. Turn bluetooth on and then off on your magic
.
7. Unplug and then replug the usb cable from your magic
.
8. Enter the following commands into the command window
a)adb shell (you will get a $ prompt)
b)rootshell (you will be prompted for a password)
c)secretlol (you will get a # prompt)
d)chmod 666 /dev/mtd/mtd1
e)exit (you will be back to $ prompt)
f)flash_image recovery /data/local/recovery-RA-hero-v1.6.2.img
g)exit
.
9. Turn off your phone.
.
10. Boot into recovery by holding the Home + Power keys.
.
11. Using the trackball, select "Flash ZIP from SD Card"
.
12. Select update-hboot-1.76.2007-signed.zip
.
13. Press the HOME key to confirm selection.
14. Reboot phone as requested. It will boot back into recovery.
14. Enter the fillowing into the command windown
a)adb shell reboot bootlaoder
.
15A. When phone has booted into fastboot enter the following into the command window.
a)fastboot flash radio Radio_HTC_PVT_32A_3.22.26.17.img
b)fastboot flash hboot hboot-1.33.2010.img
c)fastboot flash recovery recovery-RA-sapphire-v1.7.0H.img
d)fastboot reboot-bootloader
.
16. When phone has booted into fastboot enter the following inot the command window.
a)fastboot erase system -w
b)fastboot erase boot
c)fastboot oem powerdown
.
17. After phone powers off, reboot into recovery by holding Home + Power keys.
.
18. Using the trackball, select "Flash ZIP from SD Card" and flash the following files.
Select the home key to confirm each file
a)update-cm-5.0.8-DS-signed.zip
b)bc-5.0.8-ebi1-signed.zip
c)gapps-ds-ERE36B-signed.zip
.
19. After the last file has finished flashing reboot the phone normally.
It can take anywhere from 5-15 min for the first boot.

[Q] is there a custom recovery that will work for me

My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem

there was one thread here .. try to search it i forget link it can explain you how to root official 2.1 otherwise run RUU & Do downgrade

according to all the programmes i run to check status of root (latest one is under the hood) it lists
Device: htc_hero hero
Root Status: Device routed
ro. build fingerprint: orange_uk/htc_hero/hero/hero:2.1-update1/ERE27/196735:user/release-keys
every programme that requires root access works for me tho i do have to grant it every time for programmes , the clockwork recovery has to be reflashed if phone has been restarted to enable me to access the recovery, and when i do this su pops up telling me it has been granted.

1 method i tried but never got past step backup recovery was this but i get message backup failed could not run command
"HTC Hero Custom Recovery
Step 1:
It's advisable to format the SD Card before do this process. You're going to lose all the information in the SD Card, do a manual backup to your computer of whatever you want, to do it:
Settings -> SD Card & phone storage -> Unmount SD card -> Format SD card
Step 2:
Download the flashrec from http://code.google.com/p/flashrec/
Download the recovery image provided by Paul from http://www.romraid.com/paul/hero/1.2-hero-recovery.zip
Extract the 1.2-hero-recovery.zip to your PC.
Step 3:
Now copy flashrec and recovery-RA-hero-v1.5.2.img (wich is inside the .zip file) directly to your SD card
Step 4:
Use an app installer from Google Market to install flashrec, i used ASTRO, but can be any other.
Step 5:
Once installed, open the program, click the button "Backup Recovery Image" and wait to finish, shouldn't take much time, this will do a backup of your actual recovery and put it in your SDCard with the name recovery-backup.img.

brisuth said:
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
Click to expand...
Click to collapse
You're absolutely right, the 2.1 update for the Hero installs a recovery rom reset, so whenever you boot up your phone normally, it reflashes it (or possibly checks that it's not the original and then flashes).
I don't quite remember where this was done anymore, it might have been a script in /system/bin that gets called from init(rc), called something like flash_recovery.sh. Perhaps someone who isn't running a custom rom could help out and pinpoint it for future reference (I am so not going back from cyanogen 6.0
Edit: I grabbed unyaffs and checked out my old nandroids, it's /system/etc/install-recovery.sh, comment out the line in it (add a # at the beginning of the line) and it will not clobber your custom recovery

i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.

brisuth said:
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
Click to expand...
Click to collapse
It might need to be a text editor that knows not to break unix line endings, but you can copy the file (cat file > /path/to/destination/file) to your sdcard or use adb to pull the file... fairly straightforward I thought.

A big thankyou to duck0 for identifying the problem and botoo for getting me to a happy conclusion with the correct commands
SOLUTION IS HERE USING Console mode from windows using ADB USB DEBUGGING HAS TO BE ENABLED WITH HERO CONNECTED TO PC THEN TYPE THE FOLLOWING
THEN ENTER AFTER EACH COMMAND
anyone needing help setting up adb see this link http://forum.xda-developers.com/showthread.php?t=757233
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Thats it all done next step
INSTALL ROM MANAGER FROM MARKET IT IS FREE
open it and sellect flash alternate recovery image from the bottom, you can use the clockwork recovery but it is not compattable with all roms.
once done turn phone off, boot into recovery home + power choose to exit recovery with reboot shut down once again and if you can enter recovery then everything is sweet.

root 2.3.4,downgrade,and s-off

ATTENTION! this thread is OUTDATED
unrevoked has always been a finicky program,3.22 working fine for some,not so much for others.recent updates seemd to have made it even worse, i see alot of issue and fustration with it lately. as such, i do not recomend this method any longer.
IMO,at this time htcdev is the best way to root,downgrade,and achieve s-off. while it technically does void your warranty,and wipe your data,it has thus far at least proven to be reliable. i doubt may original droid incredibles have factory warranty left anyway it does not use unrevoked,or any otehr root tools or programs,just htcs own unlock(you can giggle loudly,or silently,as you use their unlock to achieve s-off
the original home of the hctdev method is here, on android forums.
it is also here: http://forum.xda-developers.com/showthread.php?t=1600904 but not as well supported since im not here as much.
_______________________________________________________________________________________________________________________
*outdated guide:
i wasnt sure if this should be here,or in development,so feel free to move it if you feel its in the weong spot. i cant take credit for any of this,i just took it all from different places and put it all here. unfortunately,i cant gaurantee that this will work for everyone. but several have succesfully downgraded and regained s-off.
its intended for someone who has no adb experinece,and is overwhelmed at the thot of downloading and installing the SDK. if your proficient at adb,your welcome to pull flash_image and mtd0 out,and place them in tools,platform tools,or wherever you usually push files from,rather than changing to the mini-adb_inc directory.
thots and feed back are welcome. ive had this guide up here on AF for a few days. ill try and provide support here as well,but please underdstand computer time is limited these days and i dont make it here as often. in otherwords,please help each other out
_______________________________________________________________________________________
PLEASE NOTE: this thread is for the original droid incredible. NOT the incredible 2(vivow) or incredible S(vivo)
for info on downgrading the inc 2 to .97 hboot so you can root with revolutionary,see this thread here in the inc 2 all things root subforum
if you DO have an original droid incredible,aka Inc 1,then procede
_________________________________________________________________
**********************************************************
_________________________________________________________________
READ THIS: i dont mean to sound like i dont want to be bothered with questions. however,folks are having basically the same issues thru-out the 600+ posts,so i can almost gauarntee if you have a prollem,it has been covered. please try and search for some answers before jumping to the end and posting. answering the same things over and over is just making the thread even longer and harder to search.
if you do have trouble and need to post questions about ADB commands,please provide a copy of your entire session in the command window along with the question. its usually pretty easy to see what went wrong when we can see the whole thing.
copy everything in the command window,and paste it into a code box by:
-right click in the command window,click mark.
-highlight everything in white. hit enter.
-then,in your "reply to thread" box here,click the "#" up top
-right click and "paste" everything between the
Code:
tags.
_________________________________________________________________
i cant take credit for any of this,i just took it all from different places and put it all here. unfortunately,i cant gaurantee that this will work for everyone. but several now have rooted 2.3.4,and 1 has succesfully downgraded and gained s-off.
its intended for someone who has no adb experinece,and is overwhelmed at the thot of downloading and installing the SDK. if your proficient at adb,your welcome to pull flash_image and mtd0 out,and place them in tools,platform tools,or wherever you usually push files from,rather than changing to the mini-adb_inc directory.
thots and feed back are welcome. there will prolly be several edits of this as i try to clarify it,and make it a lil better. but for now im tired and 5am comes early ;)
[B]first and foremost,giving proper credit to all that deserve it:[/B]
*alpharev and unrevoked for all they for the root community :cool:
-efizzle for getting the ball rolling in [URL="http://forum.xda-developers.com/showthread.php?t=1286223"]this thread[/URL] on xda by figuring out that an older version of unrevoked would get superuser access on 2.3.4
-iowabowtech for point me in the direction of [URL="http://forum.xda-developers.com/showthread.php?t=768295&highlight=ota"]this thread[/URL] that i collected the misc image,and parts of the guide. also for his support answering questions.
-sele and the crew in the "rescue squad" on [URL="http://api.viglink.com/api/click?format=go&drKey=1153&loc=http%3A%2F%2Fandroidforums.com%2Fthunderbolt-all-things-root%2F418539-thunderbolt-root-unroot-thread.html&v=1&libid=1318297929451&out=http%3A%2F%2Fwww.thunderboltforums.com%2F&ref=http%3A%2F%2Fandroidforums.com%2Fthunderbolt-all-things-root%2F&title=Thunderbolt%20Root%2FUnroot%20Thread%20-%20Android%20Forums&txt=HTC%20Thunderbolt%20Forum&jsonp=vglnk_jsonp_13182980284911"]the thunderbolt forum[/URL] for what i like to call the "mini-adb" concept.
-rooter28 for testing and keeping me updated as he made progress. hopefully he will stop in and help answer questions :)
-mkreiger for fearlessly jumping in to be the second official tester
-lovejess for finding a mac download for unrevoked 3.22
-gkinsella2 for contributing the mac specific instructions
-whomever origianlly came up with the images and guide linked above. if i can figure out who this was,ill add you in later.
*special thanks to sdrawcab for his invaluable support in helping answer questions and prollems
-prolly more,im sure there will be several edits of this.
1)[B][I]download these files[/I][/B],and save them somewhere you can easily find them:
[U]unrevoked 3.22[/U] [url=http://www.multiupload.com/WMGYYGL97Z]unrevoked 3.22[/url]
[U]mirror:[/U] [URL="https://www.box.net/shared/8e3nb5l5lnjjuh6vbqt7"]unrevoked 3.22 mirror[/URL]
md5: [COLOR="red"]5760fbe8ed6d44752e78433252f2d5b2[/COLOR]
[U]unrevokeds modified usb drivers[/U] [url=http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install]public:windows_hboot_driver_install [RootWiki][/url]
[U]mini-adb_inc[/U](contains misc image,flash image,and some basic adb tools)[url=http://www.multiupload.com/0G635MCZS2]Multiupload.com - upload your files to multiple file hosting sites![/url]
md5: [COLOR="red"]a793cc0142e1cd18f60849894bbc47cd[/COLOR]
[U]mirror:[/U][url]http://www.mediafire.com/?o6c4kq4wyccuom5[/url]
mirror md5: [COLOR="Red"]7c5211686a20b558ccd660c782f82e2b[/COLOR]
[I]*clockwork and zergrush included in mirror[/I]
[U]PB31IMG for 2.2[/U] (2.2 downgrade) [url=http://www.mediafire.com/?uvha2u2pv3xp8d5]PB31IMG.zip[/url]
[U]mirror:[/U] [url]http://pvillecomp.com/?page_id=22[/url]
md5: [COLOR="red"]31bb1611a0fa8197d447c0438426717e[/COLOR]
[U]clockwork 5.0.2.0[/U] [url=http://www.multiupload.com/FGEU9VPGKF]Multiupload.com - upload your files to multiple file hosting sites![/url]
[U]mirror:[/U][url]http://pvillecomp.com/?page_id=28[/url]
md5: [COLOR="Red"]e8ac35ddc1c37000bb0852d1f380b5bb[/COLOR]
**make sure to check the md5 sums match those listed!**
if you dont have an md5 sum verifier on your PC,there are many out there for free. heres an example: [url=http://www.md5summer.org/]Home of the MD5summer[/url]
2)[B][I]root with unrevoked 3.22[/I][/B]
-go to settings/applications and [U]uncheck[/U] "fastboot". having this checked will prevent you from getting to hboot via power/vol down.
-open the recovery-clockwork-5.0.2.0-inc_PB31IMG download. extract it first if you need to. inside there is an image called "recovery-clockwork-5.0.2.0-inc". right click on this image,then click "copy". navigate to a directory you can easily find it,then right click in that directory,then "paste". alternatively,you can drag it from the extracted folder to a convienient spot(i personally like to drag files around,but its fine either way).
-use your md5 summer to verify the md5 of just the image,not the whole .zip. it should be: [COLOR="Red"]ea382ca5809cb872d0582aa22741d592[/COLOR]
-install the drivers as described on unrevokeds page above.
-unplug your phone.
-extract the contents of the unrevoked 3.22 .zip. open the folder, right click on "reflash" and run as administrator if possible.
-click on "file" in the corner of the relfash window
-click custom recovery
-navigate to,and select your "recovery-clockwork-5.0.2.0-inc" image and select it. at the bottom of your reflash app window, it should now say "recovery:custom" and "waiting for device"
-make sure usb debugging is checked ON in settings/applications/development.
-plug in your phone and place it in charge only mode. assuming you installed the drivers correctly,unrevoked 3.22 will start. let it do its thing. it will reboot a couple of times. when its finished,it may leave you on a blank screen. if this is the case,pull the battery and reboot.
-you [I]should[/I] now have the superuser app in your app drawer. if so,go to settings/applications/manage apps/superuser and clear data. test that superuser is working and granting permissions by downloading rom manager,and using it to flash the newest clockwork recovery. alternatively,download and run a "root checker" or any of your favorite "root only" apps and make sure they work.
-once you get "successfully flashed clockwork recovery" boot to it and make a backup,since downgrading to get s-off [U]WILL[/U] wipe all your data. boot back into the operating system.
*[I]special note to slcd users[/I]: this version of unrevoked is installig an old, non-compatible version of clockwork,so you will just see a black screen if you do not install newer clockwork as described above.
-if you plan to install a custom rom after downgrading,now is a good time to download titaium backup,and its pro key(WELL worth the $$) and do a batch backup of all your user apps and app data(no system data)
*at this point,you could just enjoy root access without doing anything else. if all you care about is using a couple of root only apps,and deleting some bloatware,you can remain rooted and s-on if youd like. id personally reccomend to downgrade and become s-off in case future OTAs knock out your root access.
3)[B][I]prepare to downgrad[/I]e[/B]
-extract the mini-adb_inc .zip. place the extracted folder on the root of your c drive. it comtains mtd0,flash_image,and some adb tools.
-place the 2.2 downgrade on the root of your sd card,and verify it is named "PB31IMG". now is a good time to verify that your SD card is formatted "FAT32" by right clicking on the drive that is your phones sd card,then click "properties". if you find your card is formated anything else,youll have to re-format it. start by backing up all files to your PC as reformatting [U]WILL[/U] wipe it clean. using your PC,do a full format to FAT32. you can then transfer the files back. *this is important-as your phone will not find the downgrade PB31IMG unless your card is formatted to FAT 32,and the file is correctly named.
[U]special notes on hboot flashing PB31IMG files[/U] a common issue folks are having is the PB31IMG is not being found by hboot.
*there are only 2 reasons a PB31IMG is not found on the root of the sd card:
a)not named correctly. the phone muse see exactly "PB31IMG.zip". due to the way windows automatically adds and hides file extensions,it is usually correct to name the file "PB31IMG" with windows. common errors are for the file to be named "PB31IMG.zip.zip" after manually tying in the ".zip". on rarer occasions,it may not be adding/hiding the file extension,resulting in the file actually beening seen by the phone as "PB31IMG" :eek: [I]check your file with a file manager on your phone[/I] and see how its seeing it.
b)sd card not formatted FAT32. if it is plain FAT or anything else,PB31IMG is invisible. on rare occasion,i have seen claims that a bad sd card,or card that needs reformatted(even tho it may be FAT32) will have the same affect.
*this has been addressed [U]several[/U] times in the thread,skim thru it for more information.
4)[B][I]downgrade with adb[/I][/B]. make sure your phone is charged to 100% before starting.
-on windows 7,click the start bubble and type "command" in the search box. this should open a small black command window. from this point forward,all code will be in [B]bold[/B] so you know what lines to copy and paste(or type,if you really want to type them all in). additional comments will be blue,and should not be copy/pasted. please note that each line is one command. copy/paste it into the prompt in your command window,and push enter. one line at a time.
at the end of the post,is a copy of my session,to show what the outputs of the entered lines should look like. hopefully,its a little less scary when you know that youre getting the right responses to the things you enter.
-make sure phone is plugged in and usb debugging checked on,in charge only mode
-at the promt in your command window:
[B]cd c:mini-adb_inc [/B] [COLOR="Blue"]this should change your command promt to "mini-adb_inc",indicating youre using that directory.[/COLOR]
[B]adb devices[/B] [COLOR="blue"]this should output your phones serial number,indicating its recognized[/COLOR]
[B]md5sums mtd0.img [/B] [COLOR="blue"]it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839
[/COLOR]
[B]md5sums flash_image[/B] [COLOR="blue"]again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a[/COLOR]
[COLOR="Red"]*both those numbers must match exactly. if they do then you can procede.
[/COLOR]
[B]adb push flash_image /data/local/[/B]
[B]adb push mtd0.img /sdcard/[/B]
[B]adb shell[/B] [COLOR="Blue"]your prompt should change to a #. if it changes to a $,then type[/COLOR] [B]su[/B] [COLOR="blue"]note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.[/COLOR]
[B]cd /data/local[/B]
[B]chmod 0755 /data/local/flash_image[/B]
[B]cd /data/local[/B]
[B]./flash_image misc /sdcard/mtd0.img[/B]
[COLOR="blue"]you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off[/COLOR]
[B]exit[/B] [COLOR="Blue"]to get out of your adb shell,and back to the "mini-adb_inc" prompt[/COLOR]
[B]adb reboot bootloader[/B] [COLOR="blue"]this will boot your phone to "fastboot" select "bootloader" with the power button.[/COLOR]
hopefully what you will see now,is a blue status bar as your phone finds the PB31IMG,unpacks it,checks it,then asks if youd like to update. select yes to update with the volume up rocker. if youve never installed a full ruu in hboot,it will take a few minutes,so dont panic. place the phone gently down somewhere where it wont fall and spit out the battery. let it do its thing. push power to reboot when prompted.
let the phone fully boot,then place in disk drive mode and immediately delete PB31IMG from your sd card,as it will interefere with running unrevoked forever.
*[I][U]special note:[/U][/I] if your phone does not fully boot after running PB31IMG,dont panic. its happened to quite a few users,for some reason. simply pull your battery,boot to hboot via power/volume down and run PB31IMG again.
download unrevoked forever from here: [url=http://www.unrevoked.com/recovery/]unrevoked3 recovery reflash tool, v3.32[/url]
run it as you did the previous version. before plugging in your phone,make sure "disable phone security is checked" in the file menu. this time,it will root you,and turn the secure flag off on your radio. this is good,as it will allow you to always flash things that werent signed and approved by htc. you can flash new radios and recoveries,and flash any ruu you wish. the secure flag is in the radio,so running ruus or even accepting OTAs will not over-ride it. you will always stay s-off.
[I][U]*unrevoked 3.32 note:[/U][/I] if you check the "disable phone security" box as described above,and unrevoked still fails to turn s-off,you are not lost.[U]simply flash the s-off tool in recovery[/U]. you can find it here: [url=http://unrevoked.com/rootwiki/doku.php/public/forever]public:forever [RootWiki][/url]
if you wish to return to where you were,sign into google,download rom manger,flash the latest clockwork recovery. boot to recovery,then restore the back you made before we started.
optionally,you can now install the custom rom of your choice,along with a new recovery and radio if you desire. :)
and heres what you will see when entering the commands(the red are my copy/paste's):
[CODE]Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:mini-adb_inc[/COLOR]
c:mini-adb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT07DHJ02777 device
c:mini-adb_inc>[COLOR="red"]md5sums mtd0.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_inc]
mtd0.img 34307be744275f1db1dd16af04c37839
c:mini-adb_inc>[COLOR="red"]md5sums flash_image[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_inc]
flash_image 0098a7dd6600b55fac34fc6645be5d7a
c:mini-adb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1547 KB/s (76044 bytes in 0.048s)
c:mini-adb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1662 KB/s (655360 bytes in 0.385s)
c:mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
# [COLOR="red"]exit[/COLOR]
exit
$ [COLOR="red"]exit[/COLOR]
exit
c:mini-adb_inc>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_inc>
other info:
-unrevoked 3.22 for mac can be found here: http://downloads.unrevoked.com/recovery/3.22/Reflash.dmg at this point youre on your own converting the adb commands. if someone wants to translate,or make a mac adb guide,ill gladly add it in
-until we put together a mac specific guide,directions for modifying the rest of it to work on a mac are found in post #629,here: http://androidforums.com/incredible...-3-4-root-downgrade-s-off-13.html#post3623666 courtesy of gkinsella2. mac users(and everyone else ) make sure to click the thanks button on his post!
______________________________________________________________________________________
*last and not least,this is a direct copy/paste of the AF thread,so any references to pages numbers are references to THAT thread on AF

the zergRoot method
this is for folks who for whatever reason,unrevoked 3.22 does not work to get them root access.
this could also be used if youve got a replacement device thats not setup,and you could care less about installing a recovery. this still requires unrevokeds drivers to be set up,so you can root with unrevoked 3.32 after downgrading,but otherwise,it prolly is a lil quicker since you dont need to download and run unrevoked 3.22.
alternately,use this if you just like ADB if your proficient in adb,feel free to remove the images from mini-adb_inc,and place them and the zergRush tool into whatever folder you typically push files from.
like above,this is intended for someone whose never installed ADB or entered command lines before.
1)download these files,and save them somewhere you can easily find them:
unrevokeds modified usb drivers public:windows_hboot_driver_install [RootWiki]
mini-adb_inc(contains misc image,flash image,and some basic adb tools)Multiupload.com - upload your files to multiple file hosting sites!
md5: a793cc0142e1cd18f60849894bbc47cd
PB31IMG for 2.2 PB31IMG.zip
md5: 31bb1611a0fa8197d447c0438426717e
zergRush tool from xda: Revolutionary - zergRush local root 2.2/2.3 - xda-developers
md5: 12c52b97e75e73595b325c03610b3380
**make sure to check the md5 sums match those listed!**
if you dont have an md5 sum verifier on your PC,there are many out there for free. heres an example: Home of the MD5summer
3)prepare to downgrade
-extract the mini-adb_inc .zip. place the extracted folder on the root of your c\ drive. it comtains mtd0,flash_image,and some adb tools.
-extract zergRush.zip. take the image inside,and either copy/paste or drag it into your mini-adb_inc folder
-place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG. now is a good time to verify that your SD card is formatted "FAT32" by right clicking on the drive that is your phones sd card,then click "properties". if you find your card is formated anything else,youll have to re-format it. start by backing up all files to your PC as reformatting WILL wipe it clean. using your PC,do a full format to FAT32. you can then transfer the files back. *this is important-as your phone will not find the downgrade PB31IMG unless your card is formatted to FAT 32,and the file is correctly named.
4)downgrade with adb. make sure your phone is charged to 100% before starting.
-on windows 7,click the start bubble and type "command" in the search box. this should open a small black command window. from this point forward,all code will be in bold so you know what lines to copy and paste(or type,if you really want to type them all in). additional comments will be blue,and should not be copy/pasted. please note that each line is one command. copy/paste it into the prompt in your command window,and push enter. one line at a time.
at the end of the post,is a copy of my session,to show what the outputs of the entered lines should look like. hopefully,its a little less scary when you know that youre getting the right responses to the things you enter.
-make sure phone is plugged in and usb debugging checked on in charge only mode
-at the promt in your command window:
cd c:\mini-adb_inc this should change your command promt to "mini-adb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized
md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839
md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a
md5sums zergRush again,output stuff, then this number: 3cf8a3fbceb667121d91f4ef1a66684c
*all those numbers must match exactly. if they do then you can procede.
adb push zergRush /data/local/
adb shell this will change your promt to a $
chmod 755 /data/local/zergRush
/data/local/zergRush
this will cause zergRush to start,and it shoudl say "found a gingerbread!" followed by a bunch of other funny stuff.
last thing it says will be: Killing ADB and restarting as root... enjoy!
you should then be returned to your "mini-adb_inc>" prompt
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
adb shell your prompt should change to a #
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local
./flash_image misc /sdcard/mtd0.img
you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off
exit to get out of your adb shell,and back to the "mini-adb_inc" prompt
adb reboot bootloader this will boot your phone to "fastboot" select "bootloader" with the power button.
hopefully what you will see now,is a blue status bar as your phone finds the PB31IMG,unpacks it,checks it,then asks if youd like to update. select yes to update with the volume up rocker. if youve never installed a full ruu in hboot,it will take a few minutes,so dont panic. place the phone gently down somewhere where it wont fall and spit out the battery. let it do its thing. push power to reboot when prompted.
let the phone fully boot,then place in disk drive mode and immediately delete PB31IMG from your sd card,as it will interefere with running unrevoked forever.
download unrevoked forever from here: unrevoked3 recovery reflash tool, v3.32
run unrevoked(extract the contents,right click on "reflash",run as adminstrator if possible). this time,it will root you,and turn the secure flag off on your radio. this is good,as it will allow you to always flash things that werent signed and approved by htc. you can flash new radios and recoveries,and flash any ruu you wish. the secure flag is in the radio,so running ruus or even accepting OTAs will not over-ride it. you will always stay s-off.
and heres what you should see when entering the commands(my copy/pastes are in red):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_inc[/COLOR]
c:\mini-adb_inc>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT117HJ00242 device
c:\mini-adb_inc>[COLOR="red"]md5sums mtd0.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
mtd0.img 34307be744275f1db1dd16af04c37839
c:\mini-adb_inc>[COLOR="red"]md5sums flash_image[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
flash_image 0098a7dd6600b55fac34fc6645be5d7a
c:\mini-adb_inc>[COLOR="red"]md5sums zergRush[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
zergRush 3cf8a3fbceb667121d91f4ef1a66684c
c:\mini-adb_inc>[COLOR="red"]adb push zergRush /data/local/[/COLOR]
1150 KB/s (21215 bytes in 0.018s)
c:\mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]chmod 755 /data/local/zergRush[/COLOR]
chmod 755 /data/local/zergRush
$ [COLOR="red"]/data/local/zergRush[/COLOR]
/data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015108
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219e4 0x006c
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd158bf 0xafd1ace3
[*] Sending 149 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
c:\mini-adb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1547 KB/s (76044 bytes in 0.048s)
c:\mini-adb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1017 KB/s (655360 bytes in 0.629s)
c:\mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
#[COLOR="red"] exit[/COLOR]
exit
c:\mini-adb_inc>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_inc>
edit:apparently the zergRush tool has changed. ive included the new md5s,so hopefully there wont be any more confusion like the old md5s caused earlier. be aware of this,however, in case they do change again. you are right to be cautious if it doesnt match,so ill do my best to keep up with it.

This does work, but god I wish it was all ADB it was all so easy before unrevoked it didn't work the first time it gave me SU and root but no s-off then unrevoked would not run again due to new firmware. I did full downgrade to 2.2 and followed all directions ADB is so simple but unrevoked took 2 hours of just missing around to get s-off which included flashing 2.2 in hboot again starting over, running what I could run again in ADB without the gingerbreak since I was now on froyo, it was mostly just repushing the files and binary. But after all that unrevoked ran and gained root and s-off. Worst root I have ever done but people its all about making smart decisions before you do it if you make a mistake and get stuck, get help or trouble shoot but use you head before you battery pull and make sure you read before you hit anything.
If I helped you in any way please use the thank you button

sorry you had such issue with unrevoked. usually thats the easy part most folks are confused by adb and running commnads and wish it was all automated!
just a couple things that may help folks in the future:
-if you dont want to fool with unrevoked 3.22 in 3.2.4 use the "zergRoot"method in post 2. its all adb up to the downgrade. once you get to this point,you could easily roll yourself all the way back to the shipping firmware(assuming amoled screen) if you wanted,and then use an adb method(if one exists,im not that flamiliar with the inc). you dont have to go back to 2.2. i just picked that cause most folks are familiar with it,and with using unrevoked 3.32 to root/s-off it
-there have been a few complaints of unrevoked not giving s-off on 2.2. before you start,make sure "disable phone security" is checked in the file menu. if s-off still fails,but gives you root and a recovery,its worked for everyone thus far to just run the "forever" .zip in recovery,no real need to reflash the 2.2 ruu and run unrevoked multiple times.
-last and not least unrevoked is not ever going to give s-off in the 2.3.4(unless they release a new version for 2.3.4),as is uses an unsupported baseband,thats why the 2.2 downgrade is needed. folks that have no intention of backing up or returning to 2.3.4 and are fairly savy like the poster above,id strongy encourage to just use directions in post 2,its a lil quicker to not have to mess with unrevoked 3.22. its mainly included for the folks that want to make a nandroid or run tibu prior to the downgrade(plus zergRoot hadnt come out yet,when i originally put this together )
once your back on 2.2 you could even just use z4root to get get root access,install rom manager and clockwork,then flash the forever patch. once you can downgrade,there are alot of ways to skin the cat

Worked after a few tries!
Thanks Scotty for this writeup. I thought for a minute that things wouldn't work, but a third try proved fruitful.
Here's a few tips that I can add to things.
Things failed for me at the restore 2.2 part - HBOOT would not recognize the zip file as correct.
I am on a Win XP machine... Format the sd card to fat 32 using something other than Windows - I used a little program called "fat32format.exe". Windows seems to have a problem formatting sd cards correctly, so that could have been it.
Once I made sure the sd card was formatted, I put the 2.2 zip (PB31IMG) back on the sd card and started over using the zergRush method.
If you have tried this before, you will have to remove two directories from the /data/local/tmp directory. These are sh and boomsh. Thanks to ieftm in this forum for this tidbit of info.
If your zergRush is giving you problems stating:
[-] Cannot copy boomsh.: Permission denied
Then use this method to fix as I stated in paragraph above: remove sh and boomsh
Once these directories were removed and the zergRush was completed, the downgrade commenced just as described.
Side note - Unrevoked 3.32 installed Unrevoked forever automatically onto my DInc, so there was no reason to do the additional forever installation. You may have the same results.
For anyone else that can't seem to get things working, the search is your friend. It took me a while of hacking away at things, but eventually they all turned up roses...
Good Luck!

problems install roms
I have a problen,I can't install a Rom error e: can't open/sdcard/primexl3d.zip, why?

saosinalm:
First off, that's the wrong name for the downgrade zip according to the instructions that scotty posted above. Make sure the file is titled correctly and follow his instructions from beginning to end. I believe when mine succeeded my file title was "PB31IMG.zip" but in his instructions he leaves off the ".zip" at the end.
If there is an error in the process, you will have to start over from about step 3. You can't just start back from where you left off if you reboot the phone. Make sure you check your MD5's once you download, then you won't have to go back over that step.
I found the zergRush method easier, but I am more comfortable with adb...
I would suggest re-reading the instructions and following closely - he walks you through things really well.

I have one question....
Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.
Am I wrong?

epescina:
That's really best answered differently depending on the type of person you are. If you like to play around and experiment with things or like learning how things work, maybe this works for you. Some people do it to get a custom look that no one else has, some do it to try and get better performance out of their phone that may have been bloated with apps out of the factory, and others are learning about developing apps and programming with it. Every person is different. Maybe it's just not for you, but others on this board can't live without it. To each his (her) own...

saosinalm said:
I have a problen,I can't install a Rom error e: can't open/sdcard/primexl3d.zip, why?
Click to expand...
Click to collapse
what are you trying to do exactly? no part of this guide requires you to flash a rom. so if youre tryingto root,be more specific what youre having trouble with, and if this is just a general question about flashing roms,you might do some research and/or post a new thread where more people will see it

epescina said:
I have one question....
Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.
Am I wrong?
Click to expand...
Click to collapse
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own

scotty1223 said:
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own
Click to expand...
Click to collapse
I too hate the HTC Sense and wish I could change the overall layout of my phone. When I did load a new ROM that changed the layout it always seemed to be screwed up for one reason or another.
For example the lastest rom (Cyanogen) I absolutely loved but it didn't have market and I never could find out how to load it!

scotty1223 said:
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own
Click to expand...
Click to collapse
Couple of quick questions (which might appear silly):
"place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG"
#1) What do we rename "PB31IMG.zip" to? The directions simply state to rename it.
#2) Move it to the root of the external sdcard or internal sdcard?
tia, and I hope these questions weren't too ridiculous.

kjy2010 said:
Couple of quick questions (which might appear silly):
"place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG"
#1) What do we rename "PB31IMG.zip" to? The directions simply state to rename it.
#2) Move it to the root of the external sdcard or internal sdcard?
tia, and I hope these questions weren't too ridiculous.
Click to expand...
Click to collapse
It should be named PB31IMG.zip
It all depends how you rename it, if you use your pc it may not show the.zip extension if you have "show extensions" turned off. So on your pc it may just say PB31IMG even though it is really a zip. Sometimes when extensions are off people end up naming it PB31IMG.zip.zip wich will not work. It is best to have your pc show extensions you can do that by going to controll pannel / folder options / view tab uncheck hide extensions for known file types.

cmlusco said:
It should be named PB31IMG.zip
It all depends how you rename it, if you use your pc it may not show the.zip extension if you have "show extensions" turned off. So on your pc it may just say PB31IMG even though it is really a zip. Sometimes when extensions are off people end up naming it PB31IMG.zip.zip wich will not work.
Click to expand...
Click to collapse
wow lol ok, that just seems common sense, but I guess you never know who your audience is
Which sdcard should the file be on?

kjy2010 said:
wow lol ok, that just seems common sense, but I guess you never know who your audience is
Which sdcard should the file be on?
Click to expand...
Click to collapse
It should be on the removable sd not the internal storage if thats what you were asking.

cmlusco said:
It should be on the removable sd not the internal storage if thats what you were asking.
Click to expand...
Click to collapse
thanks again, just making certain. going for my third try now!
---------- Post added at 01:20 PM ---------- Previous post was at 01:14 PM ----------
I'm getting an unmatched number on zergRush
"md5sums zergRush again,output stuff, then this number: 795275fb9c41ebd5b9fe7ab19108c52b"
I get "4bf71b766a9603fa7db98e71e3f3b470"
??
It states:
"*all those numbers must match exactly. if they do then you can procede."
What do you do if they don't match?
Sorry for the n00b questions, been dealing with nothing but HC since June.

I would try redownloading and then check it again. If its still wrong i would contact the op scotty and ask him, as he is the one who provided the original md5.

cmlusco said:
I would try redownloading and then check it again. If its still wrong i would contact the op scotty and ask him, as he is the one who provided the original md5.
Click to expand...
Click to collapse
thanks, d/l it three times already what a PITA

I get a md5 of
3cf8a3fbceb667121d91f4ef1a66684c
for the zergrush file in the zip and.
12c52b97e75e73595b325c03610b3380
for the zip it self, different than both of your guys.
Edit. I believe that the zergrush file has been updated since this post to include more phones so that is probably why the md5 is different.

[GUIDE] Rooting G1, ADB/Fastboot Setup, Partitioning, etc.

This guide is compiled of various guides and threads that I've read and I want
to sum it all up in one post so you can root your HTC Dream (G1)
*many if not all rooting guides are incomplete or missing download links – I will do my best to keep links
posted and alive!
!!READ AND FOLLOW DIRECTIONS!! DO AT OWN RISK. I AM NOT RESPONSIBLE
FOR BRICKING YOUR PHONE.
I've compiled all of the files necessary and uploaded them to my drop
box
INDEX:​
-|1|: Setting up adb and fastboot
-|2|: Rooting
-|3|: Changing hboot versions
-|4|: No recovery?
-|5|: Un-Root
*This guide assumes you are using Windows but Linux and iOS will be able to use most of it.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
First off thanks to Demkantor since he was my sensai in a way (wax on wax off style)
Then thanks to HTCDreamOn, EzTerry, Cyanogenmod and all the developers out there that make all of this possible!

This is the optional ADB and Driver setup. I recommend you follow it through as it would make things easier in the future. This is more a reference post.
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
1: ADB and Fastboot setup with HTC Drivers
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
In order to do certain things that pertain of flashing radios and hboots you are going to need ADB and
fastboot. This is also useful for The Google Bypass if you dont have data or an activated sim card.
Go ahead and download this zip
Extract the zip file straight to your local disk. (You should get something like this
afterwards "X:\Android" x being the letter of your local disk)
Now that you have that on your local disk. Go to X:\Android and install HTCDriver3.0.0.007.exe. (This
has most if not all HTC USB drivers)
Finally add a path in order to access ADB and Fastboot from cmd on the computer.
Click on the Start button and right click "My Computer" and choose
"Properties".
Now you should be in "System Properties" under the
"General" tab, go to the "Advanced" tab and click
"Environment Variables".
Now you'll be in "Environment Variables", Now under the
"System Variables" scroll down to "Path" and highlight
it by clicking on it and now click "edit".
IMPORTANT be sure to not delete ANY of the
variable values already in the "Variable Value" section. Now that that is
clear, go ahead and ADD this to the "Variable Value"
section: ";X:\Android" (Obviously replace X with your appropriate local disk letter and without
quotations)
You now have setup ADB and Fastboot.
But in order to use ADB and Fastboot you must go back to "Start" click or search
for run, type in cmd and you will now have command prompt open.
NOTE: I will not post what the command are since all you have to do is type in "adb" or "fastboot" in the command prompt and it will show you the sub
commands for each perspective command.

---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
2: Rooting
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
-----------------
Step 1
-----------------
Assuming you're not on stock Android 1.0 follow steps 1-6, if already on android 1.0 skip to step 7 (1 when item is hidden).
This link is for RC29 (US)
*Optional is the update.zip as it seems to not work for some other wise you can skip the update.zip flash*
But if you need RC7 (UK) then use this link
Now plug in your phone and go to USB-MS. Go ahead and right click your USB-MS drive that appears
on your computer and hit "Format..". Now under file system be sure to set it
as FAT32 then hit format. Depending on how much memory your SD card is will
effect how long it will take. Once it is done move the DREAIM.NBH and update.zip into the
root of the SD card.
*only do this step if you got the update.zip file otherwise skip this step* Now power down your phone and boot up into Recovery mode (Home+Power).
You'll see an exclamation point with a triangle if you booted correctly. At this point
press "ALT+L" then you want to wipe all data so press
"ALT+W" then press "ALT+S" to
apply the update from the SD card.
Power down your device and boot it back up into fastboot mode (Camera+Power). It'll prompt you
if you'd like to install update hit prompted button and wait, this may take a bit and it won't be done
untill it prompts you that it is done so do not worry if it seems like its taking long and DO
NOT battery pull while it is installing.
Power down and now boot normally. You now have android 1.0 stock.
Sign-in into google.
GOOGLE BYPASS METHOD : only necessary if you do not
have data or an activated sim card or no sim card at all. But Wifi is required.
("<enter>" is actually the actual enter button so when it says "<enter>" press the enter button AKA return button)
Power on your phone but do not press anything. Plug your phone in via USB.
Slide your keyboard up type this is: "<enter>setprop persist.service.adb.enable 1<enter>". (Since you are on 1.0 this actually a command to enable USB Debugging although
you can't see anything)
Your pc will detect another device and begin installing drivers. (This is what HTC drivers installer was
for so your device will be installed correctly)
Now open cmd via run on your computer. Type in "adb devices" and it should show your device.
Example :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>adb devices
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>
Click to expand...
Click to collapse
(You only see this: "adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *" when its the first adb command your run when you open cmd)
type: telnetd<enter>
now on the computer using the command prompt type: adb forward tcp:23 tcp:23
then press enter
type: telnet localhost
press enter and you should see a # as you should have a root shell (while in this shell in order to backspace you must press the "Delete" button on your keyboard as pressing backspace will not do anything)
type: setprop app.setupwizard.disable 1
press enter
type: ps
press enter, this will show all the running processes
on the right column look for "com.android.setupwizard" then once that is located follow that line on to the second column from the left, the number in that column is the PID
type: kill PID
replace PID with the number that you found from the second column
It should now be at the home screen, if not press the "Emergency Call" button and press back and then you should be able to unlock the phone with the "Menu" button.
Now you can go to the settings connect with wifi and then bring down the notification that says you need to set up your account to sign in with your google email
Go to the market and download "TelNet" app. Once you have
it installed, go to USB-MS and put this recovery image onto the root of your SD card. reboot your device but do not press
anything or unlock the screen.
Once booted up slide your keyboard up, will unlock the device, and press the enter button twice and
type this in "telnetd" then hit enter (It’ll be a contact search but it’s okay). Now
go open Telnet app, and hit connect. If you did the telnetd part correctly you
will be prompted with a #. Otherwise you'll get a connection failed message, if
so reboot device and attempt the telnetd command again.
Type these commands in on your phone:
Press enter after each line
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
You now successfully flashed Amon_RA_ Recovery. :good:
You may reboot into your new recovery (power on holding home button) and flash a custom ROM. But
I do suggest upgrading your bootloader and radio first as the amount of ROMs available to you will be
much greater!
-----------------
Step 2
-----------------
Okay so now we will be updating to radio2.22.23.02 and DangerSPL.
Reboot into recovery mode (POWER+HOME), plug your phone in via USB and toggle USB-ms and delete everything off your SD card and placethese files onto the root of your SD card. Exit USB toggle.
Scroll down to wipe data and do so.. than go to "flash .zip file" now the first file you want to flash is the radio2.22.23.02 let finish then press home+back to apply update, it should reboot back to recovery after this.
Now go to wipe again and do so.. the next file you want to flash is the G1 Spl (Hard SPL) so flash the .zip file and let finish than press home+back to apply update.
Go to wipe data 1 more time. now go to flash zip and select the "Danger SPL.zip" let finish and press home+back to apply update.
Power back on into bootloader (camera+power) and check if device says.
Dream PVT 32b ENG S-off
HBOOT 1.33.2005 (drea10000)
CPLD-4
RADIO 2.22.23.02
APR 20, 2009, 15:30:43
Click to expand...
Click to collapse
If so you can move on to the next part!
-----------------------------------------*
Step 3
-----------------------------------------
Again delete the old files off your sd card and place these files on it!!
Quick note this is the last radio update for this section, radio2.22.27.08, now if you want radio update 2.22.28.25 refer to the changing hboot section and it will have the steps to do so.
Radio 2.22.28.25 may have better reception in your area but will drain your battery quicker.
Boot up into recovery mode, go to flash zip from sd and select Ohsaka superwipe. wait till finish then go to power down!! now boot back up into recovery again.
Now do a manual wipe of data and cache.
Now flash the radio2.22.27.08 file.. let finish than flash the hboot1.33.0013d file and let it finish! then reboot the device for update to apply.
Power off the device, then reboot into bootloader (camera+power) and check if device says.
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.27.08
OCT 21,2009,22:33:27
Click to expand...
Click to collapse
*If so you now have updated both your radio and SPL and you can now flash any ROM you'd like.
But if you'd like you can follow the next step and install a custom ROM and I will show you how to partition your SD card as well.
-----------------------------------------*
Step 4
-----------------------------------------
Okay so now that you have completed step 3 you can flash a custom rom but now we must partition the SDcard.
Reboot into recovery mode and go to Partition SDcard
Partition SD. Press home.
Now I have 4GB micro SD hc. My partition settings are*
Swap: 128mb (swap is not needed and is purely optional)
Ext: 576mb ( or whichever option is closest to that I can't remember, this is for apps2ext so you can save your apps to your sd card)
Rest: FAT32 (this will once again delete everything but you should have all your backed up data on your pc)
This is what I have for my partitionings and it's works fine for me and it should for you too!
Once that is done go to SD:ext2 to ext3 and once that is done upgrade the ext3 to ext4. You now have a partitioned SD card with EXT4!!
Now all that is needed is to flash the custom ROM. I am currently running this ROM.
Now return to toggle USB-ms and place the ROM zip file from the link above as well with Ohsaka superwipe from the previous step (download it once again)
Go to flash zip file and flash Ohsaka superwipe.
Power down. Reboot into recovery.
Now return to flash zip file and flash the ROM which should be named FroyoCreamSandwhich. Once it is done it will prompt you to press HOME+BACK do so.
Now reboot your phone normally and allow it to boot up (it may take a bit the first time but this is normal when you flash a new ROM). You will now be given the option to sign in create an new account or skip (although I believe it has the option to connect to wifi built in). You now have flashed your New ROM!!!!

---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
3: Changing HBOOT version
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
This option is for which ever reason you need the flash recovery/radio/etc you need the Engineer SPL. which is the SPL from step 2 in rooting. although since if you are already rooted and have the latest HBOOT then that route is not the way to go.
So in order to go back to that engineer SPL all you need to do is flash Engineering SPL zip in recovery.
Then you can proceed to update radio/ recovery etc and then flash back to the latest HBOOT which is 0013d so just download
Hboot0013dand flash it through fastboot with this command: fastboot flash hboot hboot.img

--------------------------------
No Recovery?
--------------------------------
Download: http://d-h.st/v9b2erpqfyd7/orange-1.58.73.2.nbh
Like always place the file in the same folder as the fast boot directory.
Enter fastboot and run "fastboot flash nbh orange-1.58.73.2.nbh"
Wait for it complete the flash
Boot into boot loader again and you will have an engineer SPL 1.42.2000
Now you can flash any hboot/recovery/radio via fastboot.

--------------------------------
Unroot
--------------------------------
ldrifta said:
---------------------------------------------------------------------------------------------------------------------------------------------
5~Un-Rooting
---------------------------------------------------------------------------------------------------------------------------------------------
Download these files...
DREAIMG.nbh
update.zip
Now would be a good time to un partition your sd card since there will no longer be a custom recovery..
1. first you take the "DREAIMG.nbh" file and the first "update.zip" file and place on root of sdcard!
2. start phone in recovery mode (home+power) do a quick wipe of everything! than flash the update.zip file.. wait for finish than reboot or power off.. whatever prompts tell you. than make sure device is powered off after finished installing!
3. power on via fastboot (camera+power) and wait for selection to pop up asking to install the update! press confirmation button to apply and let it work its magic!!
Now your phone will be on stock android 1.0 firmware! you have 2 options..
a. wait for automated updates.. could take up to 48 hrs..
b. flash updates to 1.5 and or 1.6 via stock recovery!
if you chose option b than you are smart! lol who wants to wait for updates for a G1 nowadays? lol
ok so now to apply updates via stock recovery you do what you would normally do.
Download these files...
Stock 1.5 (OTA)
Stock 1.6 (OTA)
(the stock 1.5 and 1.6 files are also "update.zip" so be sure not to mix them up and confuse the proccess!!)
1. Place files on root of sd.. DO NOT RENAME FILES, the stock recovery will only flash an "update.zip" so please dont make any changes to file.names...
2. boot into recovery mode (home+power) and wait for screen with yellow triangle and this thing ! now press alt+L together untill you see more words pop up on screen..
3. Now press alt+w to wipe the data on phone... (just do it dont ask why) lol after wipe is complete press alt+s to apply update! once it's finished reboot your device and you are ready to go!!
unfortunately the 1.6 i provided is not the DMD40, you still have to wait for that automatic update lol i have the 1.6 before the update... it is the official tmobile firmware its just not the latest.. never really bothered to search for latest one..
Click to expand...
Click to collapse
if any of those links are down post a reply and i will get a mirror up as soon as possible!

Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:

Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.

Your welcome guys. I ran up with some problems and my pc isn't available so ill try finishing this soon (probably in my iPod).

Okay yes this is perfect I can generate the links via the Dropbox app so hopefully this should be done soon!

Wow phew that took longer than expected (about 3 hours) safari is a horrible browser. Kept on crashing. Finally did all of it on notes and just pasted it on, revised and posted I hope this helps out! I will have the next steps up soon but for now you should be able to root your htc g1 with no problems what so ever have fun rooting guys. :laugh: I'm heading off to sleep. I'm exhausted. Later.:silly:

HTCDreamOn said:
Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:
Click to expand...
Click to collapse
Thanks!
I decided to finish up the rooting part since there was activity on the topic. Feel free to look over it just in case I may have missed something. I doubt it but hey we're not all perfect. Exhausted but pretty satisfied on how things are coming out. Mainly I'm happy to see that this is on the G1 oracle and that this this is recognized as a contribution to the g1 forums!

luggag3 said:
Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.
Click to expand...
Click to collapse
The rest is up for rooting! Have fun rooting!

Can anyone repost the file from part 1? It doesnt work...

Good work, thread stickied.
Thank you,
mf2112
XDA Moderator

duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Which one?

duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Sorry for the incovienience but since majority of this post was made on my iPod using notes since safari is higly unreliable with desktop version sites. This the format of notes is kept when copying to the post editor. Thus this is how the link was copied:
https://www.dropbox.com/s/y3slprukiqrt9nv/
EXAMPLE.DOC
Click to expand...
Click to collapse
Instead of like this:
https://www.dropbox.com/s/y3slprukiqrt9nv/EXAMPLE.DOC
Click to expand...
Click to collapse
Thus making it believe that there is a "RETURN" in the link giving you a 404 error. I fixed this along with some other 404 error links but it is all fixed. Either way next time there is a link that is not working quote it and I'll have it back up.

So I am no longer using my G1 but I will still finish this guide. I'm sorry for the wait guys.
Sent from my Nexus 4 using xda app-developers app

Nice guide.. you left 'adb shell' in the bypass google section

Thnxxx