Jump to content

Huawei U8230, dump 2.1 stock rom without root.

Guest bUg.

By Guest bUg.
in T-Mobile Pulse

 Share

Recommended Posts

Guest bUg.

Guest bUg.

Posted
Posted

Last week our operator started selling this mobile phone with 2.1 android aboard.

Firmware Version - 2.1-update1

Baseband Version - 6383

Kernel Version - 2.6.29-perf

Build Number - U8230V100R001C152B820

Build Date - 11 May 2010

Partitions

mtd0: 00500000 00020000 "boot"

mtd1: 00500000 00020000 "recovery"

mtd2: 00140000 00020000 "misc"

mtd3: 00060000 00020000 "splash"

mtd4: 0aa00000 00020000 "system"

mtd5: 04600000 00020000 "cache"

mtd6: 0ca60000 00020000 "userdata"

mtd7: 01400000 00020000 "userdata2"

I'm trying to get stock firmware dump.

Firstly i downloaded TMN A1 superboot and booted image using fastboot. It stopped on redbull splashscreen, but i was able to see phone in 'adb devices'. adb shell gives error - 'exec '/system/bin/sh' failed: No such file or directory (2)'.

Then i tried to split image file into kernel and ramdisk and used 'fastboot kernel ramdisk'. Phone ignored this kernel booted using stock firmware.

Also i tried AmonraRecovery for pulse phone, it booted with many errors (suach as cant read CACHE, etc). both backup methods said about same errors.

Now i dont have any idea how to dump original rom ;)

P.S. on other same phone we tried to flash tmn a1 superboot and we got root, but using this way we loosing default boot partition.

Thanks for any help.

Link to comment
Share on other sites
Guest DanWilson

Guest DanWilson

Posted
Posted (edited)
CUT

Unless fastboot allows you to copy BACK the partitions, I think you have no dump.... Will report in a wee min to see if it does, then I'll Google it for you...

Nope - epic fail. No fastboot things (I did find and update.zip installer that I shall try, need to update FLB-MOD), and Google gave me nothing. I'm sorry dude.

Who is your carrier? (Which phone?)

Edited by DanWilson
Link to comment
Share on other sites
Guest Speckles

Guest Speckles

Posted
Posted

I'm sure that partition layout you have is different to the one which the Hungarian ROM gives you.

So in which case, you'll need an UPDATA which partitions in that format before you could apply it. Unless of course you just want to dump the kernel fs and see whats different.

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted
Who is your carrier? (Which phone?)

You wont find it anyway, but it's Life operator (half Turkcell) from Belarus. Phone called Huawei U8230 without any operator name.

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted (edited)
I'm sure that partition layout you have is different to the one which the Hungarian ROM gives you.

So in which case, you'll need an UPDATA which partitions in that format before you could apply it. Unless of course you just want to dump the kernel fs and see whats different.

May be you know if there is a way to change AmonraRecovery or TMN fastboot for this partition layout?

P.S. Seems like recovery image gives same errors like in this post.

Edited by bUg.
Link to comment
Share on other sites
Guest Speckles

Guest Speckles

Posted
Posted

I wouldn't have a clue, but the AmonRA recovery works on both the 1.5 and 2.1 partition layouts, so I wouldn't expect that much problems.

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted

I upacked 1.5.2-pulse-amorarecovery image and found that there is wrong partitions in fstab. repacked it with fixed fstab. will try it after i will get phone back from service ( i broke rom a bit xD )

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted

tried to fill right info in fstab, but still getting same errors. also when recovery image booted i used adb shell and did cat /proc/mtd. result:

dev: size erasesize name

I think it means that kernel didnt found any nand flash. am i wrong? and how to fix it?

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted

found in dmesg :lol: may be it help someone

<5>[1, swapper] [ 0.821766] Creating 8 MTD partitions on "msm_nand":

<5>[1, swapper] [ 0.821795] 0x000002600000-0x000002b00000 : "boot"

<5>[1, swapper] [ 0.824601] 0x000002b00000-0x000003000000 : "recovery"

<5>[1, swapper] [ 0.826700] 0x000003000000-0x000003140000 : "misc"

<5>[1, swapper] [ 0.828796] 0x000003140000-0x0000031a0000 : "splash"

<5>[1, swapper] [ 0.831020] 0x0000031a0000-0x00000dba0000 : "system"

<5>[1, swapper] [ 0.833208] 0x00000dba0000-0x0000121a0000 : "cache"

<5>[1, swapper] [ 0.835398] 0x0000121a0000-0x00001ec00000 : "userdata"

<5>[1, swapper] [ 0.837520] 0x00001ec00000-0x000020000000 : "userdata2"

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted

problem found in recovery dmesg

nandid: 5500bcec maker ec device bc

Unsupported Nand,Id: 0x5500bcec

=================================================================

flash_onenand_probe: manufacturer_id = 0x54

flash_onenand_probe: device_id = 0xec

flash_onenand_probe: version_id = 0xbc

flash_onenand_probe: data_buf_size = 0x0

flash_onenand_probe: boot_buf_size = 0x55

flash_onenand_probe: num_of_buffers = 0x54

flash_onenand_probe: technology = 0xec

=================================================================

flash_onenand_probe: Detected an unsupported device

going to find fix for it :lol:

Link to comment
Share on other sites
Guest McSpoon

Guest McSpoon

Posted
Posted
I'm trying to get stock firmware dump.

If you just want the stock firmware of the U8230V100R001C152B820 then it's on the Huawei website.

http://www.huaweidevice.com/worldwide/down...001C152B820.zip

Huawei have labeled it "U8230V100R001C152B820(White Russia BeST)". I'm not sure if "White Russia BeST" is a reference to a mobile carrier or perhaps they consider Belarus to be totally awesome.

Note: There is a Perl script called split_updata.pl which can unpack the firmware and extract the boot.img and system.img partitions, which may be of use to you.

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted (edited)

erm, i checked it yesterday and there wasnt this firmware. but 'white russia best' is right carrier and i think they put it on site tonight. that's good :lol: thanks.

but anyway i still trying to run amon ra on this device and i will do it :D it's already not because i need it, now it's a challenge!

Edited by bUg.
Link to comment
Share on other sites
Guest McSpoon

Guest McSpoon

Posted
Posted
One more question about his firmware. There is only one file UPDATE.APP. hot i can split it to kernel, ramdisk, system etc... ?

Try using the split_updata.pl script from this thread.

It should extract the boot.img, system.img and various other files.

Then use the usual unpack-bootimg.pl or split_bootimg.pl scripts from this page to obtain the kernel and ramdisk from the boot.

Link to comment
Share on other sites
Guest bUg.

Guest bUg.

Posted
Posted

Sadly there is no crc16 for mac (atleast file that i can use w/o any additional hands moves xD), will try this on my notebook with linux tomorrow. have to sleep a bit.

Link to comment
Share on other sites
Guest McSpoon

Guest McSpoon

Posted
Posted
Sadly there is no crc16 for mac (atleast file that i can use w/o any additional hands moves xD), will try this on my notebook with linux tomorrow. have to sleep a bit.

Don't worry about the crc16 part. You could edit the script to remove the line "$calculatedcrc=`./crc $BASEPATH$outfilename`", or perhaps create a fake program called 'crc' . Without it the script should still be able to extract the files (although it has never been tested on the U8230V100R001C152B820 firmware).

Link to comment
Share on other sites
Guest arlindo.costa

Guest arlindo.costa

Posted
Posted

:D :D :)

Thanks a lot bUg. THis was just what I need to get Amonra working on my TMN A1 (thought it only works when I boot the recover.img from fastboot, when I reboot into recovery it hangs on RBM screen). I think there is going to be a lot of happy folk in Portugal in the next couple of days with this new toy! :lol:

This allowed me to install Oscillation ROM R7 with a2sd which for the moment is working extremley well!

Link to comment
Share on other sites
Guest ultravox

Guest ultravox

Posted
Posted
:D :D :)

Thanks a lot bUg. THis was just what I need to get Amonra working on my TMN A1 (thought it only works when I boot the recover.img from fastboot, when I reboot into recovery it hangs on RBM screen). I think there is going to be a lot of happy folk in Portugal in the next couple of days with this new toy! :lol:

This allowed me to install Oscillation ROM R7 with a2sd which for the moment is working extremley well!

Could you please clarify this Amonra and update process? I think the TMN A1 thread would be a great place to do it and a lot of us would thank you for that.

Link to comment
Share on other sites
  • 7 months later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept