yashsingh1/xdaforums huggingface dataset:
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] paranoia_gu:
good rom.

thanks PIPIPIG233666
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] PIPIPIG233666:
link had been posted,enjoy!
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] rEsonancE_0404:
Only need firmware based on 10? Or firmware+vendor?
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] wolf9119:
thank u ....
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] soumyachatterjee:
Thank you for this.

What is the kernel you are using here?
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] Joakin2k:
Does this changes Mac address or other partition like the old build or it's safe ?
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] djdelarosa25:
LineageOS one. There's a screenshot of the build details on the original post.
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] s k:
Good job! Keeping the fingers crossed for getting an official status!

Keep rocking!
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] maroc84:
So there is no way to download at the moment :(

Is it possible to build myself from your source with this howto https://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html

or is there something to be aware of or to add or so so I (with no expericence in Building a ROM) will not be able to do this with this guide?
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] owlonke:
Please reupload or do something. I can't download from google drive because many people downloaded it. I want too...
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] ragnar6666:
I'm currently on MIUI v11.0.3.0 (Android 9) Global stock rom.

I have unlocked the bootloader and installed twrp recovery and magisk. So do I just place the rom zip into my internal storage and flash it via twrp? or there are any prior steps before installation?

Also in the instruction, it says to wipe internal storage as well. Can someone explain why?

This is my first time flashing a MIUI device :p
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] BusterCZ:
I guess that you will need to update to android 10 in prior as it will definitly be based on android 10 vendor.. Or atleast you should flash android 10 firmware (dont have a link at the moment). By wiping internal storage he means format data option in TWRP. This will delete all your data on your phone. The only reason behind this as far as i know is because the storage is encrypted by the MIUI and this new OS would not be able to decrypt it.
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] maroc84:
My Wifi-MAC got changed! :mad:

Edit:Switched back to my old ROM

- MAC addresses were changed (to maybe Pigs?)

- Fingerprint again not working

so I'll wait ...
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] xellosx:
check when you connect in wifi if you are using randomized mac instead of your device one because it's an android 10 feature
[Tilt, TyTN II, MDA Vario III General] Gaz123:
Phone Not Allowed MM#6

What dose it meen please,I have seen a few people asking about this and no one has come out and said what it meens. can you help?.

thanks gaz
[Tilt, TyTN II, MDA Vario III General] redbandana:
how often do you get this message?

I received somthing similar when I was receiving an MMS and attempted to make an important phone call but I don't remember that crazy MM*5 stuff
[Tilt, TyTN II, MDA Vario III General] Gaz123:
my htc is a work phone they had to cut off but said i can keep the phone has i dont work there any more.

its comes when i am trying to put other sim in,has i dont have a 02 sim thats what the phone was locked too.

i am half way trying to nulock it but no luck atm.

but i seen a few asking about it.

gaz
[Tilt, TyTN II, MDA Vario III General] Gaz123:
bump sorry 4 this but i like a answer thanks
[Tilt, TyTN II, MDA Vario III General] whk:
Sounds like you are trying to use an INVALID SIM or putting a SIM card in that is not working for some reason.

Does the SIM card you are trying to put in work on another phone?

Bill
[Tilt, TyTN II, MDA Vario III General] Gaz123:
i will test it when i get a other moblie but i am having problems unlocking the phone ,you could be right
[Tilt, TyTN II, MDA Vario III General] Gaz123:
Phone Not Allowed MM#6

its when the moblie company are told the phone has been stolen with the sim card,they kill the sim but also block the phone the sim was last in.

so it stops people using ithe phone with any sim at all.

They are going to unblock it has it was a miss under standing takes 7 days.

just so people know has i have seen 1 or 2 people asking.

gaz
[Asus ZenFone Max Pro M1  Questions & Answers] asthrofelis:
How we can share the same WiFi we use?? Please help!
[Asus ZenFone Max Pro M1  Questions & Answers] RedGreenBlue123:
Use Bluetooth tethering instead of WiFi hotspot.

Pair your device that need internet connection with the hotspot phone.
[Asus ZenFone Max Pro M1  Questions & Answers] asthrofelis:
Thank you,

Yup, I was mostly doing that but I heard that there is a option to share through WIFI. Which can be more fast than Bluetooth tethering.

But I don't know how to access in here..
[Asus ZenFone Max Pro M1  Questions & Answers] RedGreenBlue123:
WiFi tethering is faster but it can only share Mobile Data, cannot share WiFi. Use WiFi tethering on your Windows PC. It can share connected WiFi.

Windows 10:

Windows 7:

https://www.pcninja.us/turn-your-windows-7-laptop-into-a-wifi-hotspot
[Asus ZenFone Max Pro M1  Questions & Answers] mujammil786:
Use netshare.
[Samsung Galaxy Note 8 Questions and Answers] TheLogicalGamer:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.

Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.

I'm aware I can restore to stock via odin. But I have a couple of questions.

A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?

And

B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)

Thanks in advance for any help you can provide. :)
[Samsung Galaxy Note 8 Questions and Answers] ZeroXO:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
[Samsung Galaxy Note 8 Questions and Answers] TheLogicalGamer:
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.

Is the unknown (bat) firmware the one I need to flash to stock?
[Samsung Galaxy Note 8 Questions and Answers] stonedpsycho:
Using odin 13.1.3 is recommended.

As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)

If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.
[HTC 10 Questions & Answers] ricjames1129:
Hey guys, I've learned a lot reading from previous posts and solved a lot of issues I've come across but now I've encountered a problem that for the life of me I cannot fix. Initially my HTC 10 was rooted S-On and unlocked bootloader but I decided to bring it back to stock for various reasons. I flashed this ruu that I was able to find while digging through HTC's support website "RUU_PERFUME_UL_N70_SENSE80GP_MR_TMOUS_2.51.531.32.exe" and at first it seemed like everything was brought back to stock but after putting my sim card in the phone no longer detects it and no matter how many times I try to reseat or format and wipe the cache on TWRP the problem does not go away. I would appreciate any input and will happily provide info requested on my part.

Thanks
[HTC 10 Questions & Answers] santod040:
Guessing you already had Oreo on there, prior to flashing back to Nougat.

In which case your sim won't be read again, until you either erase the persist partition as instructed in the "downgrade" thread which is all about this issue specifically, or upgrade back to Oreo.

https://xdaforums.com/htc-10/how-to/downgrade-problems-downgrading-htc-10-t3735658
[HTC 10 Questions & Answers] ricjames1129:
Actually I was on Android 7.0 the whole time, I just had it rooted and unlocked. My original plan was to de brand my phone and get rid of the Tmobile bloatware but I hit a road block when trying to get S-Off so I just stopped there. I'll go through that thread and see if I can figure it out. Thanks!
[Touch Diamond, MDA Compact IV ROM Development] DesktopMan:
Some observations:

HTC say 192 MB on their page

Settings -> Device Information says 192 MB

So I guess we have established there's physically 192 MB.

Now... This is where it gets confusing:

Settings -> About says 113 MB. Why is the rest hidden, and what (if any) is it dedicated to? That's 80 MB gone. On my P3600 only 15 MB is subtracted here. VGA screen can only account for a few MB.

The task manager also says 113 MB, and with no applications running except TF3D after a soft reset only 55 MB is free. 30MB more than my P3600. Killing TF3D and soft resetting nets another 10 MB.

Naturally there can be differences depending on kernel versions, hacks and so on.

Some interesting math:

192MB (total) - 64MB - 15MB (value from p3600) = 113MB.

To me it looks like 64MB has been swallowed, or dedicated to 3D (why on earth would it need 64MB), or something else. The 15MB portion I assume is for kernel memory. As a side note, current HaRET version reports 128MB.

Thoughts?
[Touch Diamond, MDA Compact IV ROM Development] mr_Ray:
My thought would be "What does this have to do with ROM Development?"

Wrong forum. Let's try and keep the place tidy.
[Touch Diamond, MDA Compact IV ROM Development] DesktopMan:
IMO this has a lot do do with ROM development, seeing as custom ROMs strive for more free memory. I did debate putting it in the "Diamond" forum, but most posts are less technical there. If a mod disagrees feel free to move it.

Also, the only way you could possibly do anything with the ram setup would be a ROM modification.
[Touch Diamond, MDA Compact IV ROM Development] thaihugo:
I don't own the diamond, but couldn't this 64 mb be some video memory, like some pc embeded controlers?
[Touch Diamond, MDA Compact IV ROM Development] DesktopMan:
It could, but 64MB is a crap load for a barely capable chipset and a 640 * 480 screen. I have not seen any details on what kind of 3D hardware is actually in there, as they're holding the inner workings pretty closely wrapped.
[Touch Diamond, MDA Compact IV ROM Development] Yzord:
My guess, and correct me if i'm wrong is the 80mb preserved for the cab files?
[Touch Diamond, MDA Compact IV ROM Development] ponq:
Settings-> Device Information says 192MB Ram, 256MB Flash.
[Touch Diamond, MDA Compact IV ROM Development] TML1504:
I can give you the right answer:

The 64MB are reserved for the opera browser! I've read that somewhere else,

unfortunately I can't remeber where.

So I guess there would be cooked roms in the future without opera

and 64MB more ram...
[Touch Diamond, MDA Compact IV ROM Development] rorydaredkign:
what do you mean? like an old extended rom?
[Touch Diamond, MDA Compact IV ROM Development] Yzord:
yes..................
[Touch Diamond, MDA Compact IV ROM Development] TML1504:
i dont think that it would make sense to waste so much RAM for the cab files,

because they would only be needed once in the customizing process at the

first start of the device...

as i wrote above, according to my findings the 64mb are reserved for opera!
[Touch Diamond, MDA Compact IV ROM Development] Swiftblade:
The cabs file or the extended rom takes up storage memory and not the program memory. I read it in some review that 64MB of the program memory is dedicated to the GPU for graphics rendering of the VGA display.
[Touch Diamond, MDA Compact IV ROM Development] sorg:
Quallcomm CPU with 3D graphics requires 64MB RAM dedicated to 3D functions. No other data can be placed in thise 64MB and it can not be freed.

that's why Diamond (and Sony Xperia X1) have so huge amount of RAM.
[Touch Diamond, MDA Compact IV ROM Development] rhedgehog:
64mb just for the 3D? That explains why there weren't any 3D drivers in the kaiser and the polaris then.....
[Touch Diamond, MDA Compact IV ROM Development] walshieau:
ok this is ALL BS, the 64MB isnt "reserved", Windows Mobile reports the RAM and ROM differently then a usual PC / Windows operating environment.

It falls back on the NAND partitions and whats allocated to what. So in future this still has nothing todo with "ROM Development" so please post this in the General diamond forum.

PS: ET did partition the NAND and he ate 45MB of the ram :p
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
jesus you rarely see this load of BS :)

opera, noo, say that was meant to be a bad joke.

and please do not confuse ROM and RAM. cab files for RAM, when the ram contents get lost on battery removal?!? also the nand partitioning doesn't matter for ram, nand is rom.

not sure about the 3D, but it is quite unlikely it'd want 64MB ram. (I can check later if it accesses that much.)

what is for a fact is that there is an extra RAM shared by the radio and the SPL. the OS does not access any of it normally - but *you* can programmatically access it if you really want to, or even by using pmemdump ;) . (except you are less free to access some parts that the radio restricts access to)

however this RAM is present in all the MSM7xxx, but not reported in deviceinfo on kaiser etc, and seems to be 32MB only (though on diamond I saw indication that it might be 64, I will have to re-check that, probably my memory is failing).

but, what appears in deviceinfo is just a hardcoded value that HTC decides on. maybe for marketing reasons they chose to add this in the total RAM.

one last fact - the OS on the diamond only has access to 128MB of whatever this 192 is, this is easily seen (in nk.exe, romheader, etc), the rest is definitely reserved (either radio, or 3G, etc..). so it isn't WM itself that is eating it up.

that's the best I can say so far without specifically looking, but this is an interesting question and I'll look into this.
[Touch Diamond, MDA Compact IV ROM Development] s1rl4ncel0t:
Finally, someone who seems to know what he's talking about!!!

It's amazing how many fake problems arrise in this forum because of the lack of knowloged of people, which leads to "theories of conspiracy" and sometimes to funny jokes...

64MB RAM for Opera is a good example of a joke...for the love of God, my Opera on my PC, while working with torrents, emails, thousands of favorites, browsing history older than my great-great-grand-father, only takes 40MB RAM...so why the hell would a **** program like opera mobile would need 64MB RAM?...

Anyway, if you're not sure about what you guys are writting, it's better to stay shut up, instead of inventing things and inducing other people in error...

HastaSSSS
[Touch Diamond, MDA Compact IV ROM Development] Olipro:
"she" actually :)
[Touch Diamond, MDA Compact IV ROM Development] DesktopMan:
As fun as conspiracy theories are, I'm happy to get an answer that makes a little sense :)
[Touch Diamond, MDA Compact IV ROM Development] rorydaredkign:
So the Kaiser has this extra RAM that you can't use, but HTC didn't put it in its Device Info. Strange. Yet it's misleading to say the Diamond had 192Mb of RAM, when you cant USE 64Mb of it.

And this also suggests that the pre-release devices didn't infact have less RAM, but Just didnt have the hardcoded device info with 192MB.

How very funny that someone actually thought the extra 64MB was for Opera.

Rory
[Touch Diamond, MDA Compact IV ROM Development] KukurikU:
are you kidding?! she?! finally, saying "i can kiss you if you'll be here" can be said without sounding kinky....
[Touch Diamond, MDA Compact IV ROM Development] TML1504:
i apologize for the opera statement, but as i said i remembered to read

it somewhere else. now i've rediscovered that site:

http://www.mobiletechreview.com/phones/HTC-Touch-Diamond.htm

"Of the phone's 192 megs of total RAM, 64 are set aside

for special use, and one of these is Opera which needs lots

of memory. Yet the app, even after quitting completely,

leaves us with a seemingly confused and sluggish

Diamond."

this sounded at least possible for me, but again:

sorry if i brought confusion into xda because of that!

and for me to blame, they wrote "and one of these...".

i cited it wrong as if the whole 64mb are for opera...
[Touch Diamond, MDA Compact IV ROM Development] KukurikU:
apologies accepted:D don't worry not going to return my diamond over this hehehe..
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
well it is confirmed, SMI (that shared ram) is 64MB on diamonds.

I don't know yet what HTC needs the extra 32MB for, they allocated some heaps on it for things, is all I know so far.

otherwise this RAM is used for SPL, radio, and some hardware such as USB stack, this is not diamond specific, all MSM7xxx devices are like that.

and yes I think it is very likely the 192MB is just marketing. ;)
[Touch Diamond, MDA Compact IV ROM Development] ruffruff:
oh well ... that sucks ...

htc cheating on the end users as usual ...

192 MB of ram but not much are left usable ... feels like the old days where I have to keep tapping reclaim-memory every now and then ... :p
[Touch Diamond, MDA Compact IV ROM Development] dpduser:
Just my two cents...

Keep in mind that the MSM72XX processor that powers the Diamond and Kaiser (and others) is a dual core processor. The main core is an ARMV11 processor running the main Windows Mobile operating system (400MHz on Kaiser, 500+ on Diamond). The other core is an ARMV9 processor running at a somewhat lower speed (266MHz if I am not much mistaken) and is used to handle the radio protocols. This other core is running a Linux derivative and, of course, needs RAM to do so.

So, as both OSes are running concurrently, the main WM OS uses the lower 128MB of RAM while the linux OS runs on the top 64 - I guess some shared memory areas are required to handle the "inter-OS" communications as well.

BTW, someone posted something regarding this some time ago on xda:

http://xdaforums.com/showpost.php?p=1476164&postcount=9

Besides that, I find 64MB somewhat excessive to run a linux OS to handle a radio stack...
[Touch Diamond, MDA Compact IV ROM Development] cheetah2k:
How much Ram is left if you turn TF3D off? :confused:

Well, with it off and freshly rebooted, I have 48% used.

so on avg, 10% of the available RAM is used on just that... crazy.
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
yeah, that's correct, the radio image is even in the elf format... what's more, the ARM9 controls the ARM11 via the radio bootloader

anyway, update on original topic... I just noticed pmemmap reports:

v85e00000-87e00000 -> p02000000-04000000 2000000

this is an extra 64MB mapped. this is not present on the polaris I checked now.

it is possible that this is what HTC is marketing as extra ram. the heaps I mentioned are allocated to this RAM space.

note, this is still not program ram and is not reported in the memory applet; the OS cannot access this to allocate memory for the usual running program.

BTW, the shared radio ram is at 0-02000000.
[Touch Diamond, MDA Compact IV ROM Development] cr2:
Isn't 0x2000000 32MB ? Somebody having diamond can dump this area

so we can check its contents.

http://wiki.xda-developers.com/index.php?pagename=DiamondMemoryMap

The actual SRAM usage depends on the device. Titan/Kaiser/Diamond use it differently,

but the IPC SRAM buffer is always 1MB starting at 0x01f00000
[Touch Diamond, MDA Compact IV ROM Development] cina:
Hi!

I'm a self made programmer and I don't want to mislead anyone. I had several PDA-s from Dell Axim X3 trough ETEN M600 and now this diamondic Diamond. Love it. Each with different OS-es.

As far as I can remember each specification written the total amount of RAMs as a sum of storage and program memory (which is 113.07 + 84.69 = 197,76 with Diamond)

In WM2002 and WM2003 we were able to dinamically resize these values as all storage memory was setup in RAM and that is why these devices needed backup battery. With WM5 backup battery was not needed as storage memory was converted to a flash like memory (I don't know these type of physical devices, sorry) which keeps its data without power and program memory stayed in RAM. So the possibility of dinamic reallocation went away. So these specs probably shows the sum of storage and program memory. I know that storage is not RAM but proably they kept the specs like that just to follow conventions?

Hope that helped.

Cina.
[Touch Diamond, MDA Compact IV ROM Development] mr_Ray:
No no no no no no no no no no no no no!

NO!!!

N O ! ! ! !
[Touch Diamond, MDA Compact IV ROM Development] teammee:
YES... indeed... you are misleading everyone with that info... and it's not helping at all...
[Touch Diamond, MDA Compact IV ROM Development] JKingDev:
I absolutely love the quality and level of sarcasm served by members of this board. Thank you for making my day. :)
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
wow, where was my mind when I was looking at pmemmap? (I used my diamond to dump the map)??? :D

I am sorry, you are right, that's just 32MB.

so back to my original observations (see post #17 and post #25). if diamond has 192MB, then kaiser and polaris would have 160MB! stupid marketing!

as for IPC, yeah, diamond still has it at 0x01f00000. though USB stack needs to be at a fixed location too at around 0x80000.

you got any idea what the heaps allocated to the extra 32MB are used for ? I'm going to look into that next.
[Touch Diamond, MDA Compact IV ROM Development] cina:
In ETEN M600 Specs it says that it has 128MB RAM and the device shows 73.38MB Storage and 48.21MB Program memory. So what? That's the fact.
[Touch Diamond, MDA Compact IV ROM Development] teammee:
ETEN M600 has 128MB ROM + 64MB RAM.. look here: ETEN M600 SPEC

73.38MB is the available space in ROM after you put all the files there (OS + applications + CABS from EXTROM)..

48.21MB is the available space in RAM, 64MB minus around 15MB for WM OS...

ROM and RAM are totally different things!

what people discussing in here is about RAM... that in the spec it says Diamond has 192MB RAM, but actually only 128MB can be accessed by user...

Please don't argue about something that you don't really know about...
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
not fact, coincidence.