Database Develop

Remote Wipe Vulnerability

Hi Guys, the browser hack that wipes Samsung phones is not limited to just those handsets. These guys do a better job of describing the whole thing:
http://www.theverge.com/2012/9/26/3412432/samsung-touchwiz-remote-wipe-vulnerability-android-dialer
Here is a direct link to the exploit test:
http://dylanreeve.com/phone.php
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Maybe people can post D3 Roms that aren't vulnerable.

majatt said:
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Click to expand...
Click to collapse
Also, installing DialerOne and making it the default will protect you as well - you do not have to leave it without a default dialer set. DialerOne is actually a good dialer - I used to use it with my Droid Eris with CyanogenMod ROMs, in order to have the dial by name function that the Sense dialer supported back. And you can still leave the stock dialer set in a home page or on the launcher dock - it will still work if you call it up. It will not be called up if you launch the dialer from another app, though, if you make DialerOne the default.
The stock dialer is vulnerable - a predictable result, based on the vulnerability of MavRom, but I did want to say that I tested it. I haven't tested any other ROM - at this point, I don't have much time to try some out, and I think I recently deleted my most recent Liberty and Bionic Nandroid backups.
Let's see how long before Moto releases a critical patch update for stock.

Thanks, this is good to know. I thought it was only Samsung phones that had the issue, but since I'm still on stock 2.3.4 it appears I'm vulnerable. I have GrooveIP Lite installed on my phone, an app that allows you to make voice calls with using your Google Voice number. With this app installed I get a complete action using Dialer or GrooveIP window so I should be safe if I get a random popup Ill be sure to not select Dialer.

I heard about this "wipe" problem and when I saw it was just passing dialer codes to the fone I knew it would affect more than just Samsung.
Does anyone know if they have a list started of fones that might be vulnerable?

I read somewhere (though haven't tested it...) that the D3 does not have a dialer code that resets the phone, as the Samsung phones do/did. So, the D3 fails the display the IMEI test, but I believe that the reset code does not work with the D3.

FYI: CM10 kexec isn't vulnerable. Probably b/c it's JB (I think they fixed the vulnerability in JB). I go to the site and dialer pops up w/ *#06# No IMEI displayed
Sent from my AOKP JB GT-P3113 using Tapatalk

10.1V : 4.2 release to AOSP : any chance for us ?[Some progress already]

http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:

DannyBiker said:
http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:
Click to expand...
Click to collapse
I dont think that 4.2 is going to be CM11. Its still Jelly bean after all. I think that our only hope is that its as simple as updating the sources used to compile CM10. Then theoretically it should just slot right in there, the way that 4.1.2 did (although I dont know the actual required work in getting our device from 4.1.1 to 4.1.2), and then hopefully Pershoot could just run a new experimental build for us. Im loving his last CM10 experimental by the way. I dont seem to be having any of the previously mentioned issues.
However, with the age of our device getting closer to two years, Pershoot has been a godsend (along with isimobile and also Seo's coding work previously), but I couldnt ask him to move onto the hassles of a whole new version for us, especially if its not a simple change.

Yeah, if updating to 4.2 would ask too much work, at least to get a stable release, I wouldn't mind that all the effort are focused on bringing a final 4.1 rom for the tab and end development for it. If 4.2 is possible, that'd be great but I guess it would be the last version for us.
All in all, we won't ever be grateful enough for what you do for us pershoot. I know you don't want donations, so I'll just donate to CM instead...

4.2 has changes in Surface Flinger to support multiple screens. I made quick build for P3 and out of the box 4.2 is not compatible with current Nvidia binaries, surface flinger hangs at "create window surface". So unless we can mend 4.2 surface flinger to work with ICS nvidia binaries, this could be end of the road for Tegra 2 devices. Since Google ditched Xoom, hope is even smaller... Other option would be port 4.1.2 Surface Flinger to 4.2....could be useful for other devices though...

Well I just hope then we'll be able to implement some content of 4.2 like the lockscreen, the timer app or the multi-account feature...:good:

with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance .... it crashed later on in multimedia though, so still plenty of work.
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...

Any idea on how simple users like me can help beside beta-testing when the time will come ? Are there devices that we might need to check out as they may help us with this port ?
Thanks !
EDIT : also, I imagine that after some point, you'll share your work with pershoot.

OndraOrg said:
with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance
Click to expand...
Click to collapse
Can you tell me what you've changed?
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...
Click to expand...
Click to collapse
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.

C-o-M said:
Can you tell me what you've changed?
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Now problem is in Audio flinger, which is another component quite modified, it makes some calls to audio_policy.tegra.so with ilegal parameters. So similar issue as with graphics. I commented out this call, but then Dalvik VM crashed with some weird error. Let's see when I have more time.
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.
Click to expand...
Click to collapse
Agree here. My motivation for surface flinger port was a) this effort could be useful also for other devices which were left behind for 4.2 upgrade. b) while new Surface Flinger has many changes, lot of them are related to new multi screen functionality. That could be stubbed on api level (binder interface doesn't actually have that many changes). I bet many ppl would prefer to have 4.2 functionality, and loose HDMI functionality.
Problem I can see is that we don't know how many components we would need to port like this. Seeing now crashes in Audio Flinger, this can be lot bigger issues. There is new bluetooth stack in 4.2, replacing Bluez. If those close code binaries are using Bluez and same api does not exist in 4.2, we're in trouble.

OndraOrg said:
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Click to expand...
Click to collapse
Thanks. I'll try do redo that.

C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Let me know if it works for you, or I can share code...

C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all

OndraOrg said:
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all
Click to expand...
Click to collapse
That's awesome. Do you have a diff for me? Or even a git?

Slightly edited the title as you started messing around with it, although we all know it's just "to see where's it going" for now...

C-o-M said:
That's awesome. Do you have a diff for me? Or even a git?
Click to expand...
Click to collapse
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.

OndraOrg, I think you need to read a bit about 4.2 : Tablet UI is gone, Phone UI has been pushed to all Android devices.
See this : http://www.androidpolice.com/2012/1...just-like-a-giant-phones-and-thats-fantastic/

OndraOrg said:
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.
Click to expand...
Click to collapse
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.

C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
OK I will clean code and get you diffs.

C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries

OndraOrg said:
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries
Click to expand...
Click to collapse
Nice. Thought it was more to change.

[Q] Change CM10.1 to work in Tablet mode

Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:

karlis1989 said:
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
Click to expand...
Click to collapse
The reason why it is that way is because there are 4G models of the DS7

giveen said:
The reason why it is that way is because there are 4G models of the DS7
Click to expand...
Click to collapse
Understandable, but since I have a Wi-Fi only version I wanted to know if It's possible to change this in form of a setting or a few lines inside a configuration file without involving compiling. I even faintly remember stumbling upon something like this on a CM9 version I had on my old Xperia MT15i Neo ... if only I could remember or find where or how (currently strolling through the developer and CM10 related menus) - deleted my Xperia related bookmarks when I sold it.
p.s. - people mentioned some problems with the on-screen keyboard disappearing as described in one of the posts on the main CM10.1 thread, I've noticed them myself too and they tend to be application specific ... it feels like the keyboard crashes or force-closes due to not enough memory, like in lighter applications the keyboard works fine, but when trying to use the keyboard for writing for example a post in the comments section in a website will most likely result in keyboard disappearing after first input character.

So I am still trying to figure out why you started a new thread about this and what your question is.
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.

I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out:
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
Click to expand...
Click to collapse
... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.

karlis1989 said:
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out: ... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
Click to expand...
Click to collapse
I make it my special concern to answer questions, even if it with sarcasm
I'm not sure what more you can do besides deleting the phone. Comment out in build.prop the rild stuff

I wonder if he is referring to TabUI? Which I as well am trying to relocate the flash able .zip which enabled this display difference. I have been running cm10.1 2/12 because of the sensors not working on the 2/14 build.
Sorry to piggyback the thread, but is there an answer for where the tab ui .zip is for the 2/12 build?
Sent from my Galaxy Nexus using xda premium

Radio (3G) works better on OmniROM 4.4.4 than on my stock 4.1.2 - WHY??

Hello,
I recently installed OmniROM, but I missed the assistive cursor/pointer that is shown on the screen, so I can see where the "logical" pen tip actually touches.
So I'm back to the stock JB 4.1.2 ZTO - Brazil for a second round. I disabled most -- if not all -- bloatware and replaced TouchWiz launch screen with Google Now. I also installed Greenify, SetCPU and Xposed to trigger some actions or prevent Facebook from loading on startup.
Now, my only problem is the way the stock 4.1.2 handles 3G/HSDPA requests. On Facebook and in the built-in browser (which is basically an outdated version of AOSP browser) I constantly get timeouts, and the 3G becomes almost unusable -- except in near perfect conditions.
My question, in short is: how can I get the AOSP radio management flashed into my JB stock ROM? Is it possible? Are there workarounds?
Thanks in advance!

[Q] Could the Remix OS be ported to Droid 4 for use with a Lapdock?

Hi,
I just discovered Remix OS on Kickstarter, which sounds like an improved version of Webtop. Based on Android 4.4.2, with a Taskbar and improved multi tasking where you can switch through apps like with Alt-Tab and show tiles of running apps on the desktop. That actually sounds great for the use of a Lapdock, which I just recently got.
Now the developers offer it for a pledge of only 1 dollar and I'm thinking about pledging, but only the Nexus 9 and 10 are officially supported.
So that got me thinking, if I buy the ROM for 1 dollar, there should be a way to customize it to run with our Droid 4, right? Does anyone know how to do that or could help/teach me how to do it?
Just asking, if anyone else too thinks that this could be an interesting addition to an existing Lapdock. Now that I got CM12 running on the safe slot, the rom slot 1 would be free to test it there.
For those interested in the OS, here is a video, because the kickstarter site seems to focus more on their tablet.
Best regards and thanks in advance!

Probably not, probably android have bug and thats why lapdock doesnt work very well
Fervi

ferviverus said:
Probably not, probably android have bug and thats why lapdock doesnt work very well
Fervi
Click to expand...
Click to collapse
Which bug are you referring to?
The Lapdock 500 works fine for me, I just boot to stock slot and then Webtop activates itself automatically.

On stock it works perfect (but Remix OS is not stock)
But if you want use any other system or phone with Android - it doesn't work propertly (it works, but you have only part of your screen)
http://www.android-hilfe.de/attachm...pdock-fuer-rdh-2013-01-23_16-19-31_296_cr.jpg
Like that
And if you connect for example - Samsung Galaxy Note 2 - you still have it
But if you connect for example - computer, console or Miracast - you have full working screen
https://robpol86.com/lapdock/Atrix-Lapdock-with-a-Laptop/
I think it is a Android bug
Fervi

Why should it be a bug in Android? It works with the stock ROM, which is Android 4.1 or so. Clearly it's not a bug but something special Motorola put into that ROM, which prevents it from running if it's missing. Or maybe it just doesn't work for more recent Android version because something changed or was removed in those versions.
For non-Android-devices like a Rasberry Pi: Of course those work, because if you break it down, it's just an hdmi screen, usb keyboard and usb mouse. Those things have standard drivers in windows and linux, that's why they work.
Now this standard drivers also exist for Android, so my guess is, that Motorola somehow blocked it, but apparently people got it to work with a Samsung Galaxy S3, so it can't be an Android bug.

So maybe it is protected for Android devices, but all other (Miracast, Windows, Linux etc) works
But remember - Android have forked Linux kernel and on Linux it is working, so it is very "interesting"
Fervi

I think the problem is, only motorola and the HDMI driver on webtop is able to output a resolution different from the phone screen. CM12 for example is able to mirror the screen just fine, but only in native resolution to the phone (960x540). It would require specific software for this phone to get a different output resolution, kinda like re-writing Webtop.
Its not impossible, but I dont think its easy either, and I have no idea on how to do it.

It is possible to change resolution in phone from 960x540 to 1366x768
But you cannot resize Android on fullscreen
http://www.android-hilfe.de/attachm...pdock-fuer-rdh-2013-01-23_16-19-31_296_cr.jpg
Only stock rom do that
Fervi