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]
Related
I have recreated the romer tool. The purpose of this tool is to replace certain files to make D2 roms work on the droid 2 global. To use simply install my file after installing a droid 2 rom via recovery. This version is designed for ginger-blur based roms such as apex and liberty. Do not flash over aosp roms such as cyanogenmod and liquid. I am currently working on creating a aosp romer tool. Do not use on froyo eaither, as this will temporarily brick your phone. I have tested on both apex and liberty, and sensors,gsm,data, and phone are all working. Please enjoy
Disclaimer: I am not responsible for what you do to your phone. If your phones does not do what you like, becomes 100% useless, or explodes killing your wife and children, it is not my fault. I can garauntee that my file is safe, and works perfectly for what it is designed. Make sure to check before you flash a d2 rom that it does not contain a d2 kernel. This could permanently brick your phone! Just be careful
Download v2.2:
http://dl.dropbox.com/u/46535328/D2G-GingerBlur-Romerv2.2.zip
Thanks:
Thanks goes to fabolous for apex , which is were the majority of the files for my romer comes from.
ChangeLog:
V1.0: original, based off of GRD Rommer.
V2.0:completely remade with no more GRD remains.
V2.1:Liberty tweaks put in build.prop.
V2.2:moto boot logo and boot animation added. I can remove this if it is disliked.
Comments:
Has anyone tested out the aosp romer. I would be happy to fix things or add things as people like. I will gladly update this if anyone wants, I have just been working on other things. I have been taking a look at cm source code, and app development. Also eaither one of these will work on Droid X roms. Haptic feed back will not work though.
P.S. If you download this, and enjoy it, please press the thanks button.
**********************************************************************************************************************
This section is for my romer tool having to do with porting the new 2nd init roms or anything that is based off cyanogenmod 7 or aosp that is originaly designed for the droid 2 or Droid X. I have tested it and can approve that it will work for miui,liquid, and cm. I am not liable if this does anything negative to your phone. To use just flash over an aosp rom for the droid x or droid 2 and enjoy on your global. For now the only thing that does not work is gsm. If i can fix it I certainly will.
Thanks: I thank revnumbers for his cyanogenmod builds, as this is were I took the proprietary files for the d2g from.
Comments:
If any of you want me to add something, or try to fix something, please post and I will see what I can do.
Download/Aosp Romer V1.1:
http://dl.dropbox.com/u/46535328/D2G-Aosp-Romer_V1.1.zip
Thanks:
Thanks goes to RevNumbers for his cyanogenmod 7 build, which is were the majority of the files come from.
Change log:
V1.0: Original, fixes phone,cdma data,keyboard,camera,sensors,etc...
V1.1:Fixes su/root permission error.
Comments:
Don't worry if the phone does not receive signal immediately. It takes it a minute.
I accidently set the permissions for su binary wrong. V1.1 fixes this.
! I would HIGHLY not recomend using anything built of of the D2G's romer !
The reason for that is because that method of porting is considered vastly inferior AND because it had many bugs in it because of it. The romer team from Get R Done also had a lot of strife in it and a lack of knowledge. A straight update of the files will not work well.
It needs redone, not updated.
Thanks for the advice aceoyame . I have tested it, and it works, but I do not know what problems may arise from it. I will work on redoing it
also, if you have the time could you describe the problems into more depth of what is wrong with team get-r-done's flashing process. I am not quite as well educated in the art of writing an updater script as you are I am sure.
Well the biggest issue with a romer vs natively porting is that you have too many files that are for one type of rom vs working for others. The romer will only do Gingerblur based as you have it (that's if sensors and everything else works). It will not do any aosp based roms (liquid, CM, MIUI, etc.) The libs are way too different. If you wanted you could make an AOSP romer and Gingerblur romer. Just pointing out the flaws in it.
Thanks for replying ace. I natively ported liberty on another forum. The reason why I made this is so people can just flash it over any liberty gb rom, instead of me having to make an update for each individual version. I have only tested it on liberty, and on liberty sensors,backlights,gsm,phone,keyboard,and data are all working. I would guess that would apply to any gingerblur based rom. I knew that it would not work on cm,liquid, and miui, and did not really care since thanks to you and other devs we already have those roms made for are phone. This is for those roms that only exist on the d2 and not the d2g
Well grats on fixing the sensors then! Rewriting the romer is something we've been wanting to do but could never get around to it. If it is 100% bug free on liberty than it should work for any gingerblur rom. You got sensors to work which was the big issue with the GRD one then you at least fixed something! I would just test the hell out of it and if it works then you probably hammered out any bugs they had with it. An AOSP one would be nice for the other roms. Feel free to put this on Rootzwiki and the other forums.
Thanks, I will make a asop version when I get the time.
This is a call out to all existing and future developers of Xperia MDPI Devices.
For about a month now there is an app called Update Me Smartphone, which basically gives OTA update functionality for our Custom Roms.
From 01/05/2012 the developer of this app has given it a very interesting feature. You can view all Roms compatible with the Update Me Smartphone application. Even though you get a list a bunch of irrelevant devices, I suppose if we all "help" him with our suggestions he can make an application that will be on par with the Rom Manager app for devices that are fully supported by CWM.
To make this as simple as possible....
User "A" wants to download a new Rom for his Xperia MDPI Device. He has already downloaded and flashed a custom kernel (whether this is a Stock Kernel, or a CM kernel), then proceeds to download the app, install it and browse any compatible Rom's with his device... From then on his device will stay updated, through the Update Me application providing OTA updates of the Rom he has installed. If he wished to download another rom (compatible with the kernel he has - there are 3 Different Kernels AFAIK: GB CM, ICS CM, GB-ICS Stock Sony Kernel) he will just proceed to download the latest version of the rom he has selected straight to his device. No need to download to your computer, then connect the device, then copy it, then flash it. If you have the compatible kernel already installed, then its easy as pie.
Please let me know of your thoughts on this...
Edit: Link to the application's thread http://forum.xda-developers.com/showthread.php?t=1590170
Edit 2: Apart from Rom's we can also implement various mods, tweaks, fixes, etc for our devices. Even though that would be extremely hard, due to the fact that all these files need to be stored in a direct download location like Dropbox, its is a viable option.
OMG I love the idea, that would be awesome!!
It's very interesting, thanks a lot for the info I will try it!
Some modification: In GB we have 3 different kernel (Stock Based, CM Based, MIUI Based [not released yet]). In ICS we don't have Stock based to Xperia MDPI, because Sony don't released yet the stock for us. So we have CM9 based, AOSP based (it's work with CM9 ROMs btw), and ported Stock based.
Some another notice: I saw a lot of thread (not only in this forum), but sooo many people trying to make ROMs. It's not a problem, but some guy don't know some full minimum things... So who will help this guys to add this app to their ROMs?
Are you using a different Kernel for the Sony ICS rom port? I mean the Ramdisk is the same size and you're using the same zImage from a stock GB rom correct?
Well nobody is forced to do this. All we have to do is provide the app developer a link with the update_me_check.xml so that he will sort of add a link for that in the application.
By the way, i now got my goo.im account, and this have own OTA app. I will try it, and I will report.
But I know, this is not only OTA app... Hmm... I need to think in it
So the only developer checking the thread is Expeacer?
Ok...
dumraden said:
So the only developer checking the thread is Expeacer?
Ok...
Click to expand...
Click to collapse
What makes you think like this?
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
dumraden said:
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
Click to expand...
Click to collapse
I also read quite a lot of topics, but I don't respond in every topic.
I'd like to create a flashable zip of a full stock ROM with some really basic changes from the stock Nexus 4 4.4 factory image. I know the core of the question doesn't fit this forum section, so please bear with me and read to the end before telling me to take this to the N4 section.
I've been reading guides here on XDA on flashing and porting Android ROMs, as well as the official documentation, for a while today. Some of them are quite good and thorough. All of them seem to focus on AOSP or ROMs like CM being modified or built. There's one thing I'm left a bit unclear on which I would appreciate someone more knowledgeable clearing up for me.
How is it that I get from a factory image to a flashable zip, or from AOSP source to a flashable zip that's identical to the stock factory images Google releases?
I understand that I may need to compile this from source and I'm fairly comfortable compiling source code on Linux. What I'm not completely clear on his how close AOSP is to the stock Google factory binaries and exactly what changes would need to be made to bring it in-line with those releases other than hardware drivers.
This is initially just for my own purposes to have a flashable zip of stock Android the way I like it on my N4. The tweaks are low in number and scale. The LTE hack, the 4.4 tethering fix, and the GEL are the primary things I'd like to incorporate myself.
I'm sure someone has already done something similar to what I'd like but I'd also like to learn this so I'm not really interested in being pointed to ROMs which have already accomplished this. I do appreciate the thought though.
So it has been a long time in the works and feels like have been working on this forever. First it was an AOSP Rom, then Caf and at some point both. For now the Rom is AOSP 5.1.1 based.
Is still not 100% but have decided to just go ahead and post the Rom and improve and update.
If you have seen the Test Flight CM based version that had been posted with the Starship Kernel the overall theme is pretty much the same.
The mission now is to first go over a few parts of the theme that bug me or did not translate well in the CM to AOSP Transition such as lightening up some text so is easier to read with darker backgrounds. Second mission is go over every APK one by one and fine tune the theme and add in any extra features. Will post an update as each APK has been completed. Most of the work is done in some form or another but have spent ages nitpicking everything to death and have an external drive filled with already completed images, Colour XML's and lots of uncommitted features so updates will come rather quickly. Honestly at this point am just going to start with the APK's in Alphabetical order so if you like the Rom and theme but a few particular things bug you just let me know and I will not mind jumping ahead. Also with each Rom update not only expect app and theme improvements but kernel and other system enhancements as most are already lined up and just need to be tested in the Rom's new incarnation. It has probably seen some better days but with my constant picking and changing have gone back and forth with so many things I think its best to just post so Starship is out there and now start finalizing. What is currently posted is bare bones themed and featuring a Kernel I have also spent almost a year working on. If you had used the Kit-Kat version of Starship then already know how fast the Rom will be improved and updated based on legitimate feedback. I know I am making things out like this is an incomplete Rom but have been using and been very happy with what is posted as my daily. Yes still need to improve a few things but the truth is I am never happy with anything I do and would have kept changing direction until Android N.
Until next time keep looking up!!
Installing
This version was not compiled using the new block based zip format so will take a bit longer when flashing the Rom. Just a warning for anyone who may think something is wrong. It Just takes a minute longer to flash.
Otherwise besides first performing the usual Wipe of Caches, System and Data also recommend flashing the Rom first, Gapps second and SuperSU last.
Downloads
Starship Rom
https://www.androidfilehost.com/?fid=24052804347762130
G-Apps
I recommend using the Banks 5.21.15 version of Gapps and have posted a link below. I don’t like reposting someone else’s work but just now discovered the 6.17.15 version seems glichy during the set-up wizard sometimes needing to be in landscape mode when making a selection so have reposted the version used during testing. Have also posted a link to the 6.17.15 version but found for example during the restore option selecting done will only register the selection in landscape mode.
BaNkS-dynamic-gapps-L-5-21-15
https://www.androidfilehost.com/?fid=24052804347762124
BaNkS-dynamic-gapps-L-6-17-15
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Kernel
I will continue keeping a separate thread for Starship Kernels that may update faster than the Rom so can keep a look out here.
http://forum.xda-developers.com/goo...t/kernel-starship-kernels-01-08-2014-t2997470
In staying with the Rules will find Source for the Kernel that is included here
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Starship Github
https://github.com/Starship-Android
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Screen Shots
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a [email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
lostcelt said:
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a hud[email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
Click to expand...
Click to collapse
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
squid2 said:
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
Click to expand...
Click to collapse
Thank you for responding to my questions, squid2. I am very much honored to have had you taken the time to write on my behalf, this is certainly something to which I feel very privledged.
For the sake of clarity and accuracy I will quickly repeat the steps I just took after reading your answer to this thread. If you do not write into this thread a second time I will assume the steps I just took are indeed the correct ones.
1. I went to http://forum.xda-developers.com/moto...odems-t3296044 as you directed and downloaded only the one folder titled Modem, ignoring the larger file that includes another three folders in addition to the Modem folder (the larger file containing all the four files is 25.79GB, whereas the single Modem folder is just 561MB).
2. I then unzipped the Modem folder and selected the SURNIA-RETUS_5.1.zip, ignoring the SURNIA-RETUS_5.1_new.zip which is also in the Modem folder. (The newer SURNIA-RETUS_5.1_new.zip file is two days newer than the other SURNIA-RETUS_5.1.zip file, but since they are both in the same Modem folder I am taking that to mean I should follow your original instructions precisely as directed. Both files are about the same size, except that the newer file is slightly smaller than the other.)
Again, thank you. Your instructions were vital in enabling me to move forward on this task. We need a bitcoin tip jar for people who take time to help others.
xpmule said:
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
Click to expand...
Click to collapse
Thank you, xpmule. I had been wondering whether it was a good idea to install CM or to use a stock Rom. From what I've been reading the Moto E version of Android is fairly bloat-free and since I really only need a rooted phone there is no real need for CM.
I've learned more than once that messing around with unfamiliar OS can be a recipe for disaster after foolishly timing updates of a Linux or BSD OS when I have papers due or exams to study for.
I'll take some more time to research the other options you recommended and then follow your lead with respect to this phone.
Again I'd like to thank both squid2 and yourself for helping me on this, and may I suggest that people who provide meaningful assistance such as this put a bitcoin wallet addres in their signature so that people like me can show our gratitude .
I Support Bitcoin and i think i said that to Squid before too LOL
But i have before refused some for helping people more than once.
My help is not as much as Squid's though.. he puts in effort for his public projects LOL
I don't think you will see him giving advice too much either.. at least i haven't.
So Squid.. GET a Bitcoin address man
OP good luck.. i think Moto's Android is fairly bloat free.. The stuff Moto put on there is good.
Like the twist the phone to activate the camera app or the app that tweaks the notifications.
I am happy myself just modding the stock firmware.
Thank you squid2, I followed your directions exactly as prescribed and I am now rocking the lastest nightly build of CM on my Moto E. It was fairly easy and I can confirm that everything works just fine.
And thank you as well, xpmule. I was going to follow your instructions too but when I got to a certain point in my process and my phone asked if I was sure I wanted to reboot even though there was no OS installed, well I had one of those moments.
Thank you, thank you, THANK YOU!!
Now it's time to explore this CM OS and see what all the fanfare is really about. )