[OLED] 04/Oct r3: Superboot Root + MCRi

[Guest fluxcapacitor]

I'm having a problem, after trying to run fastboot, i get an error saying that adbwinapi.dll is missing. I do have android sdk fully installed along with the modded driver for the blade too (driver working) Have done a brief seach to download the dll, but the only link i could find wasn't working, any idea's please?

copy the file from the TOOLS folder of the SDK and paste it into the same folder as fastboot, worked for me and im a noobie!

Might be an idea to say in the original post what this does exactly for noobs?.

My lamens interpretation is that this roots the phone and installs a mod that lets you install future rom images directly from the SDCARD?

Edited September 26, 2010 by fluxcapacitor

[Guest anything-but]

Yes thanks for that.What i should have said is that when i plug my phone in to my pc and use device manager to update the drivers it just doesnt recognise them.Not sure what im doing wrong.USB in debug mode,mount or dont mount,tried both.(win 7 64).

Same here,win 7 (64) and device manager wont play ball with those drivers.

[Guest fluxcapacitor]

ok Noob alert!

I have done all the above and i now have the SuperUser app, but when i open up the adb shell and type su it says su: not found.

What have i missed?

ta!

[Guest Paul]

Strange... what about '/system/xbin/su'?

Seems to be OK here!

P

[Guest Paul]

Ah... could you check you have a /system/xbin dir?

Will fix this possiblity in a new MCRI release tomorrow.

P

[Guest fluxcapacitor]

xbin DIR is missing

cd system

# ls

lib

build.prop

framework

media

bin

usr

app

etc

fonts

lost+found

wifi

[Guest Paul]

OK, this will be fixed in a r2 release shortly.

P

[Guest fluxcapacitor]

OK thanks for all the help. Sometimes noobs are useful as we find all the bugs :lol:

[Guest Paul]

Updated to r2.

Note the superboot process only runs if /system/app/Superuser.apk is not found, so you may need to 'adb remount && adb shell rm /system/app/Superuser.apk && adb reboot' to let it do it's thang if you've already flashed r1.

P

[Guest Paul]

OK thanks for all the help. Sometimes noobs are useful as we find all the bugs B)

Aye.

The Blade situation is developing pretty fast atm too. :lol:

P

[Guest fluxcapacitor]

Updated to r2.

Note the superboot process only runs if /system/app/Superuser.apk is not found, so you may need to 'adb remount && adb shell rm /system/app/Superuser.apk && adb reboot' to let it do it's thang if you've already flashed r1.

P

su is there now... but

# su

# tar zcvf /sdcard/mcri-system.myrom.tar.gz -C /system *

tar: cache: No such file or directory

tar: config: No such file or directory

tar: d: No such file or directory

tar: data: No such file or directory

tar: default.prop: No such file or directory

tar: dev: No such file or directory

etc/

etc/bluez/

etc/bluez/main.conf

etc/bluez/input.conf

etc/bluez/audio.conf

etc/LsOmaClientSettings.xml

etc/loc_parameter.ini

etc/init.bt.sh

etc/customize/

etc/customize/default_homescreen.xml

etc/customize/default.xml

etc/gps_ouk.conf

etc/dbus.conf

etc/apns-conf.xml

etc/init.athwlan.sh

etc/NOTICE.html.gz

etc/bookmarks.xml

etc/init.goldfish.sh

etc/hosts

etc/wiperconfig.xml

etc/AutoVolumeControl.txt

etc/AudioFilter.csv

etc/init.qcom.bt.sh

etc/init.qcom.sdio.sh

etc/init.qcom.fm.sh

etc/vold.conf

etc/pvplayer.cfg

etc/cypress_firmware.bin

etc/init.qcom.coex.sh

etc/security/

etc/security/otacerts.zip

etc/security/cacerts.bks

etc/dhcpcd/

etc/dhcpcd/dhcpcd.conf

etc/dhcpcd/dhcpcd-run-hooks

etc/dhcpcd/dhcpcd-hooks/

etc/dhcpcd/dhcpcd-hooks/20-dns.conf

etc/dhcpcd/dhcpcd-hooks/01-test

etc/dhcpcd/dhcpcd-hooks/95-configured

etc/event-log-tags

etc/udhcpd.conf

etc/01_qcomm_omx.cfg

etc/permissions/

etc/permissions/qcrilhook.xml

etc/permissions/qcnvitems.xml

etc/permissions/com.google.android.datamessaging.xml

etc/permissions/com.google.android.maps.xml

etc/permissions/com.google.android.gtalkservice.xml

etc/permissions/required_hardware.xml

etc/permissions/android.hardware.touchscreen.multitouch.xml

etc/permissions/android.hardware.camera.autofocus.xml

etc/permissions/OmaDrmClient.xml

etc/permissions/platform.xml

etc/ppp/

etc/ppp/ip-up-vpn

etc/wifi/

etc/wifi/wpa_supplicant.conf

etc/pointercal

etc/firmware/

etc/firmware/yamato_pm4.fw

etc/firmware/yamato_pfp.fw

etc/firmware/wlan/

etc/firmware/wlan/qcom_cfg.ini

etc/firmware/wlan/cfg.dat

etc/firmware/wlan/qcom_nv.bin

etc/firmware/wlan/qcom_fw.bin

tar: init: No such file or directory

tar: init.blade.rc: No such file or directory

tar: init.goldfish.rc: No such file or directory

tar: init.qcom.post_boot.sh: No such file or directory

tar: init.qcom.rc: No such file or directory

tar: init.qcom.sh: No such file or directory

tar: init.rc: No such file or directory

tar: logo.bmp: No such file or directory

tar: mcri: No such file or directory

tar: persist: No such file or directory

tar: proc: No such file or directory

tar: root: No such file or directory

tar: sbin: No such file or directory

tar: sdcard: No such file or directory

tar: sqlite_stmt_journals: No such file or directory

tar: sys: No such file or directory

tar: system: No such file or directory

tar: usb.conf: No such file or directory

tar: var: No such file or directory

tar: error exit delayed from previous errors

# su tar zcvf /sdcard/mcri-system.myrom.tar.gz -C /system *

Permission denied

I notice there is a file called su2.3.1-bin-signed on my sdcard that is 0 bytes, that cant be right!?

Edited September 26, 2010 by fluxcapacitor

[Guest clivec]

copy the file from the TOOLS folder of the SDK and paste it into the same folder as fastboot, worked for me and im a noobie!

Might be an idea to say in the original post what this does exactly for noobs?.

My lamens interpretation is that this roots the phone and installs a mod that lets you install future rom images directly from the SDCARD?

Cheers, will try that later, when i get a chance

[Guest ed.dark]

Paul,

please check the MD5 hash for r2......

thanks

[Guest clivec]

ok, so i've tried flashing using fastboot now i have the dll in the right place, all seemed to go swimmingly, phone rebooted. But i have no root access. I was previously using the androot method, so i tried unrooting using androot, then ran mcri image again using fastboot. Still no root!!!

So, i've rerooted using androot method and all is ok, would like to see the fastboot method work tho for future updates.

Edit: could it be because superuser.apk was in the app dir?? As explained above, maybe unrooting does not remove it from there??

Edit2: Ok, i guessed right, just goes to show you should read the entire thread. Went in using rootexplorer, removed superused.apk from /system/app/ re-ran fastboot and mcri img r2, bingoooo! Worked. So as a note to anyone trying this after having already used the universal androot method, for this to work you need to manually remove superuser.apk even if you unroot first.

Edited September 26, 2010 by clivec

[Guest critch36]

I got this when following above insructions,I am using win7 64bit

http://www.modaco.com/style_images/blue/fo.../attach_add.png

[Guest fluxcapacitor]

I got this when following above insructions,I am using win7 64bit

http://www.modaco.com/style_images/blue/fo.../attach_add.png

You need the dll from the TOOLS folder in the android sdk, just copy it to the fastboot DIR

[Guest billyhl]

And the final line should read :-

For Windows

•When this finishes, from the command prompt run 'fastboot-windows reboot'

For linux

•When this finishes, from the command prompt run 'fastboot-linux reboot'

For mac

•When this finishes, from the command prompt run 'fastboot-mac reboot'

Just to make sure no one asks why it wont work.

Hope this helps.

Regards to all Billyhl.

[Guest clivec]

I got this when following above insructions,I am using win7 64bit

http://www.modaco.com/style_images/blue/fo.../attach_add.png

I posted this issue further back in the thread, as someone correctly pointed out, you need to copy that file from the adroidsdk\tools\ directory, into the directory you're running fastboot from. Worked for me anyway :lol:

[Guest Paul]

Updated r2 MD5 hash and tweaked instructions.

P

[Guest critch36]

You need the dll from the TOOLS folder in the android sdk, just copy it to the fastboot DIR

ok, I copied the files to the directory ,I no longer get the missing dll window but now the a command window appears then disappears straigt away with out insalling anything on the phone.

I have tried running it as admin aswell.

[Guest fluxcapacitor]

ok, I copied the files to the directory ,I no longer get the missing dll window but now the a command window appears then disappears straigt away with out insalling anything on the phone.

I have tried running it as admin aswell.

You need to run it from a command prompt not just double click on fast boot

[Guest Paul]

Fixed fastboot download.

P

[Guest critch36]

You need to run it from a command prompt not just double click on fast boot

ok working now as far as command prompt window open and now have a list ofcoomands ,update ,flashall etc

which one do I use

sorry if this seems a silly question but it is my first time on a android system,only jailbroken iphone before

[Guest stuartmc]

Thank you Paul my Blade rooted, waited 9 months before switching ROMs on WinMo but not even 9 days wait on Android before starting to "play". Can't wait for updated Vanilla ROM to play with.

[Guest Jakdaw]

This doesn't seem to work for me - when I run fastboot it seems to send over the boot.img but I never see the display change on the device & it doesn't seem to do anything. Any ideas?