LETS GET THIS LIST GOING!!
I know there are several threads on this allready, but finding the actual information of which roms work and which don't is very hard, so I've decided to make this thread to have a centralized place to list and discuss roms that work with the patch.
First things first:
The verizon patch and information about it can be found here. http://forum.xda-developers.com/showthread.php?t=2055218
Things to remember:
Do Not flash modems from any rom that doesn't have a Verizon Base.
Always make a backup before testing the patch with new roms.
(not sure if kernels are harmfull, or if you need to flash specific verizon kernel after flash, will update when I gather more info, for now this is a list of known working roms and how you got there.
Now the Good Stuff.
I thought since I was making this thread I would jump in and test first. here's what I have so far.
1) Ok, my first attempt wasn't so good. I installed the whompasaurus rom from the sprint forum. Device booted fine, but upon boot I got an Ecryption Failed screen with no way to go any further (to my knowledge anyway) I feel this is stll relevant to the thread. So post your experiences and I will update the op accordingly. I have seen a few roms on the at&t forum that say "no device check" therefore I assume they will work. Time will tell.
Please feel free to list roms that you have succesfully got working with the vzw patch and if you used build prop edits to achieve this as well then please be specific and I will add them to the op as they come in.​
Ive got all the DLL1 and DLL4 roms to work in the att & tmobile forums.
The caveat with Scott's patch is that it is only designed to get TW roms from other carriers working on our devices. While most TW roms will boot fine after the patch, they will more than likely require some build.prop modification to get them completely up to snuff. In the case of porting AOSP roms, the patch isn't entirely useful, save for a few vzw specific system applications, as AOSP doesn't use CSC files. AOSP porting can be done with build.prop adjustments.
Can you elaborate on which build prop edits need to be done, ro.product.model, etc. As I stated above I tab into an encryption problem, would a stock Verizon build pro fix that?
Sent from my SCH-I605 using Tapatalk 2
Jsminnis please add me on gtalk. [email protected]
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Evaldino said:
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Click to expand...
Click to collapse
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
JustArchi said:
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
Click to expand...
Click to collapse
Thnx JustArchi for answer (at least somebody wrote smth ).
That is not an app - it's a SIM card "feature" (a special, associated with my personal info (from my passport) SIM card which, I guess initiates those "pop-up messages").
It works this way: you go to www.example-mybank.com, enter there my ID and phone number, then (i guess) the special SIM card pushes a message "do you want to connect" (and shows control code to be sure it's your connection), enter your special PIN, and SIM card gives command to my bank "OK, let him in, it's really <Evaldino>" and the e-bank opens up for me
So, I guess it's something with "SIM services" (don't know how to call them - I'm a noob user), which work only on Stock or Sam-based ROMs, so perhaps CM/AOSP/MIUI lack a "module" or smth for these "SIM services" to work...
Also, this M-signature works on all smart devices (not only Samsung, not only Android, also on iOS, maybe even WinOS).
I see no other option as to try those SAM-based (though not really happy about that), so I'll definetely look into your ROM (I like 240DPI, circular battery, if only 4x4 pattern lock for locking screen), because for ex. on ReVolt (Sam-based, yes?) "m-signature" doesn't work (though I kind of liked this ROM)..
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Wayne Tech S-III
slaphead20 said:
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Click to expand...
Click to collapse
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
zelendel said:
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Click to expand...
Click to collapse
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Evaldino said:
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Click to expand...
Click to collapse
There are no pure aosp roms for most devices. They all use something from CM. Be it kernel or some of the coding as aosp only supports the nexus line as a base. Everything else is a fork.
Wayne Tech S-III
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
valdelis said:
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
Click to expand...
Click to collapse
There is no way to solve it. It will not work on AOSP based roms.
zelendel said:
There is no way to solve it. It will not work on AOSP based roms.
Click to expand...
Click to collapse
Actually I just flashed this one [ROM][Mar 17] Jellybean 4.2.2 for Endeavoru AOSP Build [Kernel 3.1.10] [JDQ39] #19 and at last it works! Will try to use this ROM for some time to be sure everything works, but it at least the biggest problem is solved.
By the way, I forgot to mention in my first post, I'm on HTC One X (International version with Tegra), but hope there is a workaround for SIII too.
For Samsung Galaxy Mini there is AOSP ROM (http://forum.xda-developers.com/showthread.php?t=2413108)
Hello,
So my brother bough a chinese smartphone. Many chinese apps where preinstalled and I have been able to remove them, so you wouldn't notice it is a chinese device. However it would be neat if this phone would have proper AOSP.
The current ROM is almost AOSP, minor modifications have been done. This made me curious, would one be able to compile AOSP from source, and use the original kernel (if compatible)? Is a kernel extractable from a ROM to be used in another? Do you need the sources from the manufacturer in order to succesfully build AOSP?
Please note I'm not trying to do this, I'm just curious if it could be done. I have done a fair amount of research but most of the tutorials are about compiling kernels, something I DON'T want to do.
_Roysten said:
Hello,
So my brother bough a chinese smartphone. Many chinese apps where preinstalled and I have been able to remove them, so you wouldn't notice it is a chinese device. However it would be neat if this phone would have proper AOSP.
The current ROM is almost AOSP, minor modifications have been done. This made me curious, would one be able to compile AOSP from source, and use the original kernel (if compatible)? Is a kernel extractable from a ROM to be used in another? Do you need the sources from the manufacturer in order to succesfully build AOSP?
Please note I'm not trying to do this, I'm just curious if it could be done. I have done a fair amount of research but most of the tutorials are about compiling kernels, something I DON'T want to do.
Click to expand...
Click to collapse
It is definitely possible, but will take many hours of work of you want to achieve a stable daily driver state. Usually the kernel will need modifications to make it work with the AOSP ROM.
Sent from my SGH-T999 using Tapatalk 2
Say the rom uses a kernel that works with AOSP, can one build the Android OS using the already compiled kernel from the device?
So I'll start by saying, if you read any of the current porting guides, it's basically impossible to build CM for a device unless you already have it running on the device... So that's not very helpful.
I am working on porting CM10 to the Ouya, I have the build environment set up fine, I can build a perfectly working CWM recovery from source for it, but when I build CM10 it doesn't boot, nothing even shows up on the screen. I am pretty sure this is due to some missing proprietary blobs from the Ouya, but since no one has made a proprietary-files.txt for it yet, I'm left in the unenviable postion of having to do it myself. I have no problem with doing it, I simply don't know how. I tried using the file from the tf700t source (because the hardware is the most similar) but got no better result. Now I've spent 2 days searching fourms, google, etc. to find a guide to create a proprietary-files.txt, but all I can find is a mess of sites telling you how to use an existing one...
Can anyone help me with this, or am I out of luck? Alternatively, does anyone know an IRC channel I could find an expert in? Fattire and Dalingrin come to mind for their work on the nook color and HP touchpad. If they could make those devices work they should be able to help me fix the ouya with no trouble...
I want to build the Android Wear AOSP code and flash a watch with it, however I can't find any instructions anywhere online and I've just downloaded the Lollipop Wear AOSP code but there's no instructions downloaded that I can see.
I know how to build/flash a phone AOSP but wondering if/what is different for the Wear AOSP - for example if I type lunch I still get the same options as I do for a regular AOSP -there's nothing in there specifically for wearables as far as I can see so which combo do I pick to build it?
Then after I've built it, can it be installed using fastboot flash boot|recover|system|data images or are there different partitions/images?
Thanks for any insight.