I am trying to convert a MZ600 to MZ601.
I assume there are no actual hardware differences, but only software.. and I have not found any sources/info proving otherwise...
I have allready fastboot-flashed system/user/boot/recovery of MZ601 Europe stock images, to my VZN MZ600 Xoom and everything works fine except the mobile-network ofcourse...
(btw SIM is working!)
So how can I flash the baseband to the European one ?
Is the radio.img all I need ?
In that case, can somebody send me one?
I have tryied a full EU firmware flash with RSDlite, but I get an error "Unable to retrieve initialization values from INI file." so I cant start flashing...
Any ideas?
Thanks
I saw in other thread you have gsm sbf, perhaps using sbf recalc or sbf depacker you can extract its radio image..
please check this link
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
http://and-developers.com/sbf
I thought the recovery / img files were on motorola's website now?
Thanks lesjaw , I will try..
(I did a search for sbf extractors but did not find those ones! )
Lothaen , motorola gives away the common partitions, (userdata/system/boot/recovery) and not the hardcore ones such as the radio one!
lesjaw, I tried both software. They both allow me to split files, from the SBF.
That results into 13 SMG files, which I assume are partitions (and something else?)
What format are these ? can I open them ? How do I identify the radio.img
is the IMG format same as SMG ?
MotoAndroidDepackerMono, has an option to extra radio.img, but thats from an update.zip, which I what I am trying to create
i see, honestly I never use those app, in sunday i'll give a shot..
btw, you can join #milestone-modding in freenode (irc), many of those members channel have good experience regarding sbf file..
good luck brother..
Any idea anyone, how to identify the radio image, from a SBF extract to SMG files ?
Once identified, can I use an SMG file as a "radio.img" ?
HMJ37 sbf
Motorola did just release a few days ago a new sbf for the MZ600 that is the full HMJ37 version. Here is the full file name out of the latest spreadsheet for anyone with RSD access:
VZW_MZ600_Signed_HMJ37_Signed_MDM6600BP_C_02.0F.00R_SW.combo.sbf
I think he needs an image from MZ601, not MZ600!
its been quite some time, and have not yet found an answer to this problem!!..
attached is the export from the SBF file of MZ601
I asume one of these files, is the radio.img , correct ? which one is it?
Can I do a fastboot flash radio radio.img ,using one of these files!?
Is it safe to try with the user partition to confirm my theory ? (I can identify it, from the byte size)
I tried to open the images with unyaffs-x86-win and cygwin but I always get an error message "broken image file" even on motorola's official images, hence I've got something else wrong (?)
So many questions left unanswered for so long! and I though XOOM was for hardcore android users!
nikil511 said:
its been quite some time, and have not yet found an answer to this problem!!..
attached is the export from the SBF file of MZ601
I asume one of these files, is the radio.img , correct ? which one is it?
Can I do a fastboot flash radio radio.img ,using one of these files!?
Is it safe to try with the user partition to confirm my theory ? (I can identify it, from the byte size)
I tried to open the images with unyaffs-x86-win and cygwin but I always get an error message "broken image file" even on motorola's official images, hence I've got something else wrong (?)
So many questions left unanswered for so long! and I though XOOM was for hardcore android users!
Click to expand...
Click to collapse
Are you sure that's from a MZ601 and not a Wi-Fi only MZ604 (see the "HUBBLE" and "WIFI" strings)?
You cannot fastboot flash the radio partition (which probably is called something like bpsw given this is a Motorola device). Given that these are proprietary firmware blobs, do not expect to get far assuming that these are yaffs/ext/whatever filesystem images.
thisi is where i found the SBF
http://www.mod2xtreme.com/showthread.php?t=10571
so I assume it has the radio partition.
So if I can not extract it from the SBF, how are all these baseband update zip been constructed on all other tablets/phones ? why are there none for XOOM eventhout various baseband versions exist ?
or this h.6.2 means that should be for mz604(wifi only) so it should contain no baseband image. ?
convert mz600 to mz601
hello all,
nikil511 , did you found any solution? i'd really like to convert my mz600 to mz601 !
concerning the sbf, because of the name we know it's from the wifi xoom.
but as info, the radio is cg5
regards
http://sbf.droid-developers.org/everest/list.php here new full image
in amms_sec.mbn
we can find string for new firmware VTHUBBLE_N_01.100.07P
or in rdl1.smg ..
how to use it? or convert to .img in .zip file ?
i do it
http://forum.xda-developers.com/showthread.php?t=1845212
Related
With Epsylon3 brilliant work, a new idea of flashing custom firmwares came to surface, allowing custom /system partition to be flashed directly from RSD Lite! This way you don't need to flash fixed SBFs and waste time with rooting and recovery install in case of system screw-up.
What you need:
1) MotoAndroidDepacker. With it, unpack sbf of the firmware you use as base.
2) Leave CG35(boot) and CG61(devtree) partition files, delete other smgs. Other files are not that important. You can delete all partition files if you're making backup for yourself...
3) Replace CG39(system) with your system dump:
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
copy CG39.smg from sd card to your firmware folder.
4) Compile sbf with MotoAndroidDepacker.
5) Flash your sbf in case of failure.
MAJOR CAVEAT: This sbf will work ONLY on devices with have same full SBF version applied last as your device. I.e. if you have flashed 3.4.2-107 and then upgraded it with nandroid to 3.4.2-177, the sbf you created from your system dump will work only for devices which flashed still 3.4.2-107 sbf last. To install such (custom) sbf, one would need to flash full 3.4.2-107 sbf first.
Technical: this is possible because of bug/feature in flashing process: system signature partiton is not checked if phone signature is already present. Phone signature is generated when flashing full genuine sbf and is verified aganist copy in sp partition and obviously differs for each firmware. It is stored at the end of the system partition.
Great news.
Some question:
If I install a full sbf. IE: 3.4.2-117 and then apply a custom ROM over it (CM).
So can I make a backup of my system and flash it again in case of any brick?
You can make a backup for yourself and flash it again all you want until you flash another full motorola sbf. Don't forget to make data backups as well, this method can't replace nandroid / titanium!
Interesting...
So I can flash my base sbf, integrate call recording, 720p playback, wvga recording, root, swype on my language and other mods and create a new sbf only to apply these mods.
It will be usefull....
Oh great all of us asked this question when this section began in xda. So essentially we can make an sbf out of our phones and keep it and not worry about any nandroid backups.
This is a great discovery, thanks a ton.
Cheers
So would it be possible creating custom bootmenus as these are updated by sbf's too?
If your current system contain boot menu. The custom sbf also, it is identical with the current system.
i think you can create a Full SBF with all original partitions and your "signed" CG39
I think it is not a bug... the thing is : i'm not sure sbf can work on other devices ... but anyway... it can be really usefull to recover device or to create a full backup with the good kernel made for the /system and /devtree
mbr and ebr are needed too, if the partition table has changes, you will have problems..
So the question is whether the signature is related to the specific part of every device, or it is universal as official sbf. Need to be verified .
Does this means that someone could create a sbf wich flashs dierctly CM7 or MiUi?
IE-coRe said:
Does this means that someone could create a sbf wich flashs dierctly CM7 or MiUi?
Click to expand...
Click to collapse
It's possible too.
Where i can finde the MotoAndroidDepacker?
Great news! But why are Android systems so complicated when it comes to flashing and banking up? I mean, with computers it's easy. You make an image of the system partition and you're done. Restoring is as simple as writing the backup back to the partition. So, why is it so hard to just make an entire nand backup that we can simply write back to go to a working state after failure?
Sent from my MB525 using Tapatalk
I made a custom sbf with nightly build in it . Then wipe and flash it, stuck at M logo. Bootmenu works, but it seems that it can't mount some partition , it's the same symptom when wipe in stock recovery in cm7.
Does it really need to flash a full sbf before the custom sbf ?
So if i wanted to do this i split my sbf, delete everything only leaving,
CG35.SMG
CG61.SMG
firmware.hmg
Then system dump and add that CG39.smg in and build and flash?
Have i missed anything?
Well you forgot RAMDLD... One CG39 is enough if you'll flash this SBF over ver 4 froyo (not Chinese or Korean) but i recommended CG35 and CG61 to make such sbf enough to flash over system downgraded with fixed sbf + nandroid.
Is it possible to keep all files and just replace CG39? Or are files removed for a reason? Thanks for replying.
You can keep all files, theoretically.
Well i made an sbf version of miui and it works
Wonder if it works on other peoples Defy?
Tested by formatting system and then applying sbf. Booted back into MIUI like a dream
EDIT:
Shame the SBF comes out at 300+mb May take a while to upload these things lol.
If I mount the CG39 as a loopback device in a linux box,
Can I just replace the contents and it will retain the signature?
Or the signature is based in a checksum?
I have a question, that probably isn't feasible, but I will ask it anyway. I was noticing that the size of the actual cdt.bin codegroup is a lot larger than the file flashed by the SBF. This makes me think that when the normal CG31 file is flashed to the system, that rather than replacing the existing file, it updates it, and the update must be in line with what it is expecting.
I was looking at sbf_flash, and the capability it is supposed to have, and it got me to thinking. It says that it is able to flash a specified file, that will overwrite what is there whether it is the right thing or not. (or something to that effect) what it says is, " in other words you can write arbitrary data to any location on the flash -- be careful."
This makes me wonder if it would be feasible to extract the complete cdt.bin file from a phone that has not taken the .629 update, and completely overwrite the cdt.bin codegroup, using sbf_flash.
Someone more familiar with all of this has probably already thought of this, and found it won't work, but just in case I figured I would throw the idea out there.
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045
Sammobile
P5200XXUBNG2_P5200AMNBNG1_AMN
http://samsung-updates.com/details/32840/Galaxy_Tab_3_10.1_3GplusWiFi/GT-P5200/AMN/P5200XXUBNG2.html
Has anyone been able to successfully extract the tar.md5 from the zip? I've tried numerous times, with different operating systems, but having the same problem every time (though slightly different output, tried on Windows, Mac OS X, and Linux)
Here's the output from the "unzip" command in the OS X terminal
Code:
$ unzip P5200.zip
Archive: P5200.zip
file #1: bad zipfile offset (local header sig): 0
inflating: SS_DL.dll
Any thoughts would be appreciated, I'm trying to make flashable zips from this.
Anything i've found pertaining to that error points to multi-part zip files, which obviously this is not, leading me to believe a mistake was made when zipping it.
Restl3ss said:
Has anyone been able to successfully extract the tar.md5 from the zip? I've tried numerous times, with different operating systems, but having the same problem every time (though slightly different output, tried on Windows, Mac OS X, and Linux)
Here's the output from the "unzip" command in the OS X terminal
Code:
$ unzip P5200.zip
Archive: P5200.zip
file #1: bad zipfile offset (local header sig): 0
inflating: SS_DL.dll
Any thoughts would be appreciated, I'm trying to make flashable zips from this.
Anything i've found pertaining to that error points to multi-part zip files, which obviously this is not, leading me to believe a mistake was made when zipping it.
Click to expand...
Click to collapse
Have you tried an other source? http://www.sammobile.com/firmwares/?page=1&model=GT-P5200&pcode=0#firmware
Max4000 said:
Have you tried an other source? http://www.sammobile.com/firmwares/?page=1&model=GT-P5200&pcode=0#firmware
Click to expand...
Click to collapse
As of now there's only one 4.4 source, Spain (orange)
And it doesn't seem to be working. Hmm
Perhaps someone with a P5200 could Odin to stock 4.2 Spain (orange) and try to capture the OTA
Restl3ss said:
As of now there's only one 4.4 source, Spain (orange)
And it doesn't seem to be working. Hmm
Perhaps someone with a P5200 could Odin to stock 4.2 Spain (orange) and try to capture the OTA
Click to expand...
Click to collapse
Hey , isn't someone can change CSC code to spain(orange) ????? Google it . It's given on droidviews . 'How to change CSC code on Galaxy Devices'
Luxor said:
Sammobile
P5200XXUBNG2_P5200AMNBNG1_AMN
http://samsung-updates.com/details/32840/Galaxy_Tab_3_10.1_3GplusWiFi/GT-P5200/AMN/P5200XXUBNG2.html
Click to expand...
Click to collapse
Download from samsung updates (rapidgator), it's no corrupted, i'm writing with new Kitkat for p5200
Do no install previous orange rom, no OTA update.
If you need a faster mirror https://mega.co.nz/#!zZRR2Zbb!RgYWSU_WTvsJDT_Pmiv5KaJz6BGiXaM28_WaRQ3K2hU
Hi all, I have a GT-P5200 from Brazil, with the PDA number P5200UBUAMF6 that is running 4.2.2 actually. Is it safe to update to a 4.4.2 ROM from another country (i.e. problems with 3G connectivity)?
Anyone can help me find the KDz for the LG K9, Canadian variant lmx210wm? Bricked it trying to crossbreed firmwares, and now need the original lmx210wm firmware so I can build a working qfil folder.. Any help would be greatly appreciated
****After an extensive search, i came up empty handed in finding firmware for lm-x210wm. the site exists on the LG website, but the firmware isn't downloadable. i would contact LG ... there were some other models listed, but i'm not sure if they're compatible with your system.
no luck in finding anything on 3rd party sites either, sorry****
I used the lg firmware exttaction.tool. lg-firmware-extract-tool ... Not able to post the link bcz of site restrictions.
If available, it should offer the kdz file, a way to extract the dz file and finally the bin files. Merging the system files yields a system.img file.
I didn't have luck w magisk and this file and don't know a way to convert just the boot.bin file to img.
**EDIT: renaming the boot.bin file to boot.img & then using the platform-tools and using the command
fastboot flash:raw boot boot.img (Finanly got my system rooted. supposedly the same method works w/ twrp, but that didn't throw an error and frankly i'm sick of working on this phone ... day 3.) ****
Twrp isn't compatible w my sys and no one click root methods work.
As your model is close to mine, lmx210cm ... I imagine you're going to have the same luck. No custom recovery and just a root.
****EDIT: Good luck and send me a pm if ya can figure out a way to convert bin to img. Hopefully, you will have better luck w the system.img. RESOLVED****
If there are multiple versions, start off w the ver closest to your security update. My info was in about/software.
jonathan dockery said:
****After an extensive search, i came up empty handed in finding firmware for lm-x210wm. the site exists on the LG website, but the firmware isn't downloadable. i would contact LG ... there were some other models listed, but i'm not sure if they're compatible with your system.
no luck in finding anything on 3rd party sites either, sorry****
I used the lg firmware exttaction.tool. lg-firmware-extract-tool ... Not able to post the link bcz of site restrictions.
If available, it should offer the kdz file, a way to extract the dz file and finally the bin files. Merging the system files yields a system.img file.
I didn't have luck w magisk and this file and don't know a way to convert just the boot.bin file to img.
**EDIT: renaming the boot.bin file to boot.img & then using the platform-tools and using the command
fastboot flash:raw boot boot.img (Finanly got my system rooted. supposedly the same method works w/ twrp, but that didn't throw an error and frankly i'm sick of working on this phone ... day 3.) ****
Twrp isn't compatible w my sys and no one click root methods work.
As your model is close to mine, lmx210cm ... I imagine you're going to have the same luck. No custom recovery and just a root.
****EDIT: Good luck and send me a pm if ya can figure out a way to convert bin to img. Hopefully, you will have better luck w the system.img. RESOLVED****
If there are multiple versions, start off w the ver closest to your security update. My info was in about/software.
Click to expand...
Click to collapse
Thank you very much sir. Appreciate all your effort. I'm close now I just have to finish editing the raw program XML file and start trying all these fire hose versions. I'm still not even sure if it's an 8909 or 8917. (