yashsingh1/xdaforums huggingface dataset:
[Windows RT Development and Hacking] southbird:
Is this true for sure? I figured especially since we have driver-level access we could possibly tear down the Windows kernel in reverse and start execution of arbitrary code. But I might have missed something.

The bigger issue about trying to port Linux to any device without official Linux support is usually in getting the kernel to boot and then making the hardware itself useful after that. This usually means you have to work "blind" and rely on some kind of low-level serial output to monitor the kernel boot to see where it panics. Only after getting a successful kernel boot can you even begin to think about drivers for the display, touch screen, etc.

So the prerequisites to even beginning to port to e.g. a Surface would be to find some way to kick out Windows and start arbitrary execution, enable some kind of low-level serial debugging for the would-be kernel, and then tediously poke and prod until it can successfully start. I'm not sure anyone knows of a dependable way to get serial debugging information.

Embedded devices on the whole are a lot more finicky and a lot less tolerant than normal PCs, generally due to their proprietary nature requiring a lot of hardware knowledge to initialize everything properly. About the only thing we'd have going for us is that it's a Tegra chipset, so if you can get the underpinnings working, you can probably at least get the basics like video and USB working without too much trouble.

I think the biggest thing about it is like the rest of RT ... there's just not enough interest in those with the skills to even attempt this because this is such an extreme minority platform. I imagine a Surface RT would make an excellent little Linux tablet, but I'm not holding my breath.
[Windows RT Development and Hacking] kitor:
Well, If somebody would write something like WinKExec, or HaRET (haret allowed to analyse gpios and memory on WinCE/WM devices) then things may be possible. I own XPS10, so quite different device (as it has Snapdragon CPU), but I have some (small) experience on porting Linux on ARM devices - some time ago I was able to get Linux working on Bsquare Maui: http://pdasite.pl/kitor/maui_linux/ (including hardware reverse engineering - tracking gpios using multimeter - this way i found hidden usb host ;) )
[Windows RT Development and Hacking] GoodDayToDie:
There's been talk of a WinKExec-like approach for months. Nobody has attempted it yet, though, or if they have they kept quiet about it.

One of the problems getting something like that working on RT is that it blocks kernel debugging, so you have to work pretty blindly. Then there's all the driver issues.
[Windows RT Development and Hacking] skiman10:
What about getting android to boot on it? There's drivers and such for tegra 3. I think its possible to build and deploy if we can get a kernel exploit. Am I wrong?
[Windows RT Development and Hacking] irony_delerium:
Android depends on Linux. If you can't get a Linux kernel booted, you won't be able to get Android to start up either.
[Windows RT Development and Hacking] GoodDayToDie:
The kernel by itself would be *relatively* easy (translation: still quite hard, but we could probably do it if people cared enough). However, getting all the other hardware (you know, things like the touchscreen, WiFi, and such) would likely be difficult, and without all that, it's pretty useless as a tablet. This is true for both Android and "desktop" Linux.
[Windows RT Development and Hacking] skiman10:
Where should I start to get a kernel to boot? I'm an android exploiter trying to dabble in Windows exploitation.
[Windows RT Development and Hacking] GoodDayToDie:
Well, unless you think you can break Secure Boot, you should start by writing/porting a way to use the NT kernel to launch the Linux kernel. That probably means a lot of NT driver development stuff (done without the aid of a kernel debugger, just for extra fun).
[Windows RT Development and Hacking] graphsys:
There's a doc on internet from the blackhat usa 2013 seems to be interesting.

The man from the pdf get the exploit of injecting some code from the boot, so i think we can done this, no ?

If anyone tried and arrive he'll get amout of money from me :)
[Windows RT Development and Hacking] skiman10:
Can you PM me the article?

---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------

I think there is an exploit for Secure Boot, it just hasn't been shared yet...
[Windows RT Development and Hacking] GoodDayToDie:
If you mean the exploit I think you mean (discovered by an XDA member), it's a Windows bug, not actually a Secure Boot bug. It doesn't actually allow booting a different OS directly, just messing with Windows after bootup. We already have the jailbreak (for 8.0), which is pretty much equivalent.
[Windows RT Development and Hacking] graphsys:
Im researching the doc i've found to provide you it.

Its not the jailbreak done by clockr ported by neman its another jailbreak who's available from the boot, but if remember they dont give sources... search in progress i'll post the link ;)
[Windows RT Development and Hacking] mamaich:
There is one theoretical way to remove secureboot on a jailbroken device. It is rather easy: write a driver that reads/writes physical RAM. Find EFI_RUNTIME_SERVICES in memory and look for SetVariable function. Patch it so that it does not check for a valid signature. Than write your own certificates to UEFI with this patched function. Profit.

I've already done the first part - wrote a driver and found the table in memory (this is really an easy part). But my device died before I was able to successfully overwrite the certificates.

As far as I know similar method was once demonstrated for an x86 UEFI, just noone made it for ARM.
[Windows RT Development and Hacking] GoodDayToDie:
That... is a rather clever option too, although I'm tempted to avoid things which require modifying the firmware (too much option for future updates to break things). Still, a good option for those of us with gen1 devices who would like to be able to upgrade without losing the jailbreak, and also a good option for those who would like to install different OS images...
[Windows RT Development and Hacking] skiman10:
Can we get in contact? I'd love to get a more detailed plan that I can try. Gen 1 Surface RT on Windows 8 RT.
[Windows RT Development and Hacking] graphsys:
One demo about bypass: youtube.com/watch?v=i9ULYwRK1iU searching again the pdf mens ;)
[Windows RT Development and Hacking] ThatGuy94:
About the only way you could possibly break secure boot is possibly by spoofing a key or potentially modify the UEFI to have secure boot disabled. While both are technically possible, you'd have to find an exploit to do it because I'm sure the UEFI probably can't be easily flashed
[Windows RT Development and Hacking] jordanmills:
if you got a device with a jtag interface left open, that should be easy enough. The problem is that EPROM "fuses" are usually burned on the SOC. The secureboot check is hardcoded check that flag. You can't alter the bootloader without invalidating its signature, and it's practically impossible to unset an EPROM fuse.
[Windows RT Development and Hacking] TFGBD:
Has anyone looked into porting CoLinux or writing a similar port of the Linux kernel to a system service? Is CoLinux hardcoded for x86?
[Windows RT Development and Hacking] kitor:
Colinux is sort of kernel, and yes - kernel has many things hardcoded for architecture. There's still no amd64 port of CoLinux and demand for it is over 9000 times bigger than for ARM, so i predict it won't happen.

Oh, and AFAIR itself it's a windows kernel driver, on 8.0 we can't use any kernel mode drivers even with jailbreak.
[Windows RT Development and Hacking] LolitaPlus:
I thought we can.

http://xdaforums.com/showthread.php?t=2179754
[Windows RT Development and Hacking] GoodDayToDie:
Yeah, drivers are fine as of the latter jailbreak versions. The original versions were for usermode only, but the tweak for kernelmode unlocking isn't much different.
[Windows RT Development and Hacking] TD68:
Tiny core Linux?

Has anyone looked into Tiny core Linux? Even the core by itself? It runs alone in system memory, and has been ported to run on arm, x86 and x64. The main intention of the os was so it could run on almost any system. It has low requirements, such as processor support, and ram. Also comes pretty installed with tons of drivers (idk if it has ones for RT)(can we copy drivers from rt?). And if it's an issue with booting from the internal storage, could we boot from the micro SD card slot? Also, it appears that Microsoft has removed the windows 8 rt recovery tool, so I'm stuck in 8.1 rt(if anyone could help me with that it'd be much appreciated).
[Windows RT Development and Hacking] NoSkypeOnCM:
With secure boot being broken, it should be possible to run a live-linux on Surface RT now, right?
[Windows RT Development and Hacking] TD68:
But someone has to recompile a version of linux to run on the rt hardware.
[Windows RT Development and Hacking] TD68:
has anyone found or created drivers for Surface RT hardware to work on Linux?
[Windows RT Development and Hacking] netham45:
This thread is two years old, and no, as soon as a working Linux build exists it will be everywhere.
[Windows RT Development and Hacking] abbey8k:
Am I right in saying, secure boot is not broken, a way to bypass it as been discovered, that's all & the reason we can't install ubuntu or other arm versions is not due to hardware but due to secure boot blocking modules from running in grub?
[Windows RT Development and Hacking] Wack0Distractor:
That's incorrect. I need to patch grub to allow it to load modules, that's all. You can chainload any unsigned .efi you want.
[Windows RT Development and Hacking] abbey8k:
Sorry for the miss information.
[Windows RT Development and Hacking] 7oh4exec:
Did we ever get anywhere with thism
[Windows RT Development and Hacking] as1x752:
I would like to help if you could point me in the right direction. :)
[Windows RT Development and Hacking] Kingmj666:
Well someone ask if they cared about the surface rt well I say I do I been trying to overwrite the boot loader and kernel but it seems that there is more policy in the scripts if you try to unblock one policy then there is another policy you have to unblock I been working on this rt of mind for about 2 months on in off and it's been driving me crazy
[Windows RT Development and Hacking] abbey8k:
I think we have to except nothing is going to drastically change
[Galaxy S 4 Q&A, Help & Troubleshooting] ZoharTelor:
http://s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html

KNOX*

I know it is shown in an S4 mini, but i was wondering if it could work on any rom? i want to try and use it on a stock rom for GT-i9500, but i'm not sure it will work and i don't want to ruin anything.

Thanks!
[Galaxy S 4 Q&A, Help & Troubleshooting] ZoharTelor:
sorry

Sorry for the link. apperntly i can't posr links yet... so just copy it to the browser.

Mod edit: hyperlink added ;)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] xelencin:
Keep in mind that flashing to a nonofficial rom voids your warranty. I am in no way responsible for any issues you may come across when attempting to update your rom. Please keep your questions about this rom in this thread, various users including myself can help you if needed. Please do not pm me with general questions about this rom or the mda, they would be better answered in the thread.

[ File Name ]

T-Mobile_RUU_Wizard_2210401_221_20710_ENG_US.exe

[ ROM Versions ]

IPL: 2.21

SPL: 2.21

OS: 2.21.4.1

GSM: 2.07.10.

[ Description ]

I was going to wait until the AKU 2.2 update was released before cooking a new rom but I've grown impatient. This is the latest os rom available and while it doesn't add anything new feature wise I have changed some other things around for the better. The first thing I did was update the rom install process to automatically attempt to CID-UNLOCK the device and because of this change I have recompiled all of my current roms with the new installer. The second thing I did was go through ALL of the T-Mobile default customizations and cropped out only what was needed; I also cleaned out all of the other cabs used during the customization process. The third thing was creating a new set of registry tweaks to my liking. In the end, on a fresh boot the device has over 40MB of storage space available and over 25mb of memory free.

If you have issues upgrading to the 2.x roms I would advise downgrading to 1.08 first and then try installing 2.x roms again.

[ Extended ROM Contents ]

Certificatin_Disable.cab - Disables certification requirement for cab installers.

Keyboard_English_US.cab - Sets the keyboard language to US English.

Missing Shortcuts.cab - Creates the MMS Messages folder, MIDlet Manager link & Voice Speed Dial link.

Registry_Tweaks_2.0.cab - Disable gprs disconnect button, disable menu animation, disable message sent notification, enable 4-way ie scrolling, enable 802.11g, enable edge icon, enable bluetooth receive, enable caps/dot keyboard indicators, enable cleartype in landscape mode, hide sim contacts, store ie cache on sd card, show time zones tab (network time update.) *Can be uninstalled.

Smart_Dialing_Enable.cab - Enables Smart Dialing.

T-Mobile_Jingle_Ring.cab - Installs and sets the ringtone to T-Jingle. *Can be uninstalled.

T-Mobile_My_E-mail.cab - Installs the T-Mobile My E-mail client. *Can be uninstalled.

T-Mobile_Network_Customizations.cab - T-Mobile GPRS/MMS/IE/OTA settings.

Total_Commander.cab - Advanced file manager and registry editor. *Can be uninstalled.

[ Download ]

You can download the latest rom update along with previous versions and more from my site:

http://xelencin.shackspace.com/wizard

You may also attempt to get them from the xda-dev ftp.

ftp://xda:xda@xda-developers.com/Uploads/Wizard/Roms/xelencin/

Enjoy!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] TauTau:
just in case I would install a english ROM (german ones are usually quite late), could I change the keyboard language?

Lars
[8125, K-JAM, P4300, MDA Vario Software Upgrading] LordPhong:
so what's so special about this ROM? Did they remove the stupid battery meter from where the date/time should be? I already like 2.17 even though the caller id doesn't show up on my BT headset as it did on my old JAM. Was it worth the upgrade?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] wireless_one:
Thanks for doing this!! I too have become anxious and would like to upgrade. I have been running the last custom rom you cooked and I have been happy with it thus far. However, as of recently I have been having the random phone resetting issue that has been discussed in various other threads.

Does your current custom rom address that issue, as well as put in the stereo BT fix?

Looking forward to doing the upgrade!! :D
[8125, K-JAM, P4300, MDA Vario Software Upgrading] j0nkatz:
Upgrade working great so far.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] aegeas:
Upgrade!

I have a sickness. I have to apply updates when they come available. It is a strange compulsion. Am I alone? I actually love doing it.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] xelencin:
I never had this issue but other users are reporting random bug fixes with this OS version so it may help.

Since I don't own a stereo bluetooth headset I didn't include it yet. It can be found on my site though under notused apps. ZokiA2DP.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ofer:
xelencin - YOU ARE THE MAN ! ! !

thanks again for all the work ... I have been using your 2.17 ROM since the day I got my T-Mobile MDA flawlessly and I just saw you released a new one - I'm going to install it right now.

keep up the good work ... (:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] aegeas:
Keyboard tweaked

Just installed this on a Qtek 9100 and now the keyboard is no longer mapping to what the silk screen on the key says it should be. Looks like there are some differences in key mappings between the MDA and the 9100. I did try switching it from USA English to UK English and then back to see if it was a Regional Setting error and there was no change. It is not huge differences, but large enough that when you are using the keyboard that you have to hunt around with the "alt" button until you find the right key you are looking for. The hyphen key now maps to the underscore when you press the alt key now- stuff like that. Will definitly want to be careful if you intend to install this on a 9100 or Kjam, I think.

Aegeas
[8125, K-JAM, P4300, MDA Vario Software Upgrading] visitingmalta:
MDA COMPACT SOFTWARE IN ENGLISH

Hi,

I need an english version software for my mda t mobile compact model.The software I have now is:

ROM 1.13.01BGER

ROM DATE 08.18.05

RADIO VERSION 1.12.00

PROTOKOLL VER 1337.42

EXTROM VER 1.13.129 GER

Does anyone know were I can get the update or eng software for it??

regards,

Visitingmalta
[8125, K-JAM, P4300, MDA Vario Software Upgrading] fmajoo:
Tmobile USA MDA

Hi,

I am new to this and have been reading the msgs on this forum for a few days now. I just got the new MDA they have available in the USA. I just DL :

T-Mobile_RUU_Wizard_2210401_221_20710_ENG_US.exe

I did not install this yet. Still am a bit confused

I know its stated that it will automaticly unlock the CID, but how about the SIM? Will it also unlock the SIM? If so I guess there is nothing else to do, as it will unlock both SIM and CID and then install the new ROM. If not how do I unlock the SIM?

Also another question I have is RING TONES!! tmo only has a handful of ring tones installed. I have some great ring tones that I have on my old phone. I want to transfer them to the MDA, but where would they be saved to on the MDA, and how would I select them?

Thank You in advance for everyones help.

FM
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gambino:
thanks for the new rom. Im a newbie here and i just used the lokowitz to unlock my o2 xda mini s.My question on this new rom is there a special way to run it or should i just copy it onto my mini s and just execute it. I already unlocked it and im using it for tmobile usa, just need to get the tmo rom. please advise.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ascssmith:
xelencin, thanks as always.. i downloaded yesterday from here. Have to wait till after plumber comes and goes before i update... :roll:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] rambo6:
Adding A2DP AVRCP

Xelecin:

Nice work as usual. I just barely flashed the 2.17. I was using the 2.8 Qtek Test ROM because of the A2DP and AVRCP. Can this be added to your ROM somehow?

Also, is it bad to flash the ROMs a few time?

Thanks in advance.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] rabmc:
just dloaded it - and gonna give it a try...

cheers!

:wink:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] nkoca:
what is the difference between the rom's you upload to ftp

I have mda vario. I want to upgrade rom but I'm not sure that I know the right rom available. xelencin upload 3 rom to ftp server of xda-developers(ftp://xda-developers.com/Uploads/Wizard/Roms/xelencin/). I don't know what is the difference so I want to learn the correct rom for my mda vario. Thank you
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mreeves791:
Do the ipl, spl, radio and os all come from O2 UK ROM? (which is the fastest base ROM I have tried).

Many Thanks

Martin
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cuboosh:
clock and battery still in same place :( wtf gives?!?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Jon_Hanson:
I installed this ROM on my Wizard. The express reason I installed it was because the wi-fi was non-functional for me on the stock T-Mobile firmware. This firmware doesn't seem to work either in the wi-fi department for me. The Wizard detects my wireless network and I'm prompted to enter a key (I use just WEP encryption). I enter the key and it never seems to connect. I have entered the key numerous times to make sure I have it right to no avail. One time it did seem to make a connection with my wireless network but quickly disconnected. There are other devices on my wireless network so I know it's working. My wireless network is just a simple Netgeat 802.11b access point. This is getting really frustrating. I'm running out of idea on what to try and was hoping for some help here.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Daddy_Spank:
Hey,

I just flashed my friends MDA with this new firmware with the 2.21 custom and everything went fine except after its done and i rebooted it, i am getting "Data Crashes. Please contact your system provider" and where the start button is, SIMlock is being displayed. Is there something obvious that i have missed or whats going on? I have the MDA too, succesfully installed 2.17 a few weeks ago. Any ideas?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gambino:
okay guys i have run the cid unlock with the lockowitz. When i execute the new tmo rom update i get the option the first dos option screen, where it gives me and option to unlock the cid or not. When i try both options nothing happens the dos screen just dissapears. Guys please advise.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] smpjungle:
No backlight

I was using the 2.17 custom TMO US ROM without any problems. Except, after several weeks, I was experiencing constant "low storage space" errors. Seems like every other day I was deleting the contents of the messaging folders and IE temp files to free up space. I flashed with this ROM, and everything seemed great, but once I disconnected from USB, I noticed that my backlight wasn't coming on. A soft-reset turned it back on, but again, once it was off, it wasn't coming back on. Strange. So I'm reflashing. We'll see if the problem continues. The only program I added (that I wasn't running on 2.17) is Smartskey. So I'm not sure if it was the ROM, Smartskey, or perhaps an odd combo of the 2. (Or perhaps it was just a freak glitch!) Just wondering if anyone else experienced the same? Another question: Instead of reflashing, I could just hard reset and it would have the same effect, right?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] sskarlatos:
See my post explaining the issue here.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] summiter:
I'm not a T-MO user, but I just wanted to give props to you xelencin..you've done a great job helping out your fellow T-MO folks.

--Summiter
[8125, K-JAM, P4300, MDA Vario Software Upgrading] samdogg:
FIRST BUGS

I have the first reported bugs for you, at least involving MY MDA.

1. First bug is, if you have a voicemail, when you select the voicemail icon on the title bar, it drops down a voicemail notification dialog box right? Well, when you click the voicemail choice on the bottom left softkey, it doesnt do anything!! It doesnt call up the voicemail or anything.....

2. Second issue is, say for example, someone gives you their number, so you write it down with the dialer program. Now, if you select "menu" in the bottom right soft key, and select "Save to contacts", it brings up the edit contacts fields, however, it only shows that page for a second, then goes away!!! This gives you NO time to add a name or anything??

The same thing happens when you right click on a number in "call history" and do "save contact"...

I tried doin a hard reset, that didnt work. I also uninstalled all the registry tweaks, but that didnt make a difference either. I think, therefore, that it must be the OS build itself.

Either way I wanted to thank you xelence for this rom, but these bugs are annoying as hell....Anyone else have the same problems??????

BTW, xelence how did you get 26 MB of memory available?!?!?! Did the 2.21 build come like that??? I dont get why 2.17 didnt have free memory like that????
[8125, K-JAM, P4300, MDA Vario Software Upgrading] alexsch8:
Upgraded my TMobile MDA today - all okay. Thank you very much!