hecatae

retrieving .mbn files

23 posts in this topic

000.jpg

that looks like the .mbn files from the TPT image

still reading on how to extract

0

Share this post


Link to post
Share on other sites

You want the last 4 too. A few of those files aren't in the original tpt update, but grab them anyway if you can.

0

Share this post


Link to post
Share on other sites
You want the last 4 too. A few of those files aren't in the original tpt update, but grab them anyway if you can.

will do, still reading through the 198 page user guide

0

Share this post


Link to post
Share on other sites
will do, still reading through the 198 page user guide

Great. Don't forget to post an easy to follow guide with links to the software. This could possibly be used to fix the problem with the new official 2.2 phones.

0

Share this post


Link to post
Share on other sites

going to use the below to see if I can retrieve what's needed

1. MBN-Resourcer = Qualcomm firmware resource viewer

2. QPST - Qualcomm Product Support Tools

3. QXDM - Qualcomm eXtensible Diagnostic Monitor

4. QC BS analizer - similar to mbn-resourcer, but other maintainers

5. BREW Resource editor - it's more for high level programming ...

FULL_SDRAM dump file with QPST Memory Debug contains AMSS

lets see if I can get that

Edited by hecatae
0

Share this post


Link to post
Share on other sites

Isn't the multi-image downloader a way to flash multiple devices at the same time?

Just asking, I'm not sure!

Also hecatae, can you please send me some DL links to your tools? Can't find most of them :S

0

Share this post


Link to post
Share on other sites
Isn't the multi-image downloader a way to flash multiple devices at the same time?

Just asking, I'm not sure!

Also hecatae, can you please send me some DL links to your tools? Can't find most of them :S

sent you a message with everything I'm using, already got a successful memory dump

Edited by hecatae
0

Share this post


Link to post
Share on other sites
... already got a successful memory dump

:D

Is it straightforward enough for an 'ordinary user' to dump the Gen2 files safely? (And it would probably be a user without English as their first language)

0

Share this post


Link to post
Share on other sites
:D

Is it straightforward enough for an 'ordinary user' to dump the Gen2 files safely? (And it would probably be a user without English as their first language)

you'd have to boot the device in FTM mode and use QPST 2.7 build 348 to do a full Memory Debug dump, simply a case of choose the same com port as the DFU port is registered to

0

Share this post


Link to post
Share on other sites
you'd have to boot the device in FTM mode and use QPST 2.7 build 348 to do a full Memory Debug dump, simply a case of choose the same com port as the DFU port is registered to

So are you saying you have managed to extract all the internal memory from a blade? does that mean it will be possible to flash gen1/gen2 files between phones?

Also how do you boot into FTM Mode? is the the one where you hold down both volume buttons or a different one?

0

Share this post


Link to post
Share on other sites
So are you saying you have managed to extract all the internal memory from a blade? does that mean it will be possible to flash gen1/gen2 files between phones?

Also how do you boot into FTM Mode? is the the one where you hold down both volume buttons or a different one?

As you have a Gen2 device, it is not yet been rooted, flashed with CWM, etc, right?

If so, FTM mode is achieved as recovery mode: hold down the Volume Down button while switching on the phone.

The DFU mode should equal the FTM mode (same debug interface is loaded) what you were talking about (hold down both volume buttons), but I'm not sure it will work!

hecatae, please share the method, so some more experienced Gen2 users can dump their phone -> we can make a TPT of it :D

0

Share this post


Link to post
Share on other sites
As you have a Gen2 device, it is not yet been rooted, flashed with CWM, etc, right?

If so, FTM mode is achieved as recovery mode: hold down the Volume Down button while switching on the phone.

The DFU mode should equal the FTM mode (same debug interface is loaded) what you were talking about (hold down both volume buttons), but I'm not sure it will work!

hecatae, please share the method, so some more experienced Gen2 users can dump their phone -> we can make a TPT of it :D

Ah ok, that clears things up. I have a gen1 blade - I am just curious. The reason I asked is because I Found the admin password for this program in post 45 of this thread, which had a NV backup function that resembled what is at the top of this thread. I tried to use it on my gen1 using both volume buttons boot, and it recognised my phone, but it didn't do anything because it said my phone was in "download mode"

0

Share this post


Link to post
Share on other sites

Unfortunately , you can't get a raw nand image dump by just using QPST. You can however get a full RAM dump by putting the phone in download mode (by switching it on while holding the Vol+ and Vol- keys) and using revskills. You can then "cut" the obtained image and extract oemsbl & C.

P.S. Diagnostic (FTM) Mode and Download Mode are not the same. While in Download Mode, you can send the phone a bootloader and have it run on the ARM9 (baseband) processor. With a properly written/patched bootloader you have full access to the phone hardware, including the nand. Phone flasher sends its own bootloader (armprgZTE.bin) to the phone and then use it to flash the images... we could patch it to allow nand reading.

P.P.S. NV items contain values that must be stored in a Non-Volatile way (e.g. IMEI, lock status, ...).

Edited by Slash.it
0

Share this post


Link to post
Share on other sites
Unfortunately , you can't get a raw nand image dump by just using QPST. You can however get a full RAM dump by putting the phone in download mode (by switching it on while holding the Vol+ and Vol- keys) and using revskills. You can then "cut" the obtained image and extract oemsbl & C.

P.S. Diagnostic (FTM) Mode and Download Mode are not the same. While in Download Mode, you can send the phone a bootloader and have it run on the ARM9 (baseband) processor. With a properly written/patched bootloader you have full access to the phone hardware, including the nand. Phone flasher sends its own bootloader (armprgZTE.bin) to the phone and then use it to flash the images... we could patch it to allow nand reading.

P.P.S. NV items contain values that must be stored in a Non-Volatile way (e.g. IMEI, lock status, ...).

so what on earth did QPST Memory Debug dump then?

I know Diagnostic Mode and Download Mode are not the same, Diagnostic Mode has a big FTM Icon in the middle of the screen, Download Mode shows a black screen.

Edited by hecatae
0

Share this post


Link to post
Share on other sites
so what on earth did QPST Memory Debug dump then?

You can dump the RAM, but not the nand. In fact, I bet that's what "Memory" in "QPST Memory Debug" means. :D

0

Share this post


Link to post
Share on other sites
You can dump the RAM, but not the nand. In fact, I bet that's what "Memory" in "QPST Memory Debug" means. :D

ok, any help you can give with PSAS from revskills would be appreciated

0

Share this post


Link to post
Share on other sites

so ... any idea how to dump the hidden area of the nand? any working method at all?

0

Share this post


Link to post
Share on other sites
http://forum.revskills.de/viewtopic.php?f=13&t=36

reversing QC mobiles for beginners

That guide tells you what to do with the files once you have them. Unless you mean the easiest way is creating a custom bootloader from decompiled source & hoping it works on a new phone (we wouldn't be able to test it on a new phone without risk of bricking it)?

We need to be able to convince somebody with a new 2.2 phone to get them from a phone, unless we can get an official zte 2.2 update. starting to sound like it might be easier to get a zte update than mess around getting it off a phone.

Edited by wbaw
0

Share this post


Link to post
Share on other sites
We need to be able to convince somebody with a new 2.2 phone to get them from a phone, unless we can get an official zte 2.2 update. starting to sound like it might be easier to get a zte update than mess around getting it off a phone.

I'm agreeing with that.

0

Share this post


Link to post
Share on other sites

Hmm yes you will need a modified downloader, that's with what I was struggling about flashing my Huawei E220 :D

0

Share this post


Link to post
Share on other sites

We could try to disassemble armprgZTE.bin and look for a way to enable nand reading. That bootloader can flash the phone, so it already has nand-related functions built-in. We could ask viperbjk (revskill's developer) how the bootloader is supposed to be patched to allow nand reading.

I think we should insist on looking for a solution. A method for dumping the whole nand would be very useful to users of similar-but-incompatible blade models: they could make their own TPT images, even if a leaked one doesn't exist for a specific device.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.