yashsingh1/xdaforums huggingface dataset:
[Redmi Note 12 Pro / Pro Plus 5G] rudiratlos57:
[2024-06-03 14:30:32:982:982466 a6ibj7njcakri7aa]:MiFlash 2022.5.7.0

[2024-06-03 14:30:32:982:982466 a6ibj7njcakri7aa]:vboytest index:1

[2024-06-03 14:30:32:998:998092 a6ibj7njcakri7aa]:Thread id:12 Thread name:

[2024-06-03 14:30:32:998:998092 a6ibj7njcakri7aa]:image path:I:\HyperOS Global1030

[2024-06-03 14:30:32:998:998092 a6ibj7njcakri7aa]:env android path:"H:\Tools\MiFlashPro\XiaoMiFlash\Source\ThirdParty\Google\Android"

[2024-06-03 14:30:32:998:998092 a6ibj7njcakri7aa]:script :I:\HyperOS Global1030\flash_all.bat

[2024-06-03 14:30:33:013:013716 a6ibj7njcakri7aa]:Physical Memory Usage:3584000 Byte

[2024-06-03 14:30:33:013:013716 a6ibj7njcakri7aa]:start process id 3292 name cmd

[2024-06-03 14:30:33:044:044986 a6ibj7njcakri7aa]:info1:$fastboot -s a6ibj7njcakri7aa getvar product 2>&1 | findstr "ruby" ||

[2024-06-03 14:30:33:060:060591 a6ibj7njcakri7aa]:info1:product: rubypro

[2024-06-03 14:30:33:060:060591 a6ibj7njcakri7aa]:info1:$if exist I:\HyperOS Global1030\images\anti_version.txt (for /f "delims==" %a in (I:\HyperOS Global1030\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a))

[2024-06-03 14:30:33:060:060591 a6ibj7njcakri7aa]:info1:$if [] EQU [] set CURRENT_ANTI_VER=0

[2024-06-03 14:30:33:060:060591 a6ibj7njcakri7aa]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s a6ibj7njcakri7aa getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )

[2024-06-03 14:30:33:091:091867 a6ibj7njcakri7aa]:info1:$(set version=1 )

[2024-06-03 14:30:33:091:091867 a6ibj7njcakri7aa]:info1:$if [1] EQU [] set version=0

[2024-06-03 14:30:33:091:091867 a6ibj7njcakri7aa]:info1:$set anticheck="antirollback check pass"

[2024-06-03 14:30:33:091:091867 a6ibj7njcakri7aa]:info1:$if 1 GTR 0 set anticheck="Current device antirollback version is greater than this pakcage"

[2024-06-03 14:30:33:091:091867 a6ibj7njcakri7aa]:info1:$echo "Current device antirollback version is greater than this pakcage" | findstr /r /c:"pass" ||

[2024-06-03 14:30:33:123:123091 a6ibj7njcakri7aa]:info1:"Antirollback check error"

[2024-06-03 14:30:33:123:123091 a6ibj7njcakri7aa]:info1:"Antirollback check error"

[2024-06-03 14:30:33:123:123091 a6ibj7njcakri7aa]:begin FlashDone

[2024-06-03 14:30:33:123:123091 a6ibj7njcakri7aa]:error:"Antirollback check error"

[2024-06-03 14:30:33:123:123091 a6ibj7njcakri7aa]:process exit.
[Redmi Note 12 Pro / Pro Plus 5G] NOSS8:
Did you delete all these lines in the BAT file?
​

Spoiler content hidden.

​
[Redmi Note 12 Pro / Pro Plus 5G] rudiratlos57:
Did you change the "flash_all_back" file? (like I changed it)

I also had the problem with the "antirollback check error"

Yes, I did exactly that, but it didn't work at first.

Then I just flashed the vbmeta and the boot.img from Lineage os A14 on a whim, after that only the bootloader worked, then I flashed the global with the changed bat files again with MiFlash and lo and behold.....it suddenly worked for whatever reason.....actually pretty illogical,,, but whatever, the main thing is that it worked.

I'd still like to understand it though

Thanks for your help anyway!
[Windows 11] da1uluv2hate:
How to get and use dapps
[Windows 11] xXx yYy:
AFAIK DApps, short for decentralized applications, are essentially applications that run on a blockchain network instead of a traditional server: The code and data are spread across a network of computers, making them more resistant to censorship and downtime.

Because DApps interact with blockchains using cryptocurrency, so you'll need a crypto wallet to store your digital assets and connect to DApps. Popular options include MetaMask, Trust Wallet, and Coinbase Wallet. These wallets typically offer browser extensions or mobile apps for convenient access.

Once you've chosen a DApp, visit its website or launch its app. You'll likely find a "Connect Wallet" button. Clicking this initiates a connection process where your wallet interacts with the DApp. This might involve approving the connection and potentially paying a small transaction fee.
[Vivo Nex Guides, News, & Discussion] KidCarter93:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Vivo V9  Guides, News, & Discussion] KidCarter93:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Windows Mobile Software Development] bepe:
I have been working on this new ROM Kitchen project over the last months.

Public beta can be found here:

http://www.darkforcesteam.com/showthread.php?p=3560
[Windows Mobile Software Development] motisu:
Downloading this minute. Is it also for old devices? (Blue Angel?)
[Windows Mobile Software Development] gerald_s:
Sounds great, thanks for this kitchen
[Windows Mobile Software Development] bepe:
Should theoretically work for all HTC devices.

Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...
[Windows Mobile Software Development] Ather:
Nice to see you back Bepe!, Happy New Year :)
[Windows Mobile Software Development] KMFM$:
OMFG

bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations. :D
[Windows Mobile Software Development] guitardoc64:
Downloaded, will check it out and post results. Thanks!!!
[Windows Mobile Software Development] monkey1208:
:p:p

Hmm.it will work on all htc devices.

maybe some older dev cant use,need to test by yourself

really nice Rom Kitchen.

Great jod!!!

Cheers

Monkeybape
[Windows Mobile Software Development] sackbauer:
i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*
[Windows Mobile Software Development] chavonbravo:
Is removal of unneeded files from XIP supported, bepe??
[Windows Mobile Software Development] mbarvian:
this look fantastic bepe, as usual ;)

even though I have tested it, I noticed two things:

1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?

2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?

other than that, it looks GREAT!

thanks again
[Windows Mobile Software Development] bepe:
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.

the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.
[Windows Mobile Software Development] bepe:
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.

example:

- you are using a WWE Kitchen with a WWE nls size: 267 KB

- you want to change lang to CHT, the nls size would be 1500 KB

--> this means the size of the xip section would grow very much

--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP

--> ImplantXIP.exe should give you an error I think... never tried it...

solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)

The CHS roms would have more space for XIP, so all would be working fine

2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:

- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD

- Base_DPI_96 - only for QVGA devices

- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for

You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...

... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed
[Windows Mobile Software Development] Fancy_Lad:
Would take a look at it, but the forum requires compulsory registration to view. :(

Please fix your forum.
[Windows Mobile Software Development] MrDSL:
It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.
[Windows Mobile Software Development] gullum:
I keep getting this error when it comes to running platformbuilder

This aplication has requested the runtime to terminate it in an unusal way
[Windows Mobile Software Development] dan-htc-touch:
boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve :) Thanks much for sharing your work with all of us though
[Windows Mobile Software Development] egzthunder1:
Good to see you back bepe!!! I will give this a shot later on today...
[Windows Mobile Software Development] Knumb:
outstanding bepe!! I thought your tutorials were excellent too!
[Windows Mobile Software Development] !Aman!:
thanks bepe :)

tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin :). although i had to make some adjustments to Dump_200.bat for dumping the ROM.

also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?

and, do check your paypal for Transaction ID: 45A49499TS934251W :D
[Windows Mobile Software Development] ngagephone:
Hi nice kitchen but the package builder dosent work for me it just pops up with a black dos prompt then disappears and the old package tool loads up then i select the dump folder and nothing happens is there any files needed and runtimes or something?
[Windows Mobile Software Development] bepe:
Thank you very much! :)

Changing kernel modes is not part of the tool anymore,

but at http://msdn.microsoft.com/en-us/library/aa908726.aspx you can read about the ROMHDR stuct.

ROM\romhdr.bin is exactly this struct and can be edited using a hexeditor before building the rom... or perhaps someone will make a tool for that
[Windows Mobile Software Development] bepe:
No other files should be needed, please check out the video tutorials on how to use the tool.

You just need to drop the dump or IMGFS folder onto packagebuilder.exe, no need to select a folder this way ;)
[Windows Mobile Software Development] duttythroy:
nice work bro once again you outdone it.:D
[Windows Mobile Software Development] !Aman!:
thought so :)

however could u look into implantxip's problem?

PS: could u send me the tools without donations text :D?
[Windows Mobile Software Development] nosedive:
yeah nice work ... thanks

definitly a replacement for my old kitchen ;)
[Windows Mobile Software Development] pawaj:
If you use Ervius's XIPExporterEX you should write new MBR to your reduced payload and implantxip will work fine.
[Windows Mobile Software Development] ngagephone:
Hi yes sorry i was talking about the old package tool. But yes when i dump the imgfs dir onto the package tool the screen pops up with a dos prompt then it exits within a second please help thanx.
[Windows Mobile Software Development] MrDSL:
If no other files are needed can anyone tell me why I get a missing file msvcr71.dll error when I try and dump my os.nb?
[Windows Mobile Software Development] !Aman!:
i know, but Ervius' tool doesnt remove the ULDR completely ;)

@bepe: implantxip problem is becauase i've removed my ULDR partition completely. could u fix implantxip to handle such situations? thanks.
[Windows Mobile Software Development] !Aman!:
just copy this dll file into windows\system32, that should be enough.
[Windows Mobile Software Development] Ather:
thats the requirment of windows to run C++ Programs, look for that Dll on google or install Visiual Studio Redistributable Package 2008
[Windows Mobile Software Development] MrDSL:
I'll install that tonight thanks.
[Windows Mobile Software Development] nosedive:
errorlevel

i did all the conversion and that stuff from my old kitchen..

but when execute build_rom.bat i get an errorlevel 3 right after processing extended packages ... it says done! but, then the error pops up ... i guess its the same error gullum reported in post 16

do you need more info?

edit 21:34

i guess it has something to do with os.nb.payload

the payload i use is working successfully with buildos..
[Windows Mobile Software Development] ngagephone:
Hi still no luck with the package builder any help please.

When i drag my dump folder on to the package builder the dos propt just opens then close instant.
[Windows Mobile Software Development] anryl:
723fb954-d931-4348-b672-82a188e587b5.dsm

sorted :cool:
[Windows Mobile Software Development] Premananda_laishram:
doubt

Will this kitchen work in building rom for Asus P525?
[Windows Mobile Software Development] Laurentius26:
Hi,

I had also this problem with setting up the kitchen (ERROR LEVEL 3 :D).

Some tips I like to give you about that.

Use the toolset in the kitchen to setup the kitchen!

I mean, to make it work don't use a SYS, XIP or OEM dir from your previous used kitchen.

Start with setting up the kitchen using a shipped rom and see if it cooks fine.

Another tip:

To extract the .nbh to get os.nb I used Bepe's Simple Live Tools:

http://www.darkforcesteam.com/showthread.php?t=289

When it works you can start converting the packages to EXT.

Just wanted to let this know so others could see and not having a hard time setting up the kitchen.

Thanks Bepe, I'm getting used to the kitchen now. :)

Grtz,

Leo :)
[Windows Mobile Software Development] !Aman!:
i used OEM and SYS directly from my old kitchen and they worked perfect :D
[Windows Mobile Software Development] Laurentius26:
Yes I know, but I was struggeling for days to make the kitchen work.

'Error level 3' all the time :mad: , yesterday I discovered it happened because of one stupid package I was using in SYS hehe... :D

So I think it's a good tip to start from scratch and add your packages and tweaks one by one.

It will save time and a lot of stress! ;)
[Windows Mobile Software Development] nosedive:
yeah, i can confirm.. it was because i made the ext folder myself..

besides this kitchen really works well and fast! :D
[Windows Mobile Software Development] c_shekhar:
Hi bepe!

Firstly falicitations for releasing yet another landmark in ROM cooking.

But, I notice that it essentially gived a ROM which has all the RGUs as well as DSMs deleted. As a result the ROM cannot be repackaged after it is dumped.

or I need some more lines in the BuildROM.bat?
[Windows Mobile Software Development] xtep:
Problem with modules relocation

I have tested this new tool with the files of my own ROM kitchen (x7510 with ported 21109 build), but I can make the resulting ROM to work properly (some programs features works others don't)

I think that there is some problem with the modules: I have compared the temp/dump folders generated by platformbuilder and buildOS and I have found that int the dump folder created with the new platformbuilder all the modules lacks the last S00x file.

For example: module ceshell.dll (in folder dump\ceshell.dll)

- Files with platformbuilder: imageinfo.bin S000 S001 S002

- Files with buildOS: imageinfo.bin imageinfo.txt S000 S001 S002 S003

I think that imageninfo.txt is the same info that imageinfo.bin, but what happened with the last section file?
[Windows Mobile Software Development] aalim:
the Greatest of all tools

cant believe it is real

Can you please make a pdf guide with steps as i cant play the video properly (flash consumed memory)

or just upload it to you tube??
[Windows Mobile Software Development] aalim:
Found Following problems:

-------------------------

1. With original roms: i get an error with nmerge at last stage of building (i attached a photo).

2. In case of cooked roms: sys files are dumped in the dump folder inside a subfolder with the rom name beside .ROM & .VM folders and it gives me an error: cannot overwrite & if i put all sys files into dump it gives an error: coudnlt find initflash.dat in specified folder.

3. Can OEM2EXT tool work for older device roms or only with those with PACKAGE-something??

My device is trinity & tried also to cook a rom for diamond but so far couldnt cook anything. is there a package or some runtime i should install before i try the kitchen??

AND WHERE is EVERYBODY???
[Windows Mobile Software Development] itje:
just donated, Transaction ID #5H060262YW8283458

good work, as always.

cheers
[Windows Mobile Software Development] tomal:
Anybody has noticed that that .provxml's under EXT doesn't work with the new kitchen. Is it because of missing DSM's or I'm missing something?

Transaction ID: 8C3683187R8209018 :)
[Windows Mobile Software Development] GSLEON3:
The provxml's work for me all the time when OEM'd using oemizer, & only most of the time when individually placed within the EXT folder.

Otherwise it works great. Just wish you could more easily mix & match SYS files. You cannot relace the .rom & .vm modules only, at least not all the time, as you get boot errors, even with reloc tools. Nice & easy XIP porting though!
[Windows Mobile Software Development] bepe:
Yes, thats right.

DSM and RGU files ar not needed by the OS, so they are all removed.

If you want to offer a rom to public that other users can recook, why not release the whole kitchen?

More files in the rom mean slower OS, so it makes no sense to keep this files
[Windows Mobile Software Development] bepe:
the last section is reloc section, needed for:

- updating the flash using *.cab.pkg or *.cab.pku files (UDLR and that stuff)

- for relocating a rom when building it

it's not needed for running a rom!

PRB removes this sections since no one of you is (/should be) able to make pkg nor pku files.

this is like removing the ULDR partition from a rom:

- might free some IMGFS space

- less loading time for modules... not much... but one section does not need to be checked

- after dumping a rom build with PRB it can't be recook (you can think of it in some kind of protection)

the relocation process is perfect, but for this you need, clean, bug free, modules, best would be from an original rom
[Windows Mobile Software Development] bepe:
provxml's in EXT are working fine for me
[Windows Mobile Software Development] sk801:
I'm trying to dump HTC's kaisers WWE 3.34.721 rom.

Quick question.

If no .dsm or .rgu files appear in the XIP folder does that mean they were never originally in the OEM .nbh file?

P.S. Thanks for the great tools bepe! :D
[Windows Mobile Software Development] corosivi:
hi

Is it also for dell x51v devices?:eek:
[Windows Mobile Software Development] xtep:
Thanks for the info.

Sorry If I offended you. I know that your software is always good coded and tested.

What do you mean with this. All the modules I use are taken from an original ROM, but the ROMs that I cook with your tool do not work properly (for example cab files cannot be opened or activesync does not work).

One of my experiments is to build a ROM for a HTC Universal. I have a WWE ROM based that use your tool and i want to translate it to Spanish, so I remove english packages and replace it with spanish ones taken from other original ROM (for other device). It seems clean and easy but it does not work.

Other of my trials is to take a rom cooked by myself for a x7510 that works fine. I dump it following the instructions in your tutorial and then I rebuild it without any changes. This rom does not boot.

Can you (or someone) help me?
[Windows Mobile Software Development] tomal:
I've published a kitchen for Universal, which has been built based on Bepe's PRB. You may take a look here:

http://xdaforums.com/showthread.php?t=476544
[Windows Mobile Software Development] littlescott:
Hello, I get this same problem, when I run it from the prompt it complains that about 20 mxip files are missing. :/ Am i doing something wrong?

Cheers,

Scott
[Windows Mobile Software Development] Fraction:
@bepe:

can u mirror the public beta for the second forum.? i dont wanna register ;P

thx
[Windows Mobile Software Development] utak3r:
Tested with Hermes - works ok :)

Thanks bepe for your work :D
[Windows Mobile Software Development] Mnemonique:
Tried using it with Blue Angel...

didn't worked for BA's :(

using *200.bat
[Windows Mobile Software Development] mettercomputers:
can someone share a mirror for this darkforcesteam site is down thank you
[Windows Mobile Software Development] CRACING:
I am too facing same problem, Can anyone plz help

Thanks in advance
[Windows Mobile Software Development] :
Guys I am using this kitchen for a non-HTC device i.e. the MWG Zinc II...I have xip.bin and imgfs.bin from Part01.raw and Part02.raw using pdocread. The only problem I am having with this kitchen is that I have no os.nb.payload. How should I go about solving or working around this issue?
[Windows Mobile Software Development] CRACING:
Use your os.nb base file and rename to os.nb.payload. :D
[Windows Mobile Software Development] DaveShaw:
Can't you just dump them using IMGFSTODUMP ?

Then just rename dump to IMGFS.

You'll then have the IMGFS folder like you dumped the new OS_NewOSBuild.nb in this video : http://www.bepe80.com/test/2/

Have a look into the readme in imgfs tools\bin for more info on the dumping tools.

Ta

Dave
[Windows Mobile Software Development] :
The problem isn't that I can't extract imgfs.bin, the problem is to build the ROM you need os.nb.payload alongwith the XIP folder and romhdr.bin and I do not know how to get to os.nb.payload from just xip.bin and imgfs.bin
[Windows Mobile Software Development] trueg:
Anybody have any luck finding a mirror? I registered on DarkForcesTeam forum a few hours ago and still do not have access to it. :(
[Windows Mobile Software Development] utak3r:
JUst either change the scripts or rename your os.nb file to os.nb.payload. Not every device has their rom images splitted in that way. Just do it, don't mind of this .payload thing.
[Windows Mobile Software Development] :
as I said sir I do not have the os.nb files...the xip and imgfs are from a dump and the original rom cannot be extracted
[Windows Mobile Software Development] CRACING:
Don't you have base os.nb? Its impossible to cook rom's without this file.

Thanks and regards