Database Users

[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.

Updating HBOOT 08x to 1.01.000 on HTC Wildfire (including Rooting & S-OFF)

Hi guys
I just updated my HTC Wildfire from HBOOT version 08… to 1.01.0001 and I ran into many problems on the way. I’m just writing this guide to help out any other people that are in the same situation as me and don’t want to be searching Google for half a day finding solutions to every tiny problem. Please note this worked for me but I cannot guarantee it will work for you so follow this tutorial at your own risk!
Step 1: Find the RUU that has HBOOT 1.01.0001
I used RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe which you can find here.
And more specifically the download link is here (Credits to 3xeno for the RUU list and uploads).
Step 2: Extract the rom.zip from the RUU
There are many ways of extracting rom.zip the method I used is:
1. Run the RUU installer.
2. Go to your windows temporary folder.
3. Search for rom.zip
Another method that will definitely work and you can be sure you have the correct zip file is given here.
Step 3: Create a goldcard (easy way)
I found that flashing the above RUU was impossible without a goldcard and after lots of searching I found a link for downloading the GoldCardTool - a software that automates most of what you have to do and saves you lots of time.
Note: You need to format your SD card so backup anything important and then go to
Settings -> Storage -> Unmount SD Card
Then hit Erase SD card.
Now you are ready to create a Goldcard.
You can download the software here and follow the instructions in the readme file, they are very straight forward.
Step 4: Prepare the ROM for flashing
Rename rom.zip to PC49IMG.zip and place it on your SD card (in the root folder of your SD card ie. No folder within the SD card).
Now reboot your phone into the bootloader. Mine always starts with FASTBOOT in focus and I have to press the power button over BOOTLOADER to get it to scan the SD card for PC49IMG.zip. Once it finds the zip file it will open and parse the file and then ask you if you’d like to update. Press volume up to confirm then DON’T TOUCH ANYTHING.
Once the update is complete reboot the bootloader and make sure the HBOOT is 1.01.0001. Once that is confirmed you can boot into Android.
Step 5: Use AlphaRevx to get S-OFF and Clockwork recovery
Before you use AlphaRevx you will need to make sure you have the correct drivers.
Download the HTC Fastboot drivers which you can get here.
Also download Superuser which you will use later from here and copy this onto your SD card when you find the time!
(Credits for the links go to the guys at unrevoked for their wiki)
Now it’s time to get the Revolutionary software.
Go to http://revolutionary.io/ and download Revolutionary.
Now plug in your phone and make sure USB debugging is on, if it is not then go to Settings -> Applications -> Development and Enable USB debugging.
Now extract and run the Revolutionary software. It should open a command prompt and it will walk you through the installation, the serial number that you give in the website is given in the command prompt (it is not the same as the serial number on the back of your battery!). If you find an error right from the start it probably means you don’t have ADB drivers – Google sdk can help you out with that one. At the end of the installation it gives you the option to download and install Clockwork recovery mod – say yes (Y) to this option!
Step 6: Rooting your phone
Now that Revolutionary is complete you can reboot your phone into Clockwork Recovery. Select install application from zip file. Choose to select the zip file and then find the Superuser zip file that you download earlier (Superuser-3.0.7-efgh-signed.zip) and install it. If you forgot to put it on DON’T reboot your phone just go to the main menu of Clockwork Recovery. Go to mounts/partitions (I can’t remember the exact name) and at the bottom it says “mount SD card”. Select that and copy the file over to the SD card and then flash it using the directions given above.
Step 7: Flashing a custom ROM (or Fix for if your phone stops on boot screen)
You can either stop at Step 6 or continue to this step and flash a custom ROM.
To do this boot into Clockwork Recovery and do the following:
1. Wipe data
2. Clear cache
3. Clear Dalvik cache in advanced menu
I found that after I flashed a ROM without doing the above 3 steps it got stuck on the boot screen so please do the above 3 steps!
Now flash the ROM by choosing to install from a zip file. Reboot and you’re done!
I updated to Cyanogen mod 2.3.7 and I just want to throw in that Radio_13.55.55.24H_3.35.20.10.zip worked for me !
I really hope this tutorial helped. I just did it with my phone and it’s working well so I wanted to share what I did. Credits go out to everyone that put up tutorials on how to solve problems and all the download links and especially to the guys that wrote Revolutionary – it is an amazing software keep up the good work !
Cheers guys
Kerren

A very thorough guide and many people will benefit from this.
This is nearly exactly the same routine I followed from a guide which I can't remember where from now lol and very grateful help from 3xeno (yoda) but I don't think I did anything with alpharevx though and also I just flashed my cm7 nandroid after revolutionary to gain my superuser and I'm sure the serial part WAS my serial on phone but can't remember exactly.
Anyway my point is that after reading through your post it brought back the memory of the satisfaction of successfully s-offing my phone. great work.
"sent from me2u"

Cool!
Haha thanks man glad I could bring back memories
When it comes to the serial number I'm not completely sure, I had generated a code from the serial on the back of my battery and that didn't work. I then read the serial from command prompt and it seemed a lot shorter (also I got a code that worked ).
Maybe I made a mistake originally but all I know is that you don't have to rip your battery out to get the serial number - they give it to you anyway .
Thanks very much for the reply!

Ah yes that sounds familiar now.
"sent from me2u"

[Q] Downgrade issues?

I'm having issues during the downgrade process.. My temp root works fine but when I try to access PD15IMG.zip from the bootloader it skips the files.. From that screen it appears to be looking for PD15IMG.zip..
I tried swapping the files .. naming them vice versa but it does the same thing..
anyone seen this? any workarounds?

Maybe your PD15IMG.zip file got broken during download or while copying to sdcard. You can check that md5 hash of PD15IMG.zip exactly matches expected value (for 1.17.531.2 firmware it is 49d07f0ee7de1765a6a84cb12fa53110). There're different ways to do this: i.e. run "md5sum /sdcard/PD15IMG.zip" from adb shell or you can find some regular apps from Market that are able to do that - ES File Explorer, for example.
Forgot to mention:
Have you already decreased version number to 1.00.000.0 via misc_version utility? If you didn't - that's probably why your bootloader doesn't want to "update" the firmware - you should make it think your current version is below 1.17.531.2 before trying to downgrade.

Ok; I was following this GUIDE - http://forum.xda-developers.com/showthread.php?t=1178912
Which notes.. myTouch 4G: PD15IMG.zip
Should that be PG59IMG.zip for some devices? Or will the Bootloader switch to looking for PD15IMG.zip after the misc version step? I guess I'm just unclear on the stock rom step.. all other steps prior work and I'm temp rooted seeing the # indicator.
Checks out Like this -
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
thank you so much! I wish HTC would just let us disable Sense

pschramm said:
Should that be PG59IMG.zip for some devices? Or will the Bootloader switch to looking for PD15IMG.zip after the misc version step?
Click to expand...
Click to collapse
No, name of the image file differs from one device family to another. For MyTouch 4G it is definitely and exactly PD15IMG.zip (also, note: it's case-sensitive).
Btw I myself careful step by step followed this guide to downgrade, and everything went smooth.

I've tried the same approach.. I seem to be missing something here..
Use Volume up/down keys on the HTC Glacier for navigation and Power key for confirmation. Select Bootloader to flash the 1.17.531.2 firmware.
I click power.. It scrolls thru the files.. FINDS the PD15IMG.zip file..
I see a small blue progress indicator in the right upper corner.. that completes and it returns the bootloader screen..
Should I reboot now? Lose my temp root at that point.. (assuming it didn't update the ROM w/ my PD15IMG.zip file)
So I can't proceed to the busybox ROOT
_any help_ is greatly appreciated -
thanks guys(& gals )

You lose your temp root at the point when you reboot to bootloader to achieve the downgrade, way before you reflashed your ROM.
You don't need that temp root the moment you've downgraded. The whole purpose of downgrading is to make an easy temp-root and then permanent root available.
Please, just follow the rooting guide.

I should have been more clear.. I am following the guide exactly;
The guide says...
adb reboot boatloader
after pushing the ROM replacement to the SD card..
My issue is that the ROM doesn't appear to 'do anything' the bootloader finds it.. quick blue status bar and then nothing..
misc version reports the right version prior at a # prompt..
Just unsure of what I'm missing..
Followed the steps numerous times to the same result

There is no question on the screen after the blue bar is filled? In the same small font, on the left side?
In that case, the ROM doesn't pass verification. You'll need to turn off the phone, take out the SD card, put it into the computer (use card reader if you don't have one built in), format it, copy the ROM on it, and boot to bootloader again with the card in the phone.
If it still won't be recognized - then re-download the ROM and verify MD5SUM before using.

[Q] Rooting official 2.3.5 wirelessly

Hello!
How can one root official 2.3.5 rom without connecting to usb and adb?
The goal is to install custom ICS on U8800 that has no usb port - completely broken and even not charging phone. No warranty and repair cost is close to actual phone cost. So repairing is not an option.
Wireless adb app requires root first - so it is not an option for me also.
Any help is appreciated - I need ISC because I need ipsec vpn which is npt available in gingerbread.
I am ready to test any operation you suggest - I don't fear to brick the phone, need no backups.

It's impossible. I have one USB broken u8800 and that's why I use cm7 (.32) on it.
Sent from my U8800 using Tapatalk 2

Qqqxxxzzz said:
It's impossible. I have one USB broken u8800 and that's why I use cm7 (.32) on it.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing impossible I believe
Maybe we could find the trick - gingerbreak works on some roms - another fine exploit maybe.
I don't know - worth a try I think.

tranced1 I might have 1 possible solution for you. I've rooted my 2.3.5 some time ago and I've done a backup of boot.img.
I remember with froyo we could root it with boot.img "rooted". I bet this won't work on 2.3.5, but who knows right?
If you want to give it a try, I upload that boot.img for you.
EDIT: darn! Totally forgot you can't access bootloader directory without root & damaged usb port
Can't remember another way out... sorry

tranced1 said:
There is nothing impossible I believe
Maybe we could find the trick - gingerbreak works on some roms - another fine exploit maybe.
I don't know - worth a try I think.
Click to expand...
Click to collapse
Gingerbreak and z4root doesn't work. Only solution is build your own exploit.
Sent from my U8800 using Tapatalk 2

Is there any way to flash zip from stock recovery? I saw this root method for some samsung phones.
Does anybody know how to compile such .zip file?

tranced1 said:
Is there any way to flash zip from stock recovery? I saw this root method for some samsung phones.
Does anybody know how to compile such .zip file?
Click to expand...
Click to collapse
compiling zip is easy. Your problem is that we don't know how to sign it correctly.
Sent from my GT-P1000 using Tapatalk 2

I believe that you can use terminal emulator and zergrush exploit to root the phone.
The automatic root methods basicaly push the needed files on /data/local change permissions etc... All can be done with linux commands which are available from a terminal emulator. So I don't think that you need the usb cable to root the device. You can try investigate the runme.bat file from doomlord's root method and give the commands manually after you have put the files from files directory on sdcard.

dancer_69 said:
I believe that you can use terminal emulator and zergrush exploit to root the phone.
The automatic root methods basicaly push the needed files on /data/local change permissions etc... All can be done with linux commands which are available from a terminal emulator. So I don't think that you need the usb cable to root the device. You can try investigate the runme.bat file from doomlord's root method and give the commands manually after you have put the files from files directory on sdcard.
Click to expand...
Click to collapse
adb can access the phone as root user - from terminal file system is read-only, so even first step permission denied

Yes, you have right about that.
But, check this thread:
http://forum.xda-developers.com/showthread.php?t=1716068
the last post.
EDIT:
After reading the discription on first post of gingerbreak, I had another Idea.
Seems that gingerbreak uses sd card to temporary store the necessary for root files. So, maybe you can replace these files(and especially the exploit) whith those of doomlord's root app, before you press the root button, so to use the working zergrush exploit.

This is the B528 root bat script:
http://pastebin.ca/raw/2163499
@adb wait-for-device
@echo --- DEVICE FOUND
@echo --- reboot to bootloader
@adb reboot-bootloader
@echo --- flash the rooted bootimage
@fastboot boot boot.img
@echo --- reboot to nomal mode
@fastboot reboot
@echo --- wait for adb connect
@adb wait-for-device
@echo --- DEVICE FOUND
@adb remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
You're problem is in red... you have to flash the exploited boot image. The rest is just installing busybox, su and SuperUser.apk.
You have the stock recovery which allows you to flash .zip files, but they have to be signed correctly and I don't think that's possible.

VuDuCuRSe said:
This is the B528 root bat script:
http://pastebin.ca/raw/2163499
You're problem is in red... you have to flash the exploited boot image. The rest is just installing busybox, su and SuperUser.apk.
You have the stock recovery which allows you to flash .zip files, but they have to be signed correctly and I don't think that's possible.
Click to expand...
Click to collapse
To boot a different boot image, you have to use USB, atleast on fastboot.

dancer_69 said:
Yes, you have right about that.
But, check this thread:
http://forum.xda-developers.com/showthread.php?t=1716068
the last post.
EDIT:
After reading the discription on first post of gingerbreak, I had another Idea.
Seems that gingerbreak uses sd card to temporary store the necessary for root files. So, maybe you can replace these files(and especially the exploit) whith those of doomlord's root app, before you press the root button, so to use the working zergrush exploit.
Click to expand...
Click to collapse
Thanks for clues but seems there is no way - I cant execute exploit via ssh - permission denied I cant even chmod it.
Gingerbreak completely not working - no files created on sdcard.

Ι didn't find any other way on net. There are several discussions for this problem but not a solution. I think that the only way is to do it for an app. You can contact with the creator of gingerbreak or z4root to ask for it. Also I'll try to make an app myself, but my android developing knowledge is very basic, so don't count too much on this. If I have some kind of success I'll contact you via PM.
EDIT:
Try this mod, and if you are lucky...

dancer_69 said:
Ι didn't find any other way on net. There are several discussions for this problem but not a solution. I think that the only way is to do it for an app. You can contact with the creator of gingerbreak or z4root to ask for it. Also I'll try to make an app myself, but my android developing knowledge is very basic, so don't count too much on this. If I have some kind of success I'll contact you via PM.
EDIT:
Try this mod, and if you are lucky...
Click to expand...
Click to collapse
No I am obviously not the lucky one
My android development knowledge is zero, so if you can run zergRush from executable area it will be a very good start.
And I want to thank everybody for your support.

So, it doesn't work?
I just updated the file, so give it another try.
Also, check if you have logcat and usb debuging enabled(is needed for other methods, so maybe needed here too)

dancer_69 said:
So, it doesn't work?
I just updated the file, so give it another try.
Also, check if you have logcat and usb debuging enabled(is needed for other methods, so maybe needed here too)
Click to expand...
Click to collapse
Logcat: Cannot copy boomsh. : Permission Denied

I will revert to first beta now - and will test if it will work

I suppose this logat message is for z4root fail. Unfortunately I don't know what boomsh is. I just decompiled the apk and replaced the exploit, busybox, superuser, and su files with these from doomlord's root files directory.
So, easy solution didn't work. If I have something else I'll let you know.
EDIT:
I get some info about "cannot copy boomsh"
The exploit creates this file when run. This message appears when this file already exists and needed to be deleted from /data/local/tmp.
I checked z4root-mod on my device(which is already rooted and with ICS custom rom), and I get this message too.
The problem is that this file doesn't exist on my device, so I cannot delete it.
---------- Post added at 04:16 PM ---------- Previous post was at 03:17 PM ----------
I read on a forum that these apps(as z4root) run better after a fresh boot. So, install the latest apk(has newer files), reboot the device and run z4root again.

z4root is a froyo root exploit (I think) and seems "dead" for a long time.
Check Chainfire's Gingerbreak: http://forum.xda-developers.com/showthread.php?t=1044765