Build 6267 - how to extract "boot.img"? (Solved)

[Guest JFDee]

I could provide the "boot.img" of build 6267 if somebody would want to take a look at it.

Is there a way to extract it if the Streak is not yet rooted?

I have "adb" up and running on Windows and on Linux, and found the hints that /dev/mtd/mtd1 can be read out by "cat" to write the image to a file.

Now, what about "busybox"; would extracting work with a special version (with access rights to sdcard and including "cat") ?

The version from the Market seems to be very limited.

Edited August 9, 2010 by JFDee

[Guest fards]

I think ****************

that you can try this, instructions gleaned from loads of different places..

1) Install Android SDK or simply adb

2) Download busybox for Android from here http://benno.id.au/android/busybox

3) Launch Windows console (cmd) and go to the directory where busybox is with the "cd path/to/the/file" command.

4) "adb devices" <- Is your device detected ?

5) "adb push busybox /data/local/busybox

6) "adb shell"

7) cat /proc/mtd and check it's mtd0 that points to "boot"

8) cat /dev/mtd/mtd0 > /sdcard/6267boot.img

9) copy your extracted boot image off your sdcard to somewhere on your pc..

[code]

but I've read that it doesn't always result in a clean extracted boot.img.

worth a try though :)

if it does work (npot certain if it needs SU in adb shell) then hex compare it with a pauls rooted 4339 version, see what's different !

Edited August 10, 2010 by fards

[Guest JFDee]

Thanks for the detailed list!

I have access to the device via adb, that part worked.

Installing the new busybox worked too - though I don't know how exactly, because access to /data itself is impossible.

mtd0 points to "boot".

But the extract won't work - no permission:

$ ls -l /dev/mtd

crw------- root	 root	  90,  15 2010-08-07 22:39 mtd7ro

crw------- root	 root	  90,  14 2010-08-07 22:39 mtd7

crw------- root	 root	  90,  13 2010-08-07 22:39 mtd6ro

crw------- root	 root	  90,  12 2010-08-07 22:39 mtd6

crw------- root	 root	  90,  11 2010-08-07 22:39 mtd5ro

crw------- root	 root	  90,  10 2010-08-07 22:39 mtd5

crw------- root	 root	  90,   9 2010-08-07 22:39 mtd4ro

crw------- root	 root	  90,   8 2010-08-07 22:39 mtd4

crw------- root	 root	  90,   7 2010-08-07 22:39 mtd3ro

crw-rw-rw- root	 root	  90,   6 2010-08-07 22:39 mtd3

crw------- root	 root	  90,   5 2010-08-07 22:39 mtd2ro

crw------- root	 root	  90,   4 2010-08-07 22:39 mtd2

crw------- root	 root	  90,   3 2010-08-07 22:39 mtd1ro

crw------- root	 root	  90,   2 2010-08-07 22:39 mtd1

crw------- root	 root	  90,   1 2010-08-07 22:39 mtd0ro

crw------- root	 root	  90,   0 2010-08-07 22:39 mtd0

[Guest Vano3408]

here is boot image for 6267 backed up with the help of Koush's Clockwork Recovery..

Superboot r2 for build 4399 already applied...

6267 boot image

Thanks for the detailed list!

I have access to the device via adb, that part worked.

Installing the new busybox worked too - though I don't know how exactly, because access to /data itself is impossible.

mtd0 points to "boot".

But the extract won't work - no permission:

$ ls -l /dev/mtd

crw------- root	 root	  90,  15 2010-08-07 22:39 mtd7ro

crw------- root	 root	  90,  14 2010-08-07 22:39 mtd7

crw------- root	 root	  90,  13 2010-08-07 22:39 mtd6ro

crw------- root	 root	  90,  12 2010-08-07 22:39 mtd6

crw------- root	 root	  90,  11 2010-08-07 22:39 mtd5ro

crw------- root	 root	  90,  10 2010-08-07 22:39 mtd5

crw------- root	 root	  90,   9 2010-08-07 22:39 mtd4ro

crw------- root	 root	  90,   8 2010-08-07 22:39 mtd4

crw------- root	 root	  90,   7 2010-08-07 22:39 mtd3ro

crw-rw-rw- root	 root	  90,   6 2010-08-07 22:39 mtd3

crw------- root	 root	  90,   5 2010-08-07 22:39 mtd2ro

crw------- root	 root	  90,   4 2010-08-07 22:39 mtd2

crw------- root	 root	  90,   3 2010-08-07 22:39 mtd1ro

crw------- root	 root	  90,   2 2010-08-07 22:39 mtd1

crw------- root	 root	  90,   1 2010-08-07 22:39 mtd0ro

crw------- root	 root	  90,   0 2010-08-07 22:39 mtd0

[Guest fards]

Unfortunately that's not the right kernel then. As the superboot overwrites the original boot.img....

[Guest Vano3408]

Thrn JFDee can try to backup boot image using Koush's CRI tool

in menu choose Nandroid -> Backup

It will create boot.img file in sdcard/clockworkmod/backup

Unfortunately that's not the right kernel then. As the superboot overwrites the original boot.img....

[Guest fards]

lets hope so :)

[Guest JFDee]

Thrn JFDee can try to backup boot image using Koush's CRI tool

Thanks! Going to try that tonight.

[Guest Eric.Druse]

I could provide the "boot.img" of build 6267 if somebody would want to take a look at it.

Is there a way to extract it if the Streak is not yet rooted?

I have "adb" up and running on Windows and on Linux, and found the hints that /dev/mtd/mtd1 can be read out by "cat" to write the image to a file.

Now, what about "busybox"; would extracting work with a special version (with access rights to sdcard and including "cat") ?

The version from the Market seems to be very limited.

Boot.img of Build6267 is here:

Boot.img of Build 6267

[Guest Vano3408]

Thank you Eric, is that from baseband GAUSB1A111100-EU ?

Boot.img of Build6267 is here:

Boot.img of Build 6267

[Guest Vano3408]

Bingo. I flashed back stock boot.img posted by Eric and flashing buttons dissapeared... but th wonderful thing is the I still have ROOT!!

Thank you Eric, is that from baseband GAUSB1A111100-EU ?

[Guest fards]

Bingo. I flashed back stock boot.img posted by Eric and flashing buttons dissapeared... but th wonderful thing is the I still have ROOT!!

sounds good to me :)

[Guest JFDee]

All right, here is my freshly squeezed "boot.img". Zipped it for saving space.

streak_b6267_boot.img.zip

This is from GAUSB1A111100-EU, factory system.

It differs from Eric.Druse's; size unpacked is 5.242.880 bytes. Probably an "uncompressed compressed" file system.

Note: I had to use the old "clockwork" recovery image, version 2.5.0.1 wouldn't do anything except a beautifully black screen. In fact, it prevented the Streak from booting normally. No problems with the image from the ZIP package.

Edited August 9, 2010 by JFDee

[Guest Vano3408]

Clockwork CRI nandroid backup writes unneeded bytes, when backing up boot image. i deleted unnecessary bytes.

boot6762.img

Now size is same as Eric's image. But I compared both images by contetnt and have to say they have identical parts, but also big part is different..

Since Eric's image works fine for me and I didn't lost ROOT I will not probably do any flashing any more..

However, Paul may take a look in attached boot image to create SuperRoot image based on it.

All right, here is my freshly squeezed "boot.img". Zipped it for saving space.

This is from GAUSB1A111100-EU, factory system.

It differs from Eric.Druse's; size unpacked is 5.242.880 bytes. Probably an "uncompressed compressed" file system.

Note: I had to use the old "clockwork" recovery image, version 2.5.0.1 wouldn't do anything except a beautifully black screen. In fact, it prevented the Streak from booting normally. No problems with the image from the ZIP package.

[Guest marra2]

pardon my ignorance but this new image for booting does what exactly ? is it 2.1 or still 1.6 ?

[Guest fards]

pardon my ignorance but this new image for booting does what exactly ? is it 2.1 or still 1.6 ?

allows those whos streak came with 6267 rom and then messed it up by flashing the 4339 superboot to get a working rom again.. this is purely the boot stuff from that rom

its still 1.6 but we don't know what's different

Edited August 9, 2010 by fards

[Guest Eric.Druse]

Thank you Eric, is that from baseband GAUSB1A111100-EU ?

Yeah, that's right

[Guest Vano3408]

I compared your image with JFDee's and ramdisks are indentical, but kernels are totally different.. Wondreing why...

Yeah, that's right

[Guest JFDee]

I compared your image with JFDee's and ramdisks are indentical, but kernels are totally different.. Wondreing why...

Didn't Eric.Druse report something about a test version of the build that he has got his hand on?

This is probably different from the devices sold recently (those without any provider lock).

[Guest fards]

sounds like the one he posted is rooted...

[Guest geek78]

YOu can use the "one click root" from the nexus one to bee root even with the 6267 build (see xda-dev) :)

[Guest JFDee]

YOu can use the "one click root" from the nexus one to bee root even with the 6267 build (see xda-dev) :)

Yes, that worked nicely. Universal Androot 1.6 did it at the second attempt. Very comfortable. And reversable.

Thanks for the hint!

Now I can start coding :D

[Guest alfri68]

Bingo. I flashed back stock boot.img posted by Eric and flashing buttons dissapeared... but th wonderful thing is the I still have ROOT!!

i have 6267 root,and my led on the right flash.how have you flash this img(only 2.4 mb?)

[Guest llecaroz]

Who could provide the full 1.6 ROM 6267 & also 6267 recovery ROM (not the boot.img) to reset it to factory my DellStreak (not really satisfied by the 6947 O2 2.1 rom ?

(lot of random message saying that there is no more memory card or sim card !, lot of untraduced english sentences, facebook sync not working,...., market issues)

By the way, I will be able to fully go back to factory settings on my GAUSB1A111100-EU

thx in advance

regards

Edited August 20, 2010 by llecaroz

[Guest vivanno]

All right, here is my freshly squeezed "boot.img". Zipped it for saving space.

streak_b6267_boot.img.zip

This is from GAUSB1A111100-EU, factory system.

It differs from Eric.Druse's; size unpacked is 5.242.880 bytes. Probably an "uncompressed compressed" file system.

Note: I had to use the old "clockwork" recovery image, version 2.5.0.1 wouldn't do anything except a beautifully black screen. In fact, it prevented the Streak from booting normally. No problems with the image from the ZIP package.

Hi,

could you do the same dump for all important partitions ? i search a complet factory system backup of 1.6 GAUSB1A111100-EU for my streak :D