82 replies to this topic

[mohrun]

Case_, on Aug 1 2010, 02:19, said:

So, had a little time today to try some more and it seems like there IS something wrong with the split_bootimg.pl script after all. If I use unpack-bootimg.pl instead, I do get proper ramdisk extracted from the boot.superboot.img... (and hopefully kernel image as well, although it's called *-kernel.gz, but doesn't seem to be a gzip file)

I think split_bootimg.pl splits the image per the spec in bootimg.h, but it looks like there for some reason is an extra empty page (2048 bytes) after the header page in the superboot image. Modifying the script as below will make it extract a valid ramdisk image.

The kernel is in zImage format (which contains an unpacker and a gzipped kernel).

The reason unpack-bootimg.pl works is that it does not follow the spec, it just looks for some magic bytes and splits the file there. This is unreliable, but will in most cases extract the ramdisk properly, even if the file does not follow the bootimg.h structure.

--- split_bootimg.pl	2008-12-03 21:59:25.000000000 +0100
+++ split_bootimg_modified.pl   2010-08-01 12:21:53.000000000 +0200
@@ -72,7 +72,7 @@
 my $m = int(($RAMDISK_SIZE + $PAGE_SIZE - 1) / $PAGE_SIZE);
 my $o = int(($SECOND_SIZE + $PAGE_SIZE - 1) / $PAGE_SIZE);

-my $k_offset = $PAGE_SIZE;
+my $k_offset = 2*$PAGE_SIZE;
 my $r_offset = $k_offset + ($n * $PAGE_SIZE);
 my $s_offset = $r_offset + ($m * $PAGE_SIZE);

I am still trying to figure out why the superboot image (as well as Pauls Amon Ra recovery image) does not follow the bootimg.h spec...

Edited by mohrun, 01 August 2010 - 07:26 PM.

[Maxrunner]

I assume the end button is the right one. this is a vodafone 845 which suposedly also works with this but when i enter the super user permissions nothing appears.
The compile number is UB120V100R001C02B220

[damnsmalldan]

The 845 is a fairly similar device which means this could work.

Whenever i try on Ubuntu 10.04 i get the message:
"<Waiting for device>"

I follow the steps exactly for Linux, but it just simply won't work.
Has anyone got this working on Ubuntu? If so, what did you do?

[Case_]

mohrun: Thanks for the script patch. Still not able to create a working boot.img, but I think my problem is now the repacking of the boot.img.

damnsmalidan: You need to have adb and fastboot working first, which means modifying android udev rules for the PC to recognise the new device and installing and configuring usb_modeswitch.

[geevz]

Got it working fine so fine. mine was build XXXXXXXXXXSP06.

For those with USB mounting issues : stop the usb debugging mode and it will mount the SD Card.  

[jasonXXx]

Hi any chance of updating the superuser APK on xda developers there is a new version Superuser 2.3.1 here is a link http://forum.xda-dev...ad.php?t=682828

Also does this work fully and not mess other things up as i see people saying sd card is not mounting?

[jasonXXx]

geevz, on Aug 12 2010, 16:21, said:

Got it working fine so fine. mine was build XXXXXXXXXXSP06.

For those with USB mounting issues : stop the usb debugging mode and it will mount the SD Card.  

Does not work still no usb mounting and it also happens when flashing any rom thats not stock also any recovery image this need fixing untill this is fixed i will stick with stock everything. It feels to me that the pulse mini is dead before its even had a chance no developers and no one interested in helping.

[jasonXXx]

jasonXXx, on Aug 20 2010, 22:14, said:

Does not work still no usb mounting and it also happens when flashing any rom thats not stock also any recovery image this need fixing untill this is fixed i will stick with stock everything. It feels to me that the pulse mini is dead before its even had a chance no developers and no one interested in helping.

Ok got it working usb fine since i got no help i solved myself and this conferms the superboot make usb stop working. Ok step 1 install superboot and reboot device dont unplug usb keep it in all the time when system reboots then reboot back to fastboot and reinstall orig bootloader that way we have su but with orig bootloader this works 100% fine but if you wipe your system you will have to do the steps again. i have attached orig U8110V100R001C85B215SP02TMOUK boot image.

Attached Files

•  orig_boot.img   2.43MB   53 downloads

[Jerry786]

Hi all. If i root my phone, will it get rid of the annoying and painfully slow T Mobile branding logo on startup?

Also, it seems as though rooting is causing a few problems, Can anyone confirm that everything is working fine on the Mini once rooted?

Thanks

Edited by Jerry786, 21 August 2010 - 11:54 PM.

[jasonXXx]

Jerry786, on Aug 22 2010, 00:44, said:

Hi all. If i root my phone, will it get rid of the annoying and painfully slow T Mobile branding logo on startup?

Also, it seems as though rooting is causing a few problems, Can anyone confirm that everything is working fine on the Mini once rooted?

Thanks

Hi no it will not get rid of the t-mobile stuff and yes there are problems with usb mounting also the superuser app is very old. If you read my post above there is no usb problems but if you wipe you will need to redo steps to kepp rooted or i have just found a new way what sticks. step 1 install superboot dont unplug usb reboot when installled step 2 boot clockwork recovery via fast boot remember dont install clock work or usb problem is back just boot it via fastboot download the su-2.3.3 update.zip and place in your sdcard when you have booted clockwork select install update.zip from sdcard when done reboot backinto bootloader and flash the orig-bootloader attached abouv now you have the latest su-2.3.3 and now go into your settings and do a master reset. Thats it this way you will have stock all but rooted with the latest superuser app and no usb probs also it will stick when you master reset.

Attached Files

•  su_2.3.3.zip   136.29K   337 downloads
•  clockwork_recovery_v1.8.1.4.img   3.35MB   260 downloads

Edited by jasonXXx, 22 August 2010 - 10:45 AM.

[grogers3.14]

Case_, on Aug 8 2010, 16:16, said:

damnsmalidan: You need to have adb and fastboot working first, which means modifying android udev rules for the PC to recognise the new device and installing and configuring usb_modeswitch.

What are the udev rules for this device? I have

SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1034", MODE="0666"

and run usb_modeswitch to get the right product id (details here) and adb devices still does not list it.

[Jerry786]

jasonXXx, on Aug 22 2010, 11:14, said:

Hi no it will not get rid of the t-mobile stuff and yes there are problems with usb mounting also the superuser app is very old. If you read my post above there is no usb problems but if you wipe you will need to redo steps to kepp rooted or i have just found a new way what sticks. step 1 install superboot dont unplug usb reboot when installled step 2 boot clockwork recovery via fast boot remember dont install clock work or usb problem is back just boot it via fastboot download the su-2.3.3 update.zip and place in your sdcard when you have booted clockwork select install update.zip from sdcard when done reboot backinto bootloader and flash the orig-bootloader attached abouv now you have the latest su-2.3.3 and now go into your settings and do a master reset. Thats it this way you will have stock all but rooted with the latest superuser app and no usb probs also it will stick when you master reset.

Thanks. Might give it a go..but i dont know if its worth it. Will rooting and installing a custom ROM make the phone any faster?

Also, if i root and install ROM, will it wipe erase all data?

[jasonXXx]

Jerry786, on Aug 24 2010, 04:23, said:

Thanks. Might give it a go..but i dont know if its worth it. Will rooting and installing a custom ROM make the phone any faster?

Also, if i root and install ROM, will it wipe erase all data?

Rooting will not wipe data but installing a rom will most custom roms are faster what i would do is root the method i told you and then make your own update.zip with all extra apps and changes then flash it on stock rom.

[Jerry786]

jasonXXx, on Aug 24 2010, 12:30, said:

Rooting will not wipe data but installing a rom will most custom roms are faster what i would do is root the method i told you and then make your own update.zip with all extra apps and changes then flash it on stock rom.

Thanks might rooting it tonight. I assume it doesn't void warranty....

Typed this on my pulse mini using side it keyboard, don't know how I managed without it considering the mini keyboard of the pulse!

[Jerry786]

P S. I didnt get what you said regards to u u update. Zip

Edited by Jerry786, 24 August 2010 - 08:54 PM.

[jasonXXx]

Jerry786, on Aug 24 2010, 21:53, said:

P S. I didnt get what you said regards to u u update. Zip

Sorry the attachment su_2.3.3.zip rename it update.zip and flash it this is the latest superuser and su app thats root.

[Jerry786]

tried rooting but hangs at waiting for device.......

[Jerry786]

tried rooting but hangs at waiting for device.......

[jasonXXx]

Jerry786, on Aug 26 2010, 22:01, said:

tried rooting but hangs at waiting for device.......

Ok scrap all of above lots of what i sead is not needed.

To start make sure your on stock rom with default bootloader and recovery make sure you have the su update.zip link http://android.modac...t...st&id=61279  in the root of your sdcard. Link to clockwork recovery put this in the same folder as fastboot http://android.modac...t...st&id=61280

Step 1 boot to bootloader mode by powering off the phone and then pressing redkey and volume down plus power button at the same time for 5 secs then open command shell on windows and type fastboot boot clockwork_recovery_v1.8.1.4.img then press enter and wait for recovery to boot then select install update.zip from sd and select the update.zip attached above and that will flash super user and root your phone. Then reboot.

Thats it you will then be rooted with no problems with the latest superuser app and su it will also stick on master reset. Tested and working with no problems.

There are other ways of rooting like superboot but then come usb problems this way you will have stock recovery as we only boot CLOCKWORK not flash it and we have stock bootloader as we did not use superboot also the lates version of superuser/su. Hope this helps

Edited by jasonXXx, 26 August 2010 - 09:24 PM.

[Jerry786]

Excuse my ignorance but i did not understand this bit

Link to clockwork recovery put this in the same folder as fastboot http://android.modac...t...st&id=61280

Thanks