yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 Development and Hacking] jessenic:
Thanks spalvin. I created a branch of HaRET that does not need a GUI at all. Here's the link: https://github.com/jessenic/HaRET-WP7/tree/nogui

Feel free to fork and play with it!

Edit: I tried to make a driver, but I have no idea how to compile it... But I committed it right here: https://github.com/jessenic/HaRET-WP7/tree/driver
[Windows Phone 7 Development and Hacking] spavlin:
compillle no gui :

src/wince/haret.cpp: In function 'int main()':

src/wince/haret.cpp:45: warning: passing NULL to non-pointer argument 4 of 'int MessageBoxW(HWND__*, const WCHAR*, const WCHAR*, UINT)'

src/wince/haret.cpp: At global scope:

src/wince/haret.cpp:102: warning: 'bool try_linboot()' defined but not used

compile drive :

Compiling (armv4) out/version.cpp

Checking for relocations

Linking out/haret-debug (Version "pre-0.5.3-20120430_180128")

/opt/mingw32ce/lib/gcc/arm-mingw32ce/4.1.0/../../../../arm-mingw32ce/lib/libmingw32.a(winmain_ce.o): In function `WinMain':

/usr/src/rpm/BUILD/cegcc-mingw32ce-0.55/src/mingw/winmain_ce.c:151: undefined reference to `main'

collect2: ld returned 1 exit status

make: *** [out/haret-debug] Error 1
[Windows Phone 7 Development and Hacking] Jaxbot:
What are you doing to compile the driver?
[Windows Phone 7 Development and Hacking] jessenic:
Yeah those warnings are ok in nogui branch, easy to fix too if you want to. But to compile the driver you need to edit the makefile and do some stuff I don't know about. Spent last night trying to figure out :S
[Windows Phone 7 Development and Hacking] spavlin:
Dear GoodDayToDie

something similar by a principle :

http://stackoverflow.com/questions/4001209/net-cf-msmq-activatedevice-crash

how you plan realization kmode, In haret or external exe, dll ?

---------- Post added at 08:45 PM ---------- Previous post was at 08:19 PM ----------

HARET = GoodDayToDie + jessenic + Jaxbot

http://www.eminsenay.com/blog/category/wince-tutorial/architecture.html

http://www.eminsenay.com/blog/category/wince-tutorial/

http://msdn.microsoft.com/en-us/library/ee478797(v=winembedded.60).aspx

http://msdn.microsoft.com/en-us/library/ee482849(v=winembedded.60).aspx

http://discovertheexperience.blogspot.com/2010/08/kernel-mode-and-user-mode-dlls.html

http://msdn.microsoft.com/en-us/library/ee482741(v=winembedded.60).aspx

http://msdn.microsoft.com/en-US/library/ee482873(v=winembedded.60).aspx

http://msdn.microsoft.com/en-US/library/ee483148(v=winembedded.60).aspx

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

http://msdn.microsoft.com/en-US/library/ee483054(v=winembedded.60).aspx

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

VS2010 does not support Windows CE development. If you want to develop a Windows CE kernel driver you need Platform Builder for Windows Embedded CE 6.0 or for Windows Embedded compact 7, according to the OS you're targetting. Those development environments are based on VS2005 and VS2008 respectivelyhttp://msdn.microsoft.com/en-us/library/ee479037(v=winembedded.60).aspx

http://www.tech-archive.net/Archive...ic.windowsce.platbuilder/2008-07/threads.html

- if you want it loaded in kernel mode just

add "K" flag to the *.bib entry for the driver DLL.

mydriver.dll $(releasedir)\mydriver.dll NK SHK

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

MEMORY

--------

http://www.pocketpcjunkies.com/Uwe/...ccessing-physically-contiguous-memory-in-user

CreateFileMapping

http://msdn.microsoft.com/en-us/library/aa914748.aspx
[Windows Phone 7 Development and Hacking] spavlin:
Memory Mapping thru OALIOCTL.dll

Date: Fri, 25 May 2007 06:20:02 -0700

#define PAGE_SIZE 0x1000

#define ALIGNMENT_MASK (PAGE_SIZE-1)

PVOID VirtualAllocCopy(unsigned size,char *str,PVOID pVirtualAddress)

{

PVOID ptr;

unsigned offset;

offset = (unsigned)pVirtualAddress & ALIGNMENT_MASK;

size +=offset ? PAGE_SIZE : 0;

ptr = VirtualAlloc(0,size,MEM_RESERVE,PAGE_NOACCESS);

if (ptr == NULL)

{

ERRORMSG(1,(TEXT("VirtualAlloc failed! %s : size=0x%x,

(0x%x)\r\n"),str,size,GetLastError()));

return(0);

}

if (!VirtualCopy((PVOID)ptr,(PVOID)((unsigned)pVirtualAddress -

offset),size,PAGE_READWRITE|PAGE_NOCACHE))

{

ERRORMSG(1,(TEXT("VirtualCopy failed! %s : addr=0x%x,

offset=0x%x(0x%x)\r\n"),str,(unsigned)pVirtualAddress,offset,GetLastError()));

return(0);

}

return((PVOID)((PBYTE)ptr+offset));

}

PVOID VirtualAllocCopyPhysical(unsigned size, char *str, PVOID

pPhysicalAddress)

{

PVOID ptr;

unsigned offset;

offset = (unsigned)pPhysicalAddress & ALIGNMENT_MASK;

size +=offset ? PAGE_SIZE : 0;

ptr = VirtualAlloc(0, size, MEM_RESERVE, PAGE_NOACCESS);

if (ptr == NULL)

{

ERRORMSG(1,(TEXT("VirtualAllocCopyPhysical failed! %s : size=0x%x,

(0x%x)\r\n"),str,size,GetLastError()));

return(0);

}

if (!VirtualCopy((PVOID)ptr, (PVOID)(((unsigned)pPhysicalAddress -

offset) >> 8), size, PAGE_PHYSICAL | PAGE_READWRITE | PAGE_NOCACHE))

{

ERRORMSG(1,(TEXT("VirtualCopyCopyPhysical failed! %s : addr=0x%x,

offset=0x%x(0x%x)\r\n"),str,(unsigned)pPhysicalAddress,offset,GetLastError()));

return(0);

}

return((PVOID)((PBYTE)ptr+offset));

}

"WinCE_Coder" wrote:

Has anyone tried mapping physical memory from an User App using the

OALIOCTL.dll approach as suggested in one of the WinCE Team base blogs.

We are trying to get the physical to virtual mapping done thru OALIOCTL.dll.

We have done the following:

1. Updated the OALIOCTL.cpp source and header files for new custom IOCTL

codes.

2. Updated our OALLIB's IoctlTab.h and ioctl.c to support the new IOCTL.

3. Calling VirtualAlloc and VirtualCopy in the new IOCTL Handler.

We see that when this IOCTL is called from a User App through

KernelIoControl, the control comes to the new OAL IOCTL and able to perform

VirtualAlloc(). But VirtualCopy fails.
[Windows Phone 7 Development and Hacking] spavlin:
/WINCE600/PLATFORM/GumstixII/Src/OAL/OALIOCTL

https://gumstix.svn.codeplex.com/svn/WINCE600/PLATFORM/GumstixII/Src/OAL/OALIOCTL/

// Add platform specific IOCTL codes.

case IOCTL_HAL_PHYADR:

case IOCTL_HAL_FCS:

case IOCTL_HAL_BOOTLOADER_VER:

case IOCTL_HAL_HARDWARE_CNFG:

case IOCTL_HAL_TRANSLATE_IRQ:

case IOCTL_HAL_GET_REG_CLK_EN:

case IOCTL_HAL_GET_DBG_DATA_BUF:

case IOCTL_HAL_GET_RTC:

case IOCTL_HAL_REQUEST_SYSINTR:

case IOCTL_HAL_GET_OEMVALUE:

case IOCTL_HAL_LED :
[Windows Phone 7 Development and Hacking] Leapo:
Not sure if this is entirely to the point of this thread, but it might be of interest.

These guys have ported Android to C#, which might make it possible to run directly on top of Windows Phone 7.
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Ported C# to Android is more accurate, actually. Android is an operating system written mostly in C; porting it to C# would be... impractical.

The problem is the difference between the framework support. WP7 supports a subset of the normal .NET framework, plus a subset of the Silverlight framework (which is built on .NET but is not "part of it" really), plus some (most?) of XNA. Mono for Android, or the Dalvik-to-Mono conversion layer, is not going to support that same set of APIs.

Still, it has a little bit of potential. I'd though briefly about trying to start a project like that (an Android compatibility layer on WP7) but concluded it was an excessive effort.

In any case, this is not applicable to the thread, no.
[Windows Phone 7 Development and Hacking] Leapo:
Again, not sure if the goal here is to actually boot into a Linux environment, or if simply loading Android (through alternative means) is acceptable, but here's some clarification as to what i was suggesting above...

You're thinking of the normal Mono project, which allows C# apps to be written for Android.

This is something else entirely, they've effectively forked Android and made their own OS. They completely removed Dalvik / Java and replaced it with Mono / C#. In order to do that, every single part of Android that was written in Java was translated to C# by running the Java code through their tool called "Sharpen"

All of the Java apps and UI that sit on top of Linux and actually make android into what we recognize as "Android" are now sitting in their repository, already translated to C#. It's quite possible to run that code on top of desktop Windows right now, effectively giving you a "hosted" version of Android. Yes, the Linux backend is mostly written in C, but the UI/apps don't need the Linux backend, they just needs the dalvik or .net runtime. They don't care what OS is running the runtime (for the most part).

Now, I know Wp7 only supports a subset of C#, but what I was asking is if it were possible to "adjust" their code so that it's compatible with WP7, effectively doing the same thing as above and creating a "WP7 hosted" version of Android... making Android an app, effectively.

Would effectively mean you would have a Windows CE / C# based version of Android rather than the traditional Linux / java based version.
[Windows Phone 7 Development and Hacking] GoodDayToDie:
@Leapo: I meant what I said (porting C# to Android). I'm also aware of the older Mono-based project, of course.

This is getting completely off-topic for the thread, though if you want to start a new thread to discuss it, that would be cool.

Personally, I suspect it'll be fairly difficult on anything except maybe fully-unlocked phones; the Android and WP7 security models are just too different. Also, the problem isn't so much that WP7's C# support is partial, as that it's focused on areas that I don't believe this tool uses. For example, WP7 supports two different managed GUI libraries, but neither one is WinForms; the code would need to be re-written for Silverlight and XNA.

That said, maybe I'm wrong and turning Dalvik apps into Silverlight apps is a simple option to Sharpen. It's worth investigating... in another thread, please!
[Windows Phone 7 Development and Hacking] LENINred:
Running Homebrew Native Executables - Status: POSSIBLE!

Running Homebrew Native Executables - Status: POSSIBLE!
[Windows Phone 7 Development and Hacking] Jaxbot:
The problem isn't running EXEs, it's being able to make a CE driver that can allocate memory. This isn't possible, as far as we know, with Heath's latest breakthrough.
[Windows Phone 7 Development and Hacking] spavlin:
??? post #159

ioctl codes oalioctl.dll
[Windows Phone 7 Development and Hacking] spavlin:
Likely to please those who have made the firmware collects mutations both in the IOCTL codes oalioctl.dll then the process will go.
[Windows Phone 7 Development and Hacking] eusoulindo:
ID you guy News testers, please PM me...
[Windows Phone 7 Development and Hacking] spavlin:
cpu.h :

===============================================

---//---

// Get Program Status Register value

static inline uint32 cpuGetPSR(void) {

uint32 val;

asm volatile("mrs %0, cpsr" : "=r" (val));

return val;

}

---//---

===============================================

HTC 7 Mozart T8698:

HaRET(2)# show PSR

0x60000110

// ARM procesconsequentlyr modes

#define USER_MODE 0x10 // 0b10000

#define SYSTEM_MODE 0x1f // 0b11111

CPSR Instruction found in nk.exe (S000) :

View attachment 1271903
[Windows Phone 7 Development and Hacking] spavlin:
View attachment 1277986
[Windows Phone 7 Development and Hacking] ONDR4SH3K:
It's very sad with this topic. spavlin has try to help and nobody don't reply back.

spavlin very good work. I hope you will continue with progress.
[Windows Phone 7 Development and Hacking] jessenic:
How is it sad? Spalvin is the only one that knows something. I do not comment because I have no idea about Windows CE kernel and how it works etc. Big thanks to spalvin, he really seems to be the only one who knows something that might be useful, but we still need someone who can turn that into code :P
[Windows Phone 7 Development and Hacking] metroidnemesis13:
Perhaps it would be best to postpone this project until the release of Windows Phone 8, since it has a new kernel and different Windows CE backend. Maybe there will be more exploits available for unlocking our WP8 devices, so stuff like this can reach a wider audience.
[Windows Phone 7 Development and Hacking] link68759:
Maybe, but maybe not. There's no point in speculating right now. All current phones will not receive WP8, unless by custom ROM, so this is still a worthwhile endeavor.
[Windows Phone 7 Development and Hacking] link68759:
http://www.wpcentral.com/microsoft-beefing-security-windows-phone-8

If we need any more incentive to get the most out of our WP7 devices.
[Windows Phone 7 Development and Hacking] spavlin:
HaRET(15)# SHOW MACHMTYPE

0x00000dd8

HaRET(16)# SHOW PHYSMAPMETHOD

0x00000001

HaRET(17)# SHOW GPIOS

0: 0x00000000 00000000 32 last

1: 0x00000000 00000000 32 last

2: 0x00000000 00000000 32 last

3: 0x00000000 00000000 32 last

4: 0x00000000 00000000 32 last

5: 0x00000000 00000000 32 last

6: 0x00000000 00000000 32 last

7: 0x00000000 00000000 32 last

8: 0x00000000 00000000 32 last

9: 0x00000000 00000000 32 last

10: 0x00000000 00000000 32 last

11: 0x00000000 00000000 32 last

12: 0x00000000 00000000 32 last

13: 0x00000000 00000000 32 last

14: 0x00000000 00000000 32 last

15: 0x00000000 00000000 32 last

16: 0x00000000 00000000 32 last

17: 0x00000000 00000000 32 last

18: 0x00000000 00000000 32 last

19: 0x00000000 00000000 32 last

20: 0x00000000 00000000 32 last

21: 0x00000000 00000000 32 last

22: 0x00000000 00000000 32 last

23: 0x00000000 00000000 32 last

HaRET(18)# SHOW IRQS

0: 0x00000000 00000100 32 0

1: 0x00000000 00000000 32 0

HaRET(19)# SHOW MMUMERGESTART

0x00000000

HaRET(20)# SHOW MMUMERGECOUNT

0x00000000

HaRET(21)# SHOW MMUMERGETARGETSTART

0x40000000

HaRET(22)# SHOW MMUMERGETARGETSIZE

0x10000000

HaRET(23)# SHOW ALTL1TRACE

0xe1100000

HaRET(24)# SHOW MAXL1TRACE

0x00000000

HaRET(25)# SHOW PERMISSIVEMMUTRACE

0x00000000
[Windows Phone 7 Development and Hacking] Kr3i0s:
Hi spavlin, first of all thanks for all the hard work that you are doing. I hope we will get android running on our Wp7's eventually.

I wanted to know if you are using the same Haret version that was last compiled by jessnic or your own compiled version.

If any testing is required count me in.
[Windows Phone 7 Development and Hacking] BigJeff:
Yeah I porked the screen on my Focus S so I am willing to test as well. Hope the ball keeps movin on these projects.
[Samsung Galaxy Nexus] mobilehavoc:
I haven't put screen protectors on any phone in the last 2 years because I've never needed them. I handle with care and the phone is the only thing ever in a pocket.

Today I noticed on my GSM Nexus that there are light vertical scratches from the bottom of the screen. It reminds me a lot of the swirls/scratches you see on cars after a few washes. Head on and in daily use I don't see them but under a bright light or sun its very easy to see.

I'm not an idiot and obviously I somehow caused these scratches but what the hell could I have done to cause scratches all over fortified glass? Seems very suspicious and maybe Gorilla glass is much better.

It looks like I've been Samsunged.
[Samsung Galaxy Nexus] zehkaiser:
It is possible that Gorilla Glass may have saved your phone in this case, but I have the exact scratches on my Droid X with GG. Also my Xoom. I ended up with screen protectors on them for this reason. Nothing is impossible to scratch. And once they get tiny scratches like that they are more susceptible to more.
[Samsung Galaxy Nexus] mobilehavoc:
I never had any issues on my HTC Incredible and Sensation both which use Gorilla glass but this phone after only 2 months its crazy there are scratches. Happened over this weekend. Only thing I can think of is sliding it in and out of my jeans. That's really it. No drops or no trips to beach. Its just bizarre.
[Samsung Galaxy Nexus] omersak:
It's 'like' gorilla glass perhaps, but nowhere near as effective. Gorilla glass my not be bullet-proof or 100% scratch resistant but i find it's much, much better as resisting scratches as compared to a normal screen

I first found this out after i traded in the SGS1 for the Nexus S - never used a screen protector for the gorilla glass of the SGS1 and my nexus S screen scratched within a couple of weeks. Had to use a screen protector.

Had a SGS2 and Sensation for a few months - never used a screen protector yet not a single scratch.

The iphone 4/4s with their 'fortified/hardened' glasses are even worse.

Needless to say that the first thing i did to my GN when i got it was apply a screen protector on it. Peace of mind.
[Samsung Galaxy Nexus] lilirose:
Samsung is not advertising the glass on the Gnex as being "like" GG...I think Corning, makers of GG, would object strongly if Samsung did any such thing. If someone in a phone shop told you that, you really can't blame Samsung for it.

The Gnex doesn't have gorilla glass because the Gnex screen has a curve and GG is flat. To be honest, I've never seen advertising from Samsung that mentions the strength or durability of the glass on the Gnex at all, but I probably haven't seen every single Gnex ad that exists.

I got a scratch on my Gnex and then I got a screen protector. I was disappointed when I got a scratch, since I used my SGS "naked" and never had any damage to the screen. But I'm not so upset that I feel like I got ripped off.
[Samsung Galaxy Nexus] matt30:
Dinc didn't use gorilla glass but it was fortified glass and it didn't get a scratch in the 2 years I had it. I just have to remember to be more careful with my gnex.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mobilehavoc:
What's weird is my scratches seem to be more to the screen's coating?? than to the glass? As in you see them if you face the phone top down but at an angle you can't see them. Almost reminds me of what scratches on a screen protector look like. It has no impact at all on the display when the screen is on or when there's not a bright overhead light. Even with a bright overhead light I have to look at the screen straight on so is it possible it's a scratch in whatever coating they use? Running my fingers doesn't feel anything either.
[Samsung Galaxy Nexus] lilirose:
Weird. My scratch can easily be felt if you run a fingernail over it- or, at least, you could before I put on an XOskin (not meaning to spam on their behalf, but their screen protector fills existing scratches well). I didn't have any microscratches like you describe at all, and I think I'd be pissed about that too. Possibly a defective phone? Or a refurb that has a cheap screen protector on it?
[Samsung Galaxy Nexus] matt30:
I have the same thing. Very strange.

Edit: I can't feel my scratch with a fingernail either.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mobilehavoc:
I REFUSE to put a screen protector on, it's BS that we have to do that. I just added insurance so worst case if it gets much worse I'll pay the deductible and get a replacement. I absolutely hate screen protectors with a passion...last time I used one was on a Palm Pre and then a Hero. These beautiful phones and glass is meant to be felt by your fingertips - it's a whole different experience when you touch glass or plastic IMHO.
[Samsung Galaxy Nexus] tigajr:
Same here, I refuse to put a screen protector.

I am happy with the Samsung "fortified" glass. I have been using my GN every single day in my pocket and I have yet to see a single scratch!
[Samsung Galaxy Nexus] Stone 13:
I have a few of those tiny scratches on my Nexus. Not really noticeable unless I really look for them so I'm not terribly bothered.
[Samsung Galaxy Nexus] lilirose:
You refuse to use a screen protector, I refuse to walk around with a €600 phone that has a scratched-up screen. Different strokes for different folks.

I look at it as being no different to using a condom...not perfect, but a heck of a lot better than the alternative. ;-)
[Samsung Galaxy Nexus] RogerPodacter:
the scratches surely are not on the glass but on the coating which is applied to the glass.
[Samsung Galaxy Nexus] [hfm]:
Ditto. Since late Nov its naked in my pocket every day. Looks mint at any angle.
[Samsung Galaxy Nexus] @rbiter:
Rain X anyone? In my Grey poupon voice.

Sent from my Nexus in Texas.
[Samsung Galaxy Nexus] finch8423:
You should try Zagg. I'm serious, it doesn't interfere with the screen, and it absolutely works. Gorillia glass is tempered, meaning it's stronger than regular glass, just like a car windshield. That being said, it will eventually scratch if the conditions are right. Believe it or not, dust that settles on the glass will cause minor abrasions- couple that with being inside a pocket, it's a miracle that your phone isn't worse off.

I mean, the screen won't get scratched, and considering you have $600+ phone, I think the $12 on ebay is worth it. I'll tell you right now, the one made for the galaxy nexus covers the entire front, even the very bottom. Couple that with an otterbox commuter, or defender (with the built in screen protector removed) your phone will not get broken.
[Samsung Galaxy Nexus] dmmarck:
I am very, very careful with my GN. I put it in its sleeve, put the sleeve in the left pocket with nothing else, screen in. Always wipe after heavy usage.

Oh and I don't flail around with it like a freakin' kraken.

Result? No scratches! Of course, the charger port is getting a bit worn in, but hey, not my fault the battery sucks.

If Zagg is still the same tacky, orange-peeled nonsense that it was when I got my Incredible, I'd pass on that in a minute. It protects well, but the tackiness is absolutely unbearable (I played with my Dinc last night and the touch/feel was nonsense), the orange peel can be unslightly to the OCD (ala me), and it starts to yellow after a couple of years.

BUT....diff'rent strokes.
[Samsung Galaxy Nexus] aimetti:
Don't bother with wet application screen protectors. They all suck.

Get your self a brando UK ultra crystal. Can't even tell its on the phone. (And I hate screen protectors)

Takes like 14 days from Hong Kong to USA but its worth it.
[Samsung Galaxy Nexus] mobilehavoc:
I can look at it other way - it's a $700 phone (for me) so why ruin the amazing glass screen, touch response, look and feel of the device by a piece of $12 plastic?? ;)
[Samsung Galaxy Nexus] player911:
I have a XO skin on mine coupled with a Diztronic TPU case. I haven't used a case or a SP in years but this is my work phone. I had a LG G2x prior. Even with its Gorilla Glass I would get a tiny scratch on the screen occasionally. Being the G2x was a PERSONAL phone, I would just deal with it until I did a warranty swap.

But with this phone being a work phone on a corporate Verizon account, I don't know how easy the swaps will be, so I'd rather just protect it. Plus being a work phone it'll be in places most phones shouldn't be.

The XO "CAN" have a slight tacky feel that is noticeable immediately, but after a few days for it to fully dry, it smooths out. If your hands are sweaty or dirty, it sometimes can get tacky (but you just wash your hands at that point).
[Samsung Galaxy Nexus] DroidDavi:
Doesn't the nexus s have GG and that screen is curved
[Samsung Galaxy Nexus] dmmarck:
The XO is the only one I've seriously considered, but without knowing what you consider tacky and how my consideration of tacky stacks up (metaphorically, obviously) I've never pulled the trigger.

That and i'm TERRIFIED of putting on SP myself--wet or dry!
[Samsung Galaxy Nexus] gaetawoo:
like others have said, there is an OLEOPHOBIC coating on your phone. it resists oil (fingerprints) better than a non-coated screen. Notice that you can pretty much wipe it clean with a single wipe on some soft fabric (pants). The problem is that since this is a coating, it can easily be scratched leaving light whisps of scratches. the glass isn't going to scratch , the coating surely will.
[Samsung Galaxy Nexus] Azeolus:
One big thing to remember is that these screens (reinforced, hardened, etc) are all still quite vulnerable to silicates. While it might be impervious to something like a key, or a paper clip, which seem sharp to us. things like sand, or other tiny silicate particles are razorblades to these screens.

Even if it seems like just some dust, small particles of this stuff will really scratch a phone up bad. That is what you need to watch out for.