Related
I happened upon this link http://developer.nvidia.com/tegra/downloads where you can find a stock tegra2 froyo image. It includes system.img and recovery.img.
Given this image, would it stand to reason that we could easily create a stock 2.2 ROM with a proper extract-files.sh? Seems like it'd be worth a shot.
That's the system.img where the original performance pack was created from.
This is the one that I bookmarked (no files there, yet): http://developer.nvidia.com/tegra/devkit-ventana
roebeet said:
That's the system.img where the original performance pack was created from.
This is the one that I bookmarked (no files there, yet): http://developer.nvidia.com/tegra/devkit-ventana
Click to expand...
Click to collapse
Roebeet, have you checked the page recently? There are files for both Windows and Linux. I'm not entirely sure what files you are looking for but thought I would give you a head's up that there are files linked to on that page now.
sumdumdude said:
Roebeet, have you checked the page recently? There are files for both Windows and Linux. I'm not entirely sure what files you are looking for but thought I would give you a head's up that there are files linked to on that page now.
Click to expand...
Click to collapse
You missed the post in Android Development. We found those files already. Thank you for looking though!
Yeah, I'm looking now - they made some changes even on the old dev kit. New stuff to play with!
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
I've downloaded an unbranded stock UK ROM (i think) for a Nokia 1020 64Gb to replace the O2 rubbish.
It is file
RM875_3051.40000.1345.1003_RETAIL_eu_euro1_212_03_336753_prd_signed.ffu
It was automatically downloaded to C:\ProgramData\Nokia\Packages\Products\rm-875
I try to 'make' Product Support Tools for Store 5.0 find the download. It will not.
Regardless of which folder I place the download in (and alter the supposed location path) all the Recovery Tool sees is the software
already installed on the Nokia 1020 - filename. It defaults to this file.
RM875_059T1Z9_3051.40000.1345.1003_062.vpl
This is the nasty O2 branded crap already on the Nokia 1020 and all it wants to find.
Have I just downloaded another O2 branded rom ?
Dead end and out of ideas.
All answers on a postcard please to Muppet The Wonder Dog.
Do I have to remove something that makes it default to the installed
version of software ?
Thanks in anticipation.
To delete.
anaheiim said:
Use 059T1V6 RM-875 VAR EURO GB CV BLACK and http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
Thank you. Will Do.
Jailbreaking iPhones was never this challenging.
anaheiim said:
Use 059T1V6 RM-875 VAR EURO GB CV BLACK and http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
The download was successful. The 059T1V6 files are downloaded to C:\ProgramData\Nokia\Packages\Products\rm-875. I used NaviFirm+ to download.
Alas, Product Support Tool for Store 5.0 does not want to locate the files. Why ? I have moved the files (and changed the path) to different locations in an attempt to persuade the software to locate the 059T1V6 files. But NO ...it will not.
Every time I try to change the address path to where I've moved the files is adds "\Products" to the path address. Not helpful.
When I create the path it thinks it wants .C:\ProgramData\Nokia\Packages\Products\rm-875\Products...and place the files in this folder..it still refuses to locate the files.
Going round in ever decreasing circles.
Thanks in advance Anaheim.
To delete.
anaheiim said:
No, use Data Package Manager for DL your FW
Here http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
The reason I paid & used NaviFirm+ to DL the FW is the DL worked.
I am unable to get Nokia Data Manager to accept any text entry in any of its fields to start a DL.
I am unable to get Nokia Product Support Tool V5 to see/locate the (apparently) identical FW downloaded via NaviFirm+ to start the 'Recovery' process.
I'm on fully patched W7 (x64)
It's a mystery.
To delete.
Here are the dropbox links screenshots of
https://www.dropbox.com/s/h1f1emb2jyuvexl/Screenshot 2014-06-04 12.24.10.png
and to Nokia Care Suite
https://www.dropbox.com/s/1pz22k5a2kvox9d/Screenshot 2014-06-04 12.27.26.png
Thanks
To delete.
anaheiim said:
If you are in offline mode in the Data Package Manager (and according to the screenshot, you are) you can not DL the ROM.
Similarly for Product Support Tool, why did you connect directly your Lumia?
Follow the tutorial that I provided and you will get there.If you are unable to properly follow the steps (in most it's extremely detailed and with the screenshots), sorry but I can not help you.
Click to expand...
Click to collapse
As I said the problem is not in the downloading of the ROM.
It was very easy in NaviFirm+. I recommend the software for its simplicity and ease of use.
I have identical ROMs downloaded via Nokia Data Package & NaviFirm+.
The problem appears that the data path in Product Support Tool for Store V5.0 appends as a suffix '\Products' to the data download path. This is not the default path given from the Data Package Manager. The path is not user editable. If I create the additional folder and move the files to the folder it says it is looking for.... the Nokia package still fails to locate the FW it is trying to Recover. There are no screenshots to illustrate any error message. There is no error message.
I appreciate that it is very difficult to convey the exact steps in unambiguous English. I have been very fortunate in both multiple JailBreaks and the application of Cyanogen Mod to a collection of Samsungs..
To delete.
all paths added have the sub-folder ' \Products
' appended to the text string. I am unable to edit the path name. Just add another.
See
https://www.dropbox.com/s/vyuowb43rafn80a/Screenshot 2014-06-09 11.21.53.png
When I go to try and set the path via Data Package Manger it does not see them;which ever folder they are placed in.
https://www.dropbox.com/s/mxhjlegdqviqqis/Screenshot 2014-06-09 11.25.31.png
Sorry for the thread necro. I have an O2 1020 64GB as well and want to rebrand it, but for love nor money I can't find from where to download the firmware, all sources are down. Any input is appreciated!
triturbo said:
Sorry for the thread necro. I have an O2 1020 64GB as well and want to rebrand it, but for love nor money I can't find from where to download the firmware, all sources are down. Any input is appreciated!
Click to expand...
Click to collapse
One possibility would be to use thor2 to change the product code on the device, then let the WDRT do its job.
I've been searching for months and I haven't found a way to debrand the Lumia 1020 from ATT.
The company locks features (like internet sharing, for example) , event if you unlock the phone...
Is it the lack of interest from hackers and developers, or is ATT really that strong at keeping us from debranding it?
spaceOpia1 said:
I've been searching for months and I haven't found a way to debrand the Lumia 1020 from ATT.
The company locks features (like internet sharing, for example) , event if you unlock the phone...
Is it the lack of interest from hackers and developers, or is ATT really that strong at keeping us from debranding it?
Click to expand...
Click to collapse
See from page #54 with the assembly (DLL) modified if you are unable to flash, maybe this can help you (RM-877 > RM-877 or RM-875).
anaheiim said:
See from page #54 with the assembly (DLL) modified if you are unable to flash, maybe this can help you (RM-877 > RM-877 or RM-875).
Click to expand...
Click to collapse
Thanks for the info Anaheim.
I downloaded your dll files, but from the edits on your post, you mention that the first modified dll (Nokia.CareSuite.PlugIns.MurzimRecovery.dll) caused problems, but did you revert back the first modified dll before replaceing the second (Nokia.Packages.VariantPackage.DataPackage20.dll) ?
also, your thread (on page 54) mentions modifying the vpl file. What is required to modify exactly?
I read around the thread and other forums as well and there are many ways poeple do it. Some even change two other files (the dcp and the bin file), while some only people change file names, and some people chage the content of the files
any help will be greatly appreciated
thanks
spaceOpia1 said:
Thanks for the info Anaheim.
I downloaded your dll files, but from the edits on your post, you mention that the first modified dll (Nokia.CareSuite.PlugIns.MurzimRecovery.dll) caused problems, but did you revert back the first modified dll before replaceing the second (Nokia.Packages.VariantPackage.DataPackage20.dll) ?
also, your thread (on page 54) mentions modifying the vpl file. What is required to modify exactly?
I read around the thread and other forums as well and there are many ways poeple do it. Some even change two other files (the dcp and the bin file), while some only people change file names, and some people chage the content of the files
any help will be greatly appreciated
thanks
Click to expand...
Click to collapse
I tried with both DLLs at the same time, it did not work.
The flash procedure is performed from the VPL file (VPL file contains all the file names, for then flashed this files). It is a sort of "guide". VPL file is "signed by" the signature.bin file that contains his signature. It is useful to modified the VPL if you change / replace / etc some files.
I have not tried changing some file, because I have not had time.
anaheiim said:
I tried with both DLLs at the same time, it did not work.
The flash procedure is performed from the VPL file (VPL file contains all the file names, for then flashed this files). It is a sort of "guide". VPL file is "signed by" the signature.bin file that contains his signature. It is useful to modified the VPL if you change / replace / etc some files.
I have not tried changing some file, because I have not had time.
Click to expand...
Click to collapse
Ok thx,
so I keep the original Nokia.CareSuite.PlugIns.MurzimRecovery.dll and only change Nokia.Packages.VariantPackage.DataPackage20.dll with the one you supplied.
I tried flashing the ROM with a country variant RM-875 from GB (with only Nokia.Packages.VariantPackage.DataPackage20.dll modified) but I still got the ffu error.
I will continue to work on it and keep you updated
thanks again
spaceOpia1 said:
Ok thx,
so I keep the original Nokia.CareSuite.PlugIns.MurzimRecovery.dll and only change Nokia.Packages.VariantPackage.DataPackage20.dll with the one you supplied.
I tried flashing the ROM with a country variant RM-875 from GB (with only Nokia.Packages.VariantPackage.DataPackage20.dll modified) but I still got the ffu error.
I will continue to work on it and keep you updated
thanks again
Click to expand...
Click to collapse
Any updates on this? Where you able to successfully flash the Lumia 1020 att model?
blackbo said:
Any updates on this? Where you able to successfully flash the Lumia 1020 att model?
Click to expand...
Click to collapse
No, no news.
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
or this one seems to be even more up to date (credits to a1291762 for finding it)
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
Apparently nobody in this forum has ever posted a link to this blog.
This blog seems to be made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy these sites are but they actually just link to the official Xiaomi OTA download site(https://bigota.d.miui.com), thus the downloaded zips are the official one.
p-walker said:
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
Apparently nobody in this forum has ever posted a link to this blog.
Apparently this blog is made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy the site is though. Seems to exist for quite a while though and it's been mentioned in other threads on xda.
Click to expand...
Click to collapse
It could be useful for some OTA files specially for the latest v10.0.14.0 and v10.0.15.0 (wrongly placed in fastboot section) but about the fastboot roms the thread opened here is more updated and complete https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 it contains the latest fastboot rom for our device, v10.0.13.0.
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
a1291762 said:
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
Click to expand...
Click to collapse
Thx that site seems to be even more up to date, I will include it in the top post if you don't mind. However it is very "minimalistic" I mean there is no information at all about this site available and at least on xiaomifirware you get some extra information blog posts on top and they actually have a disclaimer that they are not affiliated with Xiaomi.
However it seems both sites are actually linking to the official https://bigota.d.miui.com site when downloading the files, thus they should be kinda trustworthy as long as they actually linkt to the official xiami site.
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
romulocarlos said:
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
Click to expand...
Click to collapse
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
a1291762 said:
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
Click to expand...
Click to collapse
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
romulocarlos said:
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
Click to expand...
Click to collapse
Files with extension tgz are full global rom to be used with MiFlash tool, fastboot or EDL and first you have to unpack it.
Files with extension zip are OTA updates to be flashed through system when it does use the scripts of the stock recovery (when you receive that you have an update) or totally through a custom recovery like TWRP and you don´t need to unpack it (inside within other files you will see payload.bin file)
All the rest that can be founded out there is unnoficial, adapted roms at the like of the user.
Hi guys. Do you know which firmware version is the last android 9 version?