Related
Hi all,
let me start telling that reading through this frum gives me the feeling that this is a very nice place for information around htc-devices and I thank both creators and users of this site for such a good information-base.
Reading here convinces me that I am able to fulfill my wish to change the language of my VPA-IV (HTC Universal).
I am a Dutch person working in Russia. As I was living in Germany I optained the device there, hence the German language.
For me personally all computer stuff should be English, so I'd also like this device to be so. The fact that the keyboard is German does not disturb me too much.
As a Vodafone user, who has other provider cards as well, I immediately bought the unlock code, so the device is working with other GSM cards as well.
When I asked Vodafone (before I bought the device) if I could switch to English I was told that I should buy myself another Windows Software and they were not able to provide me with it. They were not able to provide any help, nor software for this purpose though.
When reading around the site here (as well as the ftp) I understood that Windows is not provided now. So my first question would be :
-Am I really set to go if I have downloaded the following files :
Jasjar_WWW_11353_137_10301.zip
MaUpgradeUt_noID.zip
Universal_Radinly_UPgrade_1.04.02.zip
Or do I need something more ?
Further I read about extracting the .exe file (f.e. Jasjar_WWW_11353_137_10301.exe) and put some files from there at certain places. I have WinRar but this program does not recognize the .exe file. Can I really extract files from this .exe ? How do I do this.
A lot of talking is here about a bootloader. If the device is in this stage, can I still access it ? (f.e. like seeing a harddrive in my PC's Windows Explorer or something the like)
As I will be stressed like hell (who does not, when he does this first time) when I see the bootloader screen, is there something I SHOULD or should NOT do to make sure all will be OK ?
Last but certainly not least I feel very eager to backup before I do this. Is there a posibility to backup my ROM in some way, save the files on some place for eventual return to the ROM and ExtRom I have now ?
I tried the Program TotalCommander. If I enter the Extended_Rom in the "directory" field of this program I see all files included in the Extended_Rom, same if I enter simply "Rom". Is a backup simply copying these files to my PC or is there more to be done ?
thanks for answering in advance,
Ruud
Hi,
I'm searching a german ROM...
if you have a little of your time to spend on it, i would be very thankful.
but first:
- about extracting the .exe files: Run WinRAR -> Menue: Open file... -> change 'All archives' to 'All files'
- about ROMs: Jasjar_WWW_11353_137_10301.zip is the only rom I would update, not the Radio.
- about bootloader: In this state you can't access your device (only updating the ROM)
- about backup: It is not easy. (How to d2s (dump) the ROM ) but I think Vodafone will shortly relase a update. So it will be possible to restor the device.
How to help me out:
- you will need a Storage Card.
- Download TestWM5.rar
1. Extract TestWM5.exe from TestWM5.rar and place it to you device.
2. At the device, use File Explorer to execute the TestWM5.exe
3. Click "button1" to start the dump process, the file will then be save to \Storage Card\Dump\
4. Copy the Dump folder out and then RAR or Zip it
This will include all files in your windows dictionary -> this is what i need
Where to place exactly ?
Hi bepe,
do not know if You are still available (or again). First your issue.
I logon to FTP from XDA-developers as to upload.
In the upload directory there is only a HTC-Wizard directory, not a wizard. Is this directory the one to place your file on ?
Is there a rule how to name the file ?
I will be dumping in a minute, can upload as soon as I have your answer.
Ruud
Hi bepe,
further to your issue.
1) I do understand that no private information is copied ? or should I do a hard reset before I dump for You ?
2) Whilst running your testwm5.exe from the root-directory of the storage-card I am being asked to agree your program access. This is normal, I allow. But why are there additional programs being opened I never heard about ? I denied them access and let the program run further !
After a lot of files running through the screen (very fast) it looks like the program stopped or finished. Now which file has been created for You ?
Explorer on the Universal does not show it, through my PC I looked as well, but do not see any big file, please explain.
Ruud
Hi Bepe,
one more reply to You :
Even if I allow the file mentioned to run (during the time your program is running), I am being asked again and again if I allow it again. The name is GAC_System.Data_v1_0_5000_0_cneutral_1.dll
Even if allow access all of the occasions I being asked, no file is being created on my storage-card, nothing to dump to You. Not even the dump directory is made.
What do I do wrong here ?
To my issue :
First I noticed that the radio update is available here only as 1.04.02
My system tells me I have 1.04.10 delivered from origin. If I do a ROM-upgrade, do I loose my "radio", or will it not be touched ?
Connected to this, can I dump my "radio"-files seperately ?
WinRAR. Issue solved !
Backup : I was at the buzzdev.net link before. But I actually do not even understand where I can get or see the task32 language he dumped on his screen. And I understand that I will not be able to restore it without help anyway. So this is not really the kind of backup I want.
The information about Vodafone, where does it come from ? when is something expected ?
Ruud
For security sake only.
I am getting nearer to make that final step ;-)
My Winrar was too old, I could unzip the .zip file to a .exex, but I could not unzip the .exe file further. Just downloaded the latest Winrar, now I can see all files included in the provided .exe file.
1) I understood that I should delete the original upgrade-file called ROMUpgradeUt.exe.
2) When I start the MaUpgradeUt_noID.exe in a seperate directory with the rest of the files from the .exe I get to see a different HTC device. When I continue, it will not recognize any of the versions from my Universal. I felt unconfortable to continue.
Can it be done without a problem ??
2a) I renamed the ms_.nbf AND radio_.nbf and restart the Utility, it still shows a photo of the wrong device, but it now does recognize the versions of Device CD image version : 1.13.56 Device Extended image version : 1.13.163 and Device Radio image version : 1.04.10
It confirms to change to CD image version 1.13.53 and leaves the extended image version : "empty" as well as the Radio image version : "empty"
Does this mean that by taking away the ms_.nbf and radio_.nbf files I can stop the device from upgrading the extended rom and the radio ?
Why I ask ? Because if I renamed ms_.nbf back and ONLY radio_.nbf is unavailable now, it shows to change the Extended Rom too, but the Radio image is still empty.
Finally if I rename ALL back, it shows to change all, but all version numbers are older once ;-(
Main question here is, can I leave radio_.nbf away, upgrade and hope for radio to be my version 1.04.10 ?
Ruud
Hi,
I'm back.
I'll PM you Upload information...
private information are not copied.
Only if you have saved private information in your /windows/ folder!
i have never being asked to agree for program access :?
...but I started it of the root-directory of my device.
what is the name of your 'Storage Card' folder?
I not realy have the info from Vodafone, but for all devices before there have been more than one update. But I can't tell when the first update is expected.
If you are trying to make a backup: you will need a terminal program
About dumping
So I have a complete "new" device now.
Did a hard-reset, after which I did not give any new information to the device.
I placed the .exe file You gave me in the \windows\startmenue before, after which it is asking tonloads of access requests.
Now I replaced it in the root-directorym Yes, no additional questions asked anymore, perfect, well NO. As there is no directory made on the storage card. I tried it once with the async active and once with the device seperate. No result.
Any ideas ?
what is the name of your 'Storage Card' folder in your root?
As the device is German, it is called "Speicherkarte"
and renaming is not possible (allowed)
OK this is the problem, I'm trying to get the Source code to change that.
found something: this tool will change the folder name from different languages to "Storage card" which is often needed for different tools
Understood.
About my question, as I am still nervously waiting (cannot start the upgrade before You got your data, can I ;-)
Did I understand correctly, that the file MaUpgradeUt_noID.exe is made for different devices from HTC and therefore I do not get a photo of the universal when I start the software ?
If I start the JASJAR_WWE_11353_137_10301.exe I DO get to see the Universal, but of course get the country error.
Did I also correctly understood I can take away the radio_.nbf from the directory and the update will handle both ROM and ExtROM but leave the Radio untouched ?
Will I be entering this "bootloader" status at all, as I do not need any further updates then ? Are there any resets after the upgrade which I SHOULD or SHOULD NOT make to get the device working again ?
Ruud
Hi bebe,
storage.cab works (be it only after a soft-reset)
The program testwm5.exe is much slower now, so the result is taking minutes now (if not tens of).
Looks like the perfect speed of the program while the storage card (at least for his eyes) was absent, was due to "saving into space"
Will upload asap.
Ruud
I'm loading JASJAR_WWE_11353_137_10301.exe its at 60%
MaUpgradeUt_noID.exe is a hacked version, of another device.
So the photo should not be important. (Please wait until i have downladed the file, I'm not realy sure jet...)
OK, I have to wait anyway, because TestWM5 is very slow now, I can see file after file and calmly read it. Before it was running before my eyes. I am afraid this is going to take ages.
We are on the same frequency that the dump I am making is from a device WITH Extended Rom installed. I was NOT soft-resetting during installation, so all Vodafone add-ons, are to be there now.
If You need the one without ExtRom as well, please tell me.
The upload works OK, I prepared a directory there, but uploading is to be done after longer waiting time.
Are You afraid the JASJAR file is not good ? I downloaded it because this one was proposed on this forum.
Ruud
Its not about the ROM its about the MaUpgradeUt_noID.exe I'm not sure if ths is the exe file to update a Universal.
I dont have a Universal only a Himalaya and my up UpgradeUt starts with HimUpgradeUt... .
Was this file mentioned in the readme of the JASJAR exe?
my download is very slow... 70%
I only downloaded MaUpgradeUt_noID.exe because it was proposed here (for the Universal).
I have no Readme.txt inside the exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
UI.dll
Well and of course the original upgrade file ROMUpgadeUt.exe, but I was suppose to delete it.
Only file which I can read is RUU.conf :
[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2
OK, TestWM5 is finally ready, will do compressing and uploading soon.
Ruud
My device rom seems to be aku1.
is it possible that i use other roms,which is aku3,replace dlls and other things from them and create my aku3 rom?
For example i saw contacts in newer roms is lot improved,is it possible that i use contact.exe(if it is the file name)from newer roms,replace it into my current rom file?or other .exe or .dll files?
Thats what ROM cooking is.
You take components that are generic and not device dependent from a more advanced ROM and place it in a ROM for your device that contains all the device specific stuff like drivers.
BUT: it is not as simple as it sounds.
First, you need a ROM image for your device (and if you are going to ask more serious questions on this matter you must specify exact model of your device) which you can get through a dump or from an official update.
Second you need tools, also specific for your device, that can take apart that image and put it back together.
And finally you need the new files which also have to be obtained from a ROM image for the more advanced device.
Thank you.
Well i guess i have the tools,becouse i could create the dump folder.and repack it again.
although the generated files were not same.(someone in chineese forum told me it is enough that value in bootloader be same,in my case values before 0x060000,i dont know if it is enough or not).
I havent yet tried to upgrade that rom,until i have enough knowledge.
But if we assume i have all tools,is there a guide or something that what files i can replace?
for example if i want to have new contact program,what files should i upgrade?
or is there a list of all dlls,exe files which are device independent?
so?anyone?
Some other questions:
using addfile/removefile,can i replace .dll files?
becouse i used the dump folder,shellres.96.dll,and deleting/adding,i get no icons in windows.
also using s000 file renaming it to shellres.96.dll i still get the same problem?
is there anyway to change this dll?
Today Samsung released a patch for their WP7 devices to resolve the update problems. WP7 version 7.0.7392.0 has been withdrawn for Samsung devices because of error 801812C1 during the update. After the release of this patch Microsoft has now resumed the release of the OS update for Samsung devices.
The update for Samsung Omnia7 can be downloaded from here.
I did a quick analysis of the file. It is an executable that should be run on a Windows PC. It installs the latest USB drivers for Samsung devices on the PC. Then a flash utility starts. A ROM-file is embedded as a resource in the flashtool. It's called OS.nb and it has a familiar Ra000FF header. So I tried to open it with the latest WP7 ROM Tools. It opens and it shows the "OS partition". But, unfortunately, as soon as I expand that node the WP7 ROM Tools crash. I hope that AnDim, the author of the WP7 ROM Tools, can work on that. The embedded ROM image is about 12 MB. It should contain only the files that are updated.
So this flash tool is able to replace some specific files on the device. That cool and we may be able to use that for other purposes.
I did a quick look at the ROM file in a hex-editor. The file itself does not seem to be signed at all. Maybe the individual files in the image are signed. But so far I haven't seen anything that looks like it.
So if the WP7 ROM Tools can be adapted for this image, be might be able to exploit it and deploy our own patched ROM Images to the phone, just like custom kernels are now deployed to the Samsung Galaxy S. That would be extremely cool.
I attached the extracted OS.nb to this message. Maybe someone can have a look at it. This needs more research.
Ciao,
Heathcliff74
Heathcliff74 said:
Today Samsung released a patch for their WP7 devices to resolve the update problems. WP7 version 7.0.7392.0 has been withdrawn for Samsung devices because of error 801812C1 during the update. After the release of this patch Microsoft has now resumed the release of the OS update for Samsung devices.
The update for Samsung Omnia7 can be downloaded from here.
I did a quick analysis of the file. It is an executable that should be run on a Windows PC. It installs the latest USB drivers for Samsung devices on the PC. Then a flash utility starts. A ROM-file is embedded as a resource in the flashtool. It's called OS.nb and it has a familiar Ra000FF header. So I tried to open it with the latest WP7 ROM Tools. It opens and it shows the "OS partition". But, unfortunately, as soon as I expand that node the WP7 ROM Tools crash. I hope that AnDim, the author of the WP7 ROM Tools, can work on that. The embedded ROM image is about 12 MB. It should contain only the files that are updated.
So this flash tool is able to replace some specific files on the device. That cool and we may be able to use that for other purposes.
I did a quick look at the ROM file in a hex-editor. The file itself does not seem to be signed at all. Maybe the individual files in the image are signed. But so far I haven't seen anything that looks like it.
So if the WP7 ROM Tools can be adapted for this image, be might be able to exploit it and deploy our own patched ROM Images to the phone, just like custom kernels are now deployed to the Samsung Galaxy S. That would be extremely cool.
I attached the extracted OS.nb to this message. Maybe someone can have a look at it. This needs more research.
Ciao,
Heathcliff74
Click to expand...
Click to collapse
I'm highly curious to see what is inside of this file-as you said, it's likely the individual files that need to be updated to the phone. In this case, this could be huge for bringing custom ROMs to Samsung devices. I would experiment some more with this, but I only have one Samsung phone and it's my main, and something on a level this low could easily prove hazardous.
Heathcliff74 said:
I hope that AnDim, the author of the WP7 ROM Tools, can work on that. The embedded ROM image is about 12 MB. It should contain only the files that are updated.
Heathcliff74
Click to expand...
Click to collapse
There are two WP7 partitions in it: SLDR1, SLDR2.
To use with htcrie - cut with hexeditor from 0x8000 and replace in any Full Samsung WP7 rom.
AnDim
AnDim said:
There are two WP7 partitions in it: SLDR1, SLDR2.
To use with htcrie - cut with hexeditor from 0x8000 and replace in any Full Samsung WP7 rom.
AnDim
Click to expand...
Click to collapse
Hi AnDim
Thank you very much for your help. But I can't get this to work. I must have understood your instructions. I used a copy of the stock ROM "I8700XENJK1". I took the file "signed_pda_Cetus_Europe.nb0". It's about 209 MB. I did two attempts:
First attempt:
I took the new file "OS.nb". Copied bytes 0x8000 - C9493F. Opened the file "signed_pda_Cetus_Europe.nb0" and pasted the bytes at position 0x8000, overwriting the existing bytes and writing the file. The resulting file is the same size of 209 MB. Opening this file with htcRIE.exe crashes.
Second attempt:
I took the first 0x8000 bytes from "signed_pda_Cetus_Europe.nb0" and copied them over the first 0x8000 bytes from the new "OS.nb". The resulting file is the same size as the original "OS.nb", around 12 MB. Opening the OS node results in a crash.
Could you please tell me what I'm doing wrong? Thank you!
Heathcliff74
Finally is here! I managed to make a ROM from my Lumia 620 with the latest Windows 10 Mobile build. Here we go!
Windows 10 Mobile Build 10586.36 for Lumia 620 ROM
This Custom ROM is a build and then capture from Lumia 620 with Windows 10 Mobile Build 10586.36 using Windows Phone Internals developed by Heathcliff74. Only works with this Lumia, so don't test in other models, you can hardbrick your phone.
NOTES
This ROM is given "AS IS" and was scanned with MalwareBytes, Kaspersky and NOD32 to check if any malware was in zip file. If you download this file without password and/or CRC32/SHA-1 doesn't match with purposed behind, be careful, ROM could be altered and it would be risky for your phone. In that case, It doesn't come from me!
FILE DETAILS
Name: en_lumia620_Win10Mobile_Build10586.36_AppsUpdated_1-4-16.zip
Size: 1.452.675 KB (1.68 GB)
CRC32: 61FA13A0
SHA1: 8EF66EB5C3B925F7DBF51CEB6C707E36730DC6FF
Password: windowsphoneapps.es
Content: Data.bin file, MainOS.bin file and readme.txt.
Notes: Uncompress with 7Zip is recommended.
ROM DETAILS
ROM Base: 8.10.14219.314 / 3058.50000.1425.10479 / RM-846_eu_france_314.
Languages: English.
System Apps: Updated until 01/04/2016.
Microsoft Apps: Updated until 01/04/2016.
Some third party apps were uninstalled.
This ROM is very close to a stock one. It was free space cleaned up for best practice. It wasn't enabled Root access, so you can do that if you want.
BEFORE INSTALL THIS ROM...
Do a backup of your personal files. Installing this ROM will delete all information in your phone.
You must perform a bootloader unlock to your phone. IT'S NEEDED to flash device with this ROM. For more info, see "Getting Started" section from WPInternals, go to http://wpinternal.net or the official thread.
HOW TO INSTALL?
Open "WPInternals".
Select "Flash" option.
In "Flash ROM" section. click on "Select the source-file to flash to the phone" and select zip file.
Press "Flash custom ROM" button.
Wait until finish and press "OK" button.
Wait until phone starts in Normal Mode.
Go to Setting app > Accounts > Your email and accounts and set up your MSA.
Done!
CREDITS
- If you want to alter partitions files included in ZIP file, please specify that your work is based from mine and come from this thread.
- If you want support my work, buy a beer to me and another one to Heathcliff74. Thanks to his work I wouldn't be able to do that.
My Paypal: http://forum.xda-developers.com/donatetome.php?u=6003114
Heathcliff74: http://forum.xda-developers.com/donatetome.php?u=3254428
MEGA
https://mega.nz/#!9VcXxIiJ!yWPs0caDRAtwDUyVxJPL0RY6FFOKQ7lSy0EpJn6rZLg
Hi!
Small note: If you use the "Flash ROM" function of Windows Phone Internals, it allows you to select a Zip-file. If the Zip-file contains partition images (like your zip-file), it will extract the partitions on-the-fly and flash them straight to the phone. So you don't need to extract the partitions first. Windows Phone Internals will do that for you. It will decompress in-memory, so you don't need a lot of temporary space to extract the partitions.
Thanks for clarification, Cliff. Regards.
@MrCego,
Can i know how fast the rom is in Lumia 620? Are there any bad lags while using apps and such ?
It's the same Build 10586.36 recieved from Windows Insider. About build performance, it's ok, some bugs and little lags, but it's usable as well.
can you guys add project astoria to this build? with the cab files?
surya467 said:
can you guys add project astoria to this build? with the cab files?
Click to expand...
Click to collapse
Project Astoria is dead. I don't think it can be added.
Rivo17 said:
Project Astoria is dead. I don't think it can be added.
Click to expand...
Click to collapse
i agree but i was just thinking of a workaround, since it used to work on an older build which was on slow ring.
Maybe use that as base OS and fiddle with the feature tweaks.
Im just saying this as theory like we used to do on symbian.
surya467 said:
i agree but i was just thinking of a workaround, since it used to work on an older build which was on slow ring.
Maybe use that as base OS and fiddle with the feature tweaks.
Im just saying this as theory like we used to do on symbian.
Click to expand...
Click to collapse
If anyone still has the build on their phone, I'm sure the developers can make use of it. Maybe even use the registry to enable Astoria on newer builds since it doesn't work on them due to missing registry settings.
I am running Windows 10 mobile 10586.38 on my 525. Can u tell me how to make a flashable zip file like yours for my phone
Rivo17 said:
If anyone still has the build on their phone, I'm sure the developers can make use of it. Maybe even use the registry to enable Astoria on newer builds since it doesn't work on them due to missing registry settings.
Click to expand...
Click to collapse
same thought ^
does slow ring still give that old build? or anyone have an image of it? xd
Maybe this ROM is the only one available in the world from build .36.
WPInternals fails to flash this ROM in "flash partitions" mode: "The size of partitions 'MainOS' and 'Data' together are too big", it also fails to flash ROM directly from ZIP archive.
I am flashing Nokia Lumia 620 (RM-846) with WPInternals 1.2 under Windows 8.1 x64
THX for any suggestions
Sorry for late response. Are you tried flashing a stock ROM first?
same problems here too
MrCego said:
Sorry for late response. Are you tried flashing a stock ROM first?
Click to expand...
Click to collapse
i m having the same problems , cant flash the rom direct via the zip file or via unzipping it and flashing separately .
i am on a stock rom (had to flash an ffu image since the phone got stuck in a boot loop during bootloader unlock)
not in a hurry tho , thnx
Try flash France CV stock ROM, boot normally and then flash Custom one.
Sent from Space
MrCego said:
Try flash France CV stock ROM, boot normally and then flash Custom one.
Sent from Space
Click to expand...
Click to collapse
okay ill download the france cv ffu .
i figured one thing out tho , the data and mainOS bin files in the zip you provided are encrypted thats why it says flash failed , i unzipped them and rezipped them without a password and now it says " size of partitions mainos and data together are too big "
No. I tested it many time and with another L620. Do stock flash and we will back to talk later
Sent from Space
MrCego said:
No. I tested it many time and with another L620. Do stock flash and we will back to talk later
Sent from Space
Click to expand...
Click to collapse
nope still says flash failed .
i flashed the france cv ffu and then unlocked the bootloader and tried flashing it with both the methods . none worked
now i am doubting if its actually worth going to win 10 XD
I'm considering to try another one with Redstone.
Sent from Space
"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon
I tried this is working,nice tool.
Thanks dev.
Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
hey there! wonderful tool to have. Thank u so much
Not working in my laptop say a software need a to update
Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?
ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it
How to flash it's says this...
Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?
KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.
Can you please upload Oreo December update stock and patched boot image. TIA
Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.