yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
This is pretty much true.

No tweaks here. Mainly OS & stuff from Microsoft.

Carrier & OEM tweaks, phone specific drivers and applications is found here.

OEM\OperatorPKG\Config_Operator.txt and the files chained along within it is what autoruns during the customization phase.

Some ROMs you can (the ones with .DSM & .RGU) and some ROMs you can't.

More specifically, certain chefs use a Hermes kitchen (0 length .RGU) and other chefs use new options found in Ervius' latest tools (no .RGU and single .DSM), which make it harder to extract a ROM. W/o .DSM files, you lose all directory structure (this hasn't been mentioned in the tutorials).

This kitchen allows for extraction and re-cooking.

Yes.

See above.

.nbh are ready to be flashed to your phone. Run m (for more options) and then step 1a to strip the .nbh header to create multiple .nb files. Your .nbh file will need to be in the BaseROM folder, named RUU_Signed.nbh. Or you can just look in the batch file for what step 1a does and run manually from CLI...

The pagepool changer included within this kitchen predates Dutty's tutorial. it is not a 'true' pagepool changer. What it does is anyone's guess :D

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
The answers to your questions were posted in the wiki a whole month before you asked. :) I didn't bother responding to you before because I figured you'd eventually get around to reading the wiki. If you haven't, I'm now responding a month later to tell you that it's all in the wiki...:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dhhorn:
HTC 3.03 problems

I have cooked several roms based on the HTC 3.03 base. They seem to work ok execpt for the following issues:

1) If the phone wants to restart (like say after the at&t settings configuration, when I click restart I get a black screen and a flashing green radio light. Hiting the reset button brings the phone back and things seem fine after that.

2) the Start menu is basicly empty when I clikc start, however if I use voice command and say start pargrams I get a start menu with lots of cascading folders which pretty much looks right. What am I doing wrong?

3) I tried to make a OEM package out of my voice command cab. but it does not install correctly, does anyone have any pointers?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dhhorn:
Ok, so I loaded up the HTC 3.03.405 ROM and had the same problem with the an application/script trying to reset the machine.

As for the Start menue, to I need to add everything into InitFlash? I guess I assumed that the indivual packages did that. Is there somethine else I'm missing?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] belek:
OEM Packages creating problem

Hi All,

When i try to create an OEM packages from a CAB file (cab name is BELEK.CAB), I've got following error:

"Unable to find .inf file into packages."

Package Creator is trying to extract CAB files to C:\BELEK. If I try to change this directory manually to c:\kaiserkitchen\BELEK, I've got another error message:

"U've cancelled creating package from cab analyzer... exit!"

What is the problem???

Thanks in advance
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] tony_wh:
Reserved. Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sneekyblu3:
when i run kaiserkitchen this is the message i get...i am a noob so please take it easy on me if its something simple i need to do :D

'sleep' is not recognized as an internal or external command,

operable program or batch file.

Now flash your ROM!

Press any key to continue . . .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] andret:
Add new rom to the kitchen

this message can be deleted.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
Multiple Data Sessions Hack?

I am attempting to use Alex's 1.81(1.62 base rom) and his "fixed again" package files to create my first rom. I am not attempting to do anything special but make an ultra clean rom, yet when i try to follow GSLeon3's instructions (below) to enable multiple data sessions i can't find the code instructions in any of the 7 provxml's in oem\operatorpkg. Has anyone else been able to get this to work?

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

There is a simple provisioning XML that makes registry changes related to the RIL settings. In your dumped ROM folders locate the "OEM" Folder & within the OEM folder locate OperatorPKG.

Within the OperatorPKG you will find this provisioning XML:

Code:

<wap-provisioningdoc>

<characteristic type="Registry">

<characteristic type="HKLM\Drivers\BuiltIn\RIL">

<parm name="AGPSNVSetting" datatype="integer" value="6" />

<parm name="NIEnable" datatype="integer" value="1" />

</characteristic>

</characteristic>

</wap-provisioningdoc>The registry setting we want to change via this provisioning XML is the "AGPSNVSetting" value.

*ALSO NOTE: THIS HAS TO BE COOKED IN, REG EDITS AFTER INSTALLING WILL NOT STICK

Change this value to "5" & you will have multi-apn's at least where bbc & primary data (medianet, etc.) are concerned. The final revised xml doc should now look like this:

Code:

<wap-provisioningdoc>

<characteristic type="Registry">

<characteristic type="HKLM\Drivers\BuiltIn\RIL">

<parm name="AGPSNVSetting" datatype="integer" value="5" />

<parm name="NIEnable" datatype="integer" value="1" />

</characteristic>

</characteristic>

</wap-provisioningdoc>

--------------------------------------------------------------------------
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
If the code is not there, then you shouldn't have to worry.

By this I mean that, based on my understanding, those mxip*.provxml files get automatically reprovisioned when the device is reset. Therefore, if there is code in those files that says one thing and you manually change the registry to something it won't matter because it will get overwritten on a cold-boot.

So, if there isn't a key in the provxml file, you don't need to worry about that key getting overwritten.

So you have two choices.

1) Just manually add the key you want to the provxml file

2) Don't add anything and then just set the reg key after you have flashed the ROM. Because it isn't cooked in to the ROM you are working with (in the provxml) the change should stick even after a reboot.

That is my understanding of it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
Thanks for the help, sadly i attempted to leave it out and to add it in and both times it didn't take. I still only have the ability to have one data session open at once :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
The setting you're referring to may not be in the HTC based ROM provxml, as I seem to remember it being an AT&T setting only.

If you're having problems with creating your own working provxml, you may want to use one from an AT&T ROM.

Hope this helps.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
Thank you that makes sense and poses another question at the same time. I am using your att 1.82 rom (says it should say 1.62) making it sound right for being ripped from the feb update release, from your rapid share folder... Was this not from an att rom?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Alex, out of curiosity, why else would a regedit fail to stick unless it is being overwritten by a provxml file?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
dont know if this helps but i think i found the key instructions embedded in PT_Extra_RIL_Setting_31May07. When i unpack it the only item in the cab is an _setup.xml that has the exact programming i was looking for. Now my issue is what do i do with the extracted cab. Can i repack it and install it like a normal cab? i attempted to create a package out of it and have it install through kaiser kitchen but it still didn't stick. Thank you all for the help... i am truly stuck at this point.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Perhaps because a DLL or driver is overwriting it with each boot? Not sure, but that sounds like a good working theory :D I believe GSLeon3 also talks about provxmls and persistent registry entries. I haven't really read up on it...

1.82 was a typo and it was indeed AT&T WM6.0 1.62.

It is possible that the change that GSLeon3 references is only present in ROMs from WM6.1 and onwards. I can't recall since I haven't looked at the 1.62 ROM folders in quite some time. I also seem to remember *_105.provxml for some reason, but I have archived everything and no longer have the files easily available for reference.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
Absolutely. Thank you. I have come to the conclusion it is a limitation of wm6. Or atleast that is what i am telling myself to be able to sleep tonight. I created my own provxml along with using a settings cab that another member was kind enough to create for me and it still would not stick for me :( The only other outstanding question i have for you is if you are considering still releasing the packages and rom for kitchen use so i can try this out on the 6.1 build? Thank you again, and i am only cooking now cause you have moved on :) Thanks for the motivation!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
When I removed all the read-only attributes for the flawed beta2 home release, it really screwed up my \OEM folder. Not sure what it did, but the results weren't pleasant. I didn't back up my folders prior to making the change for the beta2 release, because I thought that the difference would be minor.

Therefore, I'd prefer not to release that kitchen, since I know it has some pretty bad flaws which I haven't even tried to fix...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
some Registry settings are even established at boot time before initialization. These types of setting cannot be changed period, at least not very easily, would probably take creating a new image with PB.

I still believe you are looking at the wrong provisioning xml. The ones you describe are general provisioning files. the AVGPN provisioning is always in a cab file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gadgetdad:
There is good chance that you are right. The .cab file that i found named PT_Extra_RIL_Setting_31May07.cab only had that _setup.xml file in it with the following script:

- <wap-provisioningdoc>

- <characteristic type="Registry">

- <characteristic type="HKLM\Drivers\BuiltIn\RIL">

<parm name="AGPSNVSetting" datatype="integer" value="4" />

<parm name="NIEnable" datatype="integer" value="1" />

</characteristic>

</characteristic>

</wap-provisioningdoc>

I was able to use winrar to unpack it and use notepad to change the value to 5 yet i can't make it back into a cab nor do i know where i would apply it to my kitchen so that it will stick for me.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] wolfgart:
Great Work ;)

Now Xiaomi MI MIX is the greatest device we can have atm
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] raimondomartire:
[MENTION=5672995]jcadduono[/MENTION] [MENTION=608699]wolfgart[/MENTION] Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here

http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961

http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010

But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] agriculture:
development is starting , great work OP
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] wolfgart:
Best device now has best TWRP ever made before.

tnx [MENTION=5672995]jcadduono[/MENTION]

;)
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] jcadduono:
Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.

Update: Official release made on newer TWRP build tree.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] mega00:
Wow, a thousand thanks.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] mega00:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] jcadduono:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.

don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] cultofluna:
Thanks to the devs for such fast development on this great phone ...

I personally coming from lg so xiaomi is completely new for me ...

I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....

I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...

What is that with the different roms?...

And how do i know wich twrp have to install?

Thanks again and sorry for the #noob# guestions....
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] wolfgart:
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .

We are waiting official sources from Xiaomi
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] knives of ice:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] mega00:
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] wolfgart:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] jacky03:
:good::good:
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] jim380:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] knives of ice:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] wolfgart:
you have to Log On with your MIUI account on device too and the retry to unlock

---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------

it works ! I can confirm. And it works using Flashify too
[Huawei P9 Questions & Answers] MontAlbert:
I have a review phone of the P9 (the 09 version). I'm trying to put a nougat beta on it. Bootloader came unlocked- see attached photo. When i go into bootloader fastboot devices sees it no worries. I ran the bat file to check and yes the bootloader is unlocked according to it.

Problem is that when I try to flash TWRP i get:

fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery" (22368 KB)...OKAY [ 0.655s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.667s

I am not a noob to hacking android etc that is for sure but this is doing my head in. Is there an issue with the bootloader unlock? I've sent an email to Huawei support people as well. I had issues getting a bootloader unlock code anyway as being in Australia it doesn't allow be to do anything in Huawei ID, so i cannot get the code. I also tried using the beta app but even when using a VPN it was geoblocked.

ideas on what is going wrong?

thanks
[Huawei P9 Questions & Answers] monoxian:
Make sure OEM unlock is enabled in developer settings. If you have an app called "Phone Finder" or any other phone tracker app, disable it. If that doesn't work, you can try restoring phone to factory settings and enable OEM unlock again then try again.
[Huawei P9 Questions & Answers] MontAlbert:
I tried the above stuff mate- unfortunately it did not work. only phone finder is android device manager and it is turned off (phone is basically stock). OEM unlock is enabled correctly etc. even factory reset and did it all over again. oh well. i give up for now. i would love root on this too...
[Samsung Galaxy S7 Edge Questions and Answers] EduardoAzzolin:
Hey, is there a way to make the photos with the front camera not look so blurred in the S7? Even with that "clear skin" option off, the photos still look bad. :/﻿
[Sprint Samsung Galaxy Note5] auburn2eugene:
Guys, my son messed up and followed instructions off the Max "HighOnAndroid" at www.galaxynote5root.com

He flashed twrp 3.0.2-1

He followed step by step. After flashing twrp, he booted back into recovery and flashed

No-verify-opt-encrypt

And

Update-SuperSU-v2.46

When he booted it back up, its stuck on the sprint splash screen. It is specifically in the screen that says LTE Plus More spectrum better network.

After I got off from work, I came home to him crying.

Ok, I have started to download the factory ROM from Sammobile but I am wondering if maybe there isnt an easier fix. I am not to familiar with changing kernels. Ive never needed to worry about them. Could I maybe just need to flash a new kernel?

From looking on here, really all he needed to do was flash twrp then SuperSU... Does anyone know a way to fix this faster than waiting 6 hours for the Sammobile stock rom?

Please help
[Sprint Samsung Galaxy Note5] auburn2eugene:
Edit....

Ok guys...

I got the file downloaded from sammobile. I installed it and got it installed and working. Then I tried to do the root myself. I followed the guide on this site. However I still couldn't get it working. It was still bootlooping. But not the same bootloop. This time around, it didn't get past the very 1st screen. I again flashed back the stock ROM and again everything works fine.

The files I tried to install are:

Twrp-3.0.2-1nobleltespr.tar.md5

Then I did the twrp install boot deal, booted into twrp and installed:

BeastMode-Stock-N920P-1.3-O16.tar.md5

BETA-Flashable_SuperSU-2.52

I now take it that the issue is my twrp says noble while I read not to use the noble kernel to use BeastMode. But I could be way off...

Man alive, I didn't know just how much I appreciated CF Auto Root until just now...
[Sprint Samsung Galaxy Note5] tdunham:
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.

The method you are using is from a very old thread. Follow the instructions in the thread below.

[How-to] Root your SM-N920P Device - all versions
[Sprint Samsung Galaxy Note5] auburn2eugene:
Thank you for responding. I was able to get the factory ROM installed and working fine.

I have downloaded the MOAR for the device and plan on giving it a go.

I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...

As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/

I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.

Like I said in my last post, I have never missed cf auto root so badly...
[Sprint Samsung Galaxy Note5] tdunham:
Root on stock is relatively simple.

TWRP + SuperSU only.

But as you saw, it's still easy to get it wrong.
[Sprint Samsung Galaxy Note5] auburn2eugene:
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.

If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.

But I'm going to take a look at your link you provided and see if I can't get root 1st.
[Sprint Samsung Galaxy Note5] tdunham:
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.

For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
[Sprint Samsung Galaxy Note5] auburn2eugene:
Thank you for pointing me to your thread. I was able to get root on my sons phone. Hard to believe the SuperSU was the problem... But it was... I was using the one from chainfires site, but yours worked when his created bootloops.

Thanks again!
[Sprint Samsung Galaxy Note5] phat0074:
Is there a root method for pk1
[XDA Assist] ahmlet:
I cant boot this cellphone samsung j7008 clone chinese mt6580. Any link to official or working firmware to flash using SP flash tool?
[XDA Assist] ahmlet:
help needed
[LG V20 Questions & Answers] LiquidHonesty:
Anyone else having issues sending MMS via anything other than the stock app? I've used Textra, Evolve, and now Google's messenger and none will send MMS nor receive MMS, I have to open the stock app on the phone to get them. I actually went a week not knowing it was happening until someone mentioned they had sent me a pic, so I opened the stock messaging app and showed I had a lot of MMS I hadn't even received.

I revoked permissions from the stock app, reinstalled the other app, even etc, but still nada, can't send/receive MMS at all.

Thoughts?
[LG V20 Questions & Answers] dwertz:
I am using YAATA no issues, but I did not disable the stock app or verizon messenger+ because my watch uses verizon messenger+

MMSCC Url

http://mms.vtext.com/servlets/mms

MMS Proxy

nothing (blank)

MMS Port

80

I also put mms over wifi
[LG V20 Questions & Answers] LiquidHonesty:
I haven't disabled anything, and it still doesn't work. I have given every app all the permissions they needs (stock messenger, google messenger, etc) yet it still won't send MMS in Evolve, or Google Messenger........ONLY the stock LG Messenger. :(

Anyone have any more ideas?
[LG V20 Questions & Answers] twistedvip:
Actually ive had issues with mine on occasion using Textra. Tells me that my APN settings are not working or something like that. Mines AT&T variant though. Idk whats up but its annoying as hell.

But after like 10 minutes it works just fine again.
[LG V20 Questions & Answers] Ryano89:
Did you buy it from Verizon? In other words is it the Verizon model, or just being used in Verizon?
[LG V20 Questions & Answers] ZachJohnson:
I've had the same issue. The weird thing is it started out working fine - I'd installed Google Messenger and I received mms group texts just fine for a couple days, but now every mms message just says "downloading"...
[LG V20 Questions & Answers] capaz:
Same issue here, with Verizon phone. Also worked fine for first week or so using Google Messenger. Now neither that nor LG Messages apps can send/receive MMS - only Verizon Messages+ works.
[LG V20 Questions & Answers] ZachJohnson:
I can't figure that one out, why it worked initially... I haven't taking the OTA, and I didn't really do anything that should have changed that, it just up and quit...

I've had luck getting Textra to work. There's an MMS Behavior option in there - Legacy appears to work (I think that's the default), system does not, then it's all just perpetually downloading...