82 replies to this topic

[pz8l8t]

insx, on Jun 28 2010, 12:02, said:

I also tried Barnacle WiFi Tether (which would be very handy). Starting the app also results in the "SU Request" hang. I assume I'm not rooted.

try putting the phone in usb debugging mode. settings->application->development and tick usb debugging. then at the su request hit always allow.

let me know how you get on with barnacle as i have having issues with it on my pulse mini (see thread barnacle wifi problems). if you manage to get it working fine, please report back and let me know on which network (i'm on tmobile).

[insx]

pz8l8t, on Jun 28 2010, 16:40, said:

try putting the phone in usb debugging mode. settings->application->development and tick usb debugging. then at the su request hit always allow.

let me know how you get on with barnacle as i have having issues with it on my pulse mini (see thread barnacle wifi problems). if you manage to get it working fine, please report back and let me know on which network (i'm on tmobile).

You lovely man! It seems USB debugging mode allowed the superuser app to do its thing.

Here's what happened with Barnacle. (I'm on O2).

Tried to open www.google.co.uk on my daughter's Win 7 netbook (with firefox). Barnacle said "Unexpected error occurred! Inspect the log and try the troubleshooting guide".
Couldn't see anything useful in the log.
Started Barnacle again, tried to open google.co.uk again, same error.
Started Barnacle again, pinged google.co.uk successfully
Opened www.google.co.uk with firefox successfully
Searched for "test" and opened a couple of results successfully
Opened youtube.com successfully and managed to watch a video (at least a couple of seconds, connection was very slow).
No sign of the connection breaking. Strange!

[pz8l8t]

insx, on Jun 28 2010, 17:19, said:

You lovely man! It seems USB debugging mode allowed the superuser app to do its thing.

Here's what happened with Barnacle. (I'm on O2).

Tried to open www.google.co.uk on my daughter's Win 7 netbook (with firefox). Barnacle said "Unexpected error occurred! Inspect the log and try the troubleshooting guide".
Couldn't see anything useful in the log.
Started Barnacle again, tried to open google.co.uk again, same error.
Started Barnacle again, pinged google.co.uk successfully
Opened www.google.co.uk with firefox successfully
Searched for "test" and opened a couple of results successfully
Opened youtube.com successfully and managed to watch a video (at least a couple of seconds, connection was very slow).
No sign of the connection breaking. Strange!

That's good to hear that you've finally got it working. On mine I can access google all day without any problems, however other sites like youtube, skyports, ebay I keep getting the "Unexpected error occurred! Inspect the log and try the troubleshooting guide" and in the log itself, "NAT exited: message to long". Not sure if it's the phone or the network. Keep me posted on how reliable your connection is.

[dt_matthews]

can this be reversed / uninstalled - I seem to have a problem with accessing the phone's memory card via usb since installing this!

[insx]

dt_matthews, on Jul 1 2010, 21:53, said:

can this be reversed / uninstalled - I seem to have a problem with accessing the phone's memory card via usb since installing this!

That's interesting. I can't access mine either but I assumed I was doing something wrong as I'd never tried it before rooting the phone. I gave up and used a card reader.

[dt_matthews]

insx, on Jul 1 2010, 22:41, said:

That's interesting. I can't access mine either but I assumed I was doing something wrong as I'd never tried it before rooting the phone. I gave up and used a card reader.

hmm, intersting but not in a  good way! can anyone advise, i really need usb access to my device and this patch appears to have stopped direct usb access ??

[m2te]

insx, on Jul 1 2010, 22:41, said:

That's interesting. I can't access mine either but I assumed I was doing something wrong as I'd never tried it before rooting the phone. I gave up and used a card reader.

I have experienced this too after flashing some debranding update.zip files I have been working on through the recovery console. Flashing with a Rom downloaded from the heuwua site fixes the problem for me but you then loose all the settings etc.

I did notice it seems to start doing this after I caused a boot loop through me having a bug in my update.zip file, have you guys experienced a boot loop at any time?

I don't think the problem is the root itself as I have flashed a rooted update.zip many times, maybe the rooting process takes the usb out in some circumstances..

[dt_matthews]

m2te, on Jul 1 2010, 22:55, said:

I have experienced this too after flashing some debranding update.zip files I have been working on through the recovery console. Flashing with a Rom downloaded from the heuwua site fixes the problem for me but you then loose all the settings etc.

I did notice it seems to start doing this after I caused a boot loop through me having a bug in my update.zip file, have you guys experienced a boot loop at any time?

I don't think the problem is the root itself as I have flashed a rooted update.zip many times, maybe the rooting process takes the usb out in some circumstances..

hmm, well i need to persist a bit more to be sure what has/hasnt happened but its certinaly not behaving as it was before the rooting execution...

[insx]

I haven't experienced a boot loop as far as I know. I did get some error about acore not responding after running superboot.

[insx]

Just to let you know that I can't access the SD card via USB on my wife's pulse mini either. It was bought off ebay but I'm pretty sure it's not rooted (su: permission denied). I just get "Please insert a disk into drive F:".

It's different on mine, I can get drive F up but it only contains the T-mobile setup files and documentation.

Maybe I'm looking at the same thing and those files have been deleted on my wife's phone.

[m2te]

insx, on Jul 2 2010, 17:20, said:

Just to let you know that I can't access the SD card via USB on my wife's pulse mini either. It was bought off ebay but I'm pretty sure it's not rooted (su: permission denied). I just get "Please insert a disk into drive F:".

It's different on mine, I can get drive F up but it only contains the T-mobile setup files and documentation.

Maybe I'm looking at the same thing and those files have been deleted on my wife's phone.

I think that is different. From what I remember when the USB mounting is broken the T-Mob setup files no longer worked as well as the SDCARD.

[insx]

I don't know what's changed but today I plugged in the USB cable, dropped down the USB notification, selected mount and there it is - drive F: with full access to my micro SD card in the phone.

[mohrun]

I have a Huawei U8100 that people are reporting can be rooted using "1.0-pulsemini-superboot.zip". Before running it I thought I'd "look under the hood" and see how it works.

I read http://android.modac...boot-explained/ and figured this one should be similar. I used split_bootimg.pl to unpack the "boot.superboot.img" kernel + ramdisk. Unfortunately it seems that the ramdisk is not a valid gzip:ed cpio-archive.

Anyone know how I can have a look inside the ramdisk image? Paul? :-)

[redmongoose]

Thanks Paul, worked a treat.

[The Only Boink]

Hi,

Being a newbie and all I need some guidance.


My primary objective is simple  - I wish to unlock my Huawei U8100/T-Mobile so that I can use
which ever carrier I see fit.


What do I need to do once Superboot is "installed"?

I have done according to the guide - that is - starting the phone in bootloader mode and run the install-superboot-windows.bat.
The phone booted and then rebooted.

It seems to me that what was suppose to happened didn't happened.
I've tried to do this a few times with the same outcome.

Do I need to run command lines from a console?
Do I have to flash the phone with a costume ROM? and if so, where do I find such ROM?

Cheers!

[Case_]

mohrun, on Jul 14 2010, 16:06, said:

I have a Huawei U8100 that people are reporting can be rooted using "1.0-pulsemini-superboot.zip". Before running it I thought I'd "look under the hood" and see how it works.

I read http://android.modac...boot-explained/ and figured this one should be similar. I used split_bootimg.pl to unpack the "boot.superboot.img" kernel + ramdisk. Unfortunately it seems that the ramdisk is not a valid gzip:ed cpio-archive.

Anyone know how I can have a look inside the ramdisk image? Paul? :-)

I second this question - I'm interested in rooting Vodafone 845, which, according to some reports, can also be rooted using this guide, but I'd also like to take a look at what I'm doing and perhaps have a way to revert back to default unrooted kernel image. I'm quite familiar with the process on Magic 32A (I've released some stuff before on XDA), but using the usual split_bootimg.pl on this .img file doesn't result in anything useful. Any idea how to split this .img file and how to eventually put it together again? Linux or Windows, doesn't really matter. I reckon there need to be some changes done in the split_bootimg.pl script, Thanks a lot for any info.

[gforums]

You should be able to use the same split_output script.

The "recovery.img" file is the "system.img".
"file20.mbn" is the "boot.img"

For me, this worked well. at least on a pulse mini.

[mohrun]

Case_, on Jul 28 2010, 13:10, said:

I second this question - I'm interested in rooting Vodafone 845, which, according to some reports, can also be rooted using this guide, but I'd also like to take a look at what I'm doing and perhaps have a way to revert back to default unrooted kernel image. I'm quite familiar with the process on Magic 32A (I've released some stuff before on XDA), but using the usual split_bootimg.pl on this .img file doesn't result in anything useful. Any idea how to split this .img file and how to eventually put it together again? Linux or Windows, doesn't really matter. I reckon there need to be some changes done in the split_bootimg.pl script, Thanks a lot for any info.

I would be surprised if the problem is in split_bootimg.pl. It is a pretty simple script that splits the image into the parts that make up an Android boot image. The format is specified in

http://android.git.k...otimg/bootimg.h

Either Huawei decided to use a different / modified format, or the kernel in the superboot-image has some special code to handle a different type of initrd. My money is on the latter. It would be a simple modification to obfuscate, encode or encrypt the ramdisk and let the kernel reverse the process after loading the initrd into RAM (before using it). The fact that the superboot initrd seems compressed (does not shrink when run through gzip) at least appears to strengthen this theory.

I tried to PM Paul, but no reply. He is probably busy rooting some phone or another, and I guess we are all happy that he makes that his no 1 priority

Time does not permit me to delve deeper into this. I'm just accepting I don't have root on my phone for now.

[mohrun]

mohrun, on Jul 31 2010, 00:48, said:

Time does not permit me to delve deeper into this. I'm just accepting I don't have root on my phone for now.

Sometimes insomnia arrives at the most opportune moment

I spent most of the night with Pauls superboot image, a hexeditor and google. It appears there is no obfuscation, it is just stored in a way that a noob like me does not quite understand yet I managed to extract the files, and a quick look indicates it works as explained in the thread I indicated in my previous post.

/superboot/superboot.sh:

mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
rm -rf /data/xbin
rm -rf /data/bin
rm /data/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su
cat /superboot/su>/system/bin/su
chmod 4755 /system/bin/su
cat /superboot/Superuser.apk>/system/app/Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system

I will have a closer look, then I'll post details of how to reproduce for anyone else interested in this.

[Case_]

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)