Database Develop

attempt to update spl and now nothing?

renamed spl to update.zip and placed in root of SD
did alt+s, think i pressed alt+w accidentally, now when booting / rebooting
trying to get my home + power screen to reload, get "ROGERS" with the red "FASTBOOT USB" at the top, according to this
Rogers, heres your real root
http://forum.xda-developers.com/showthread.php?t=544654
"(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)"
then alt+s to load the rom, well the rom isn't on there becausei was following
installing the new spl
http://forum.xda-developers.com/showthread.php?t=532719
anyway to load the actual rom some other way, can't access the SD card with the fastboot skateboard screen or the rogers with the red "Fastboot usb" screen.
Confused, and frustrated, some help would be wonderful if you have the time, Thanks !

Did you flash the SPL before you flashed the radio?

xsnipuhx said:
Did you flash the SPL before you flashed the radio?
Click to expand...
Click to collapse
what i was trying to do

note: when attempting to flash
fastboot flash radio radio.img
Error: FAILED <remote: signature verify fail>
fastboot erase system -w
-okay
fastboot erase boot
-okay
fastboot erase recovery
-okay
fastboot flash recovery recovery.img
Error: FAILED <remote: signature verify fail>

Try redownloading the recovery.img There may have been a corrupted file somewhere.

xsnipuhx said:
Try redownloading the recovery.img There may have been a corrupted file somewhere.
Click to expand...
Click to collapse
Just did, receiving same error as before
"FAILED <remote: signature verify fail>
?

Check the original thread and see if anyone else is having the same problem.

xsnipuhx said:
Check the original thread and see if anyone else is having the same problem.
Click to expand...
Click to collapse
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha

JsnLlnd said:
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
Click to expand...
Click to collapse
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.

h.nocturna said:
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
Click to expand...
Click to collapse
Tried, won't go into recovery. stays at the Rogers start screen.
Anything else?

Quick update, was able to get into
fastboot boot recovery.img
and it loaded cyanogen cf 1.5? did alt+s and alt+w but theres no rom on the sd card right? hence its not doing anything?
am i figuring this out correctly here?
when i type in the fastboot boot recovery.img
downloading 'boot.img'...OKAY
booting...OKAY
where is this thing and how do i do this right im confusing myself blahhh
--------
rebooted, now i can't get into fastboot -_-
is this thing bricked now ?
use my fastboot boot recovery.img and it goes fastboot real quick, see a loading bar, then bam back to plain rogers screen. gonna try different recovery.
possibly adb push ? im learning this all just now more or less, so a direct path from my c:\android\sdk1.5_r3\tools: adb push ??? what goes here?
as far as the alt+x option goes , i can do it , but ums_enable isn't doing anything , any more details on that so i can get that rom on the SD card, think i will be good to go after that.

Stuck at t-mobile logo after flash danger spl

Phone spec:
HTC G1
4.2.15.1 cyanogen mod
2.22.23.02 Radio
Dream PVT 32B ENG
I've been reading several post but could not find a fix for my phone. I had ADB running before when I install the cyanogen mod. When I plug the phone into usb my computer cannot detect the phone. When I tried to run ADB it said there is no device. But when i tried the fastboot device my phone show up.
C:\android-sdk-windows\tools>fastboot devices
MB010LC08461 fastboot
What step should i take to fix my soft-brick phone?
Thank you

This is a real simple fix & there are many posts on this topic (which belongs in the Q&A section btw)
Getting stuck at g1 screen is standard after updating to that spl. It requires a rom be flashed after the update is complete
What recovery image do you have installed? Chances are, if you can access fastboot, recovery will work too. Boot into it, wipe, and flash a working rom from SD.
Otherwise: enter fastboot wipe and flash good system & boot partition images to the device

phimtau123 said:
Phone spec:
HTC G1
4.2.15.1 cyanogen mod
2.22.23.02 Radio
Dream PVT 32B ENG
I've been reading several post but could not find a fix for my phone. I had ADB running before when I install the cyanogen mod. When I plug the phone into usb my computer cannot detect the phone. When I tried to run ADB it said there is no device. But when i tried the fastboot device my phone show up.
C:\android-sdk-windows\tools>fastboot devices
MB010LC08461 fastboot
What step should i take to fix my soft-brick phone?
Thank you
Click to expand...
Click to collapse
You've got fastboot working... what's the problem? Load a system image and be happy!

Mod edit: not dev related, moved to q&a

I'm not very familiar with fastboot and it command.... I do however have the cyanogen rom on the sd card. wat command would i use to flash that rom?

[Q] Bricked my CEll upgrading the radio

Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.

Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.

ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.

americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza

my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?

americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.

This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!

lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?

billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.

ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.

[Q] An unknown SPL, please help!!!

My G1 had been shipped with a 0.95.1001 spl and 2.22.20.23 radio. I've been searching through the Internet but been directed to chinese websites. Now i realize that i have a chinese version OMG
I want to flash to safeSPL in order to follow MTD PH progress (by firerat http://forum.xda-developers.com/showthread.php?t=717874),then 2.xx radio and CaNNoN rom in the end. According to lbcoder in this post: http://208.100.42.21/showthread.php?t=698260 "There is no brick risk when going from a 0.95.x000 SPL --> 1.33.2003 ..... 0.95.x000 SPLs are compatible with 1.x and 2.x radios ..... In general, the safe way to change radio or SPL on the device is to go from 0.95.x000 --> 1.33.2003, and then ONLY use FASTBOOT for switching SPLs or RADIOs in the future, and ONLY switch between 1.33.2003 and 1.33.2005." But i dont know whether my 0.95.1001 spl is in compatibility with SafeSPL? Please help me because i cant read Chinese

any one got an idea?

jilee said:
My G1 had been shipped with a 0.95.1001 spl and 2.22.20.23 radio. I've been searching through the Internet but been directed to chinese websites. Now i realize that i have a chinese version OMG
I want to flash to safeSPL in order to follow MTD PH progress (by firerat http://forum.xda-developers.com/showthread.php?t=717874),then 2.xx radio and CaNNoN rom in the end. According to lbcoder in this post: http://208.100.42.21/showthread.php?t=698260 "There is no brick risk when going from a 0.95.x000 SPL --> 1.33.2003 ..... 0.95.x000 SPLs are compatible with 1.x and 2.x radios ..... In general, the safe way to change radio or SPL on the device is to go from 0.95.x000 --> 1.33.2003, and then ONLY use FASTBOOT for switching SPLs or RADIOs in the future, and ONLY switch between 1.33.2003 and 1.33.2005." But i dont know whether my 0.95.1001 spl is in compatibility with SafeSPL? Please help me because i cant read Chinese
Click to expand...
Click to collapse
You don't need to learn chinese, just click on translate this page link on google search result and you will get the pages in english.....

No, I dont need a help in translating. I dont know whether my spl is compatilble with the radio. I tried Google translate before asked here but still have no idea

My best guess is that it is *PROBABLY* all compatible.
You already *HAVE* a 2.x radio, and a 0.95 SPL. Most likely, [read: guess] those are just *translated* versions of what we already more commonly use.
My very best guess is that your 0.95.1001 SPL can safely be changed to 1.33.2003... and your radio version... should be fine as is... but again, it is an uncommon version number -- mostly familiar with 2.22.19.26 and 2.22.23.02. Yours appears to fall somewhere in between, so is probably similar to both.
In other words, **I** would go for it, but there is some uncertainty, so it remains your choice and your risk.
Note: If you change the radio *FIRST*, then *IF* it bricks at that stage, it WILL DEFINITELY be possible to softload an SPL via JTAG and recover the device that way...
Here is how *I* would go about this:
Copy the 1.33.2003 SPL and 2.22.23.02 RADIO update.zip files onto the SDCARD. BACKUP AND UPGRADE the RECOVERY PARTITION FIRST (from within the running normal operating system), then reboot the phone and boot on the custom recovery partition (but do NOT do a "reboot recovery" -- do a power off and power it on holding the home button). IF that custom recovery partition boots, then you can be fairly (but not absolutely) certain that it will all be compatible, so proceed with SPL and RADIO updates. Be aware that the phone will reboot TWICE during the upgrade of EACH -- so from recovery, write SPL's update.zip, it will reboot into update-hboot mode and do the REAL SPL write, then reboot again into recovery and format the cache partition. At this point you will write the RADIO'S update.zip, it will reboot into update-radio mode for the REAL write and reboot again into recovery to format the cache partition. At this point, you will be ready to go at it with custom system images, custom partition tables, etc.
But just remember: I take no responsibility for weird crap that happens. I don't know that SPL, so I don't know what it will do.
Here's another thought: does that SPL have fastboot mode? If it does, what partitions does it present? Does it allow you to fastboot boot?

BACKUP AND UPGRADE the RECOVERY PARTITION FIRST (from within the running normal operating system)
Click to expand...
Click to collapse
What do you mean by "backup and upgrade the recovery partition from within the running system" ?
Here's another thought: does that SPL have fastboot mode? If it does, what partitions does it present? Does it allow you to fastboot boot?
Click to expand...
Click to collapse
It doesnt have fastboot mode. When i start my phone while holding camera button, it shows me the "rainbow-Screen" with these info:
DREA*** PVT 32B MFG
HBOOT-0.95.1001
CPLD-4
RADIO-2.22.20.23
I can't make neither the dancing android nor the skateboards appear by pressing Back button, so I guess it doesn't have fastboot, but still allows to fastboot boot, am I right?

jilee said:
What do you mean by "backup and upgrade the recovery partition from within the running system" ?
Click to expand...
Click to collapse
Cant possibly spell it out any simpler than that..
It doesnt have fastboot mode. When i start my phone while holding camera button, it shows me the "rainbow-Screen" with these info:
DREA*** PVT 32B MFG
HBOOT-0.95.1001
CPLD-4
RADIO-2.22.20.23
I can't make neither the dancing android nor the skateboards appear by pressing Back button, so I guess it doesn't have fastboot, but still allows to fastboot boot, am I right?
Click to expand...
Click to collapse
Where do you get the idea that fastboot depends on pictures? Does it SAY "fastboot"?

Where do you get the idea that fastboot depends on pictures? Does it SAY "fastboot"?
Click to expand...
Click to collapse
hihi I am so sorry 'bout that mistake. Just because i didn't read the entry on Android Wiki carefully enough ^^. I reboot onto rainbow screen, plug phone into usb, press back button and then i see the letter FASTBOOT instead of Serial0 (i havent plugged into usb while doing this before, so that's why i can't figure out the point ^^ ) . So, I got fastboot
Originally Posted by jilee View Post
What do you mean by "backup and upgrade the recovery partition from within the running system" ?
Cant possibly spell it out any simpler than that..
Click to expand...
Click to collapse
Because I dont understand. You said "within the running system" so I did backup by Astro, because i cannot do nandroid backup (go to recovery, choose nand but it says i have to "nandroid-mobile.sh" via console --> i go to console, type "/sbin/nandroid-mobile.sh -b" , and then <CR> but it has an error about cannot write or make dir or smth like that). So, can you tell me a little bit further ^^ Because i am so noob
Edit: oh, the nand problem was just space. I cleaned up my sdcard and now it work fine^^
But i still dont understand the point "backup and upgrade in the system", and also "what partitions does the fastboot present". Please make it through ^^

Since you appear to have fastboot (it remains to be seen if it is a FUNCTIONAL or crippled fastboot)... find yourself any recovery image you like and do a "fastboot boot recovery.img". It'll do one of three things;
1) work,
2) give you some kind of not-authorized error,
3) try to boot and then lock up or otherwise crash.
Cross your fingers for (1).
As for the part you don't understand.... I suggest that if you can't understand that, you probably shouldn't be messing with firmware and need to go back to google and do some research before proceeding any further.

Need help, HTC DREAM

I was trying to do the post 911 rogers root on my htc phone, i got to the point where I Amon_ra's 1.7 recovery booted but then the home button wouldn't respone which is weird as it was used to boot into recovery.
after this I researched a bit and found that an eailer version of Amon_ra's recovery used the "Send" key instead of home, flashed that on and booted into it however it still asked me for "Home" to comfirm.
I then downloaded clockworks recovery and flashed it onto my phone but now the phone is stuck(waited 3 hours) at the ROGERS boot screen. I can boot into fastboot and my computer sees it as:
"list of device
HLXXXXXXXXXXXXXX fastboot"
x=numbers/letters
but whenever I try to do a fastboot command i get an error stating that remote is not allowed.
I am worried that this phone super derpped on me

What radio and SPL do you have? It will say in fastboot mode on the device. Also, can you still get into the ROM?

thanks for the reply the spl and radio are:
spl: 1.33.0010(?)
radio: 3.22.26.17
heres what it all 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"
no I can't get into the system rom, it is stuck at the bootspalsh screen.

You have a 3.xx (EBI1) radio but clockwork recovery only works with 2.xx (EBI0) radios.
I don't know if this will work but give it a shot:
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse

I downloaded the NBH file but I can't send the file to the phone it gives me this
nbh orange-1.58.73.2.nbh
sending 'nbh' (88683 KB)... FAILED (remote: not allow)
finished. total time: 0.005s
Click to expand...
Click to collapse
EDIT*: After following this guide http://wiki.cyanogenmod.com/index.php?title=Full_Downgrade_Guide_-_HTC_Dream I can now boot past the Rogers screen but its followed by a caution triangle. Recovery doesn't work "home"+power.
EDIT**: Further inspection i can get into recovery via atl+L at the triangle screen the load then rogers rom so I can make calls. The "home button" doesn't work so i can't flash or do anything in recovery mode as it ask for the "home" key to comfirm. Also home key is useless in normal boot(doesn't return me to home) which is wierd as my phone has never been dropped or water damaged, not even a scratch. Another thing since home key is now defucnt I can't reboot my phone or it will give me the error splash screen

Thats great news that you can get into recovery. You should try to get an unlocked spl before you do anything else. It looks like the home button not working is a hardware problem. If you feel comfortable doing it you could open the device because something might just not be contacting properly. You can find a service manual if you search for it.
You could try to use flash_image to flash img files in recovery through adb without the need for the home button.
http://wiki.cyanogenmod.com/index.php?title=Flash_image
Be sure to update to the latest radio before flashing your spl. This is very important!!!