Database Develop

Attn: Dev's - Porting your ROM to the D2 made easy

OK guys I am posting the files I needed to port my 2.3.340 based ROM, GummyJAR, to the D2..
This should work for any 320/340 DX ROM really.
Now with my ROM I also had to include the AOSP keyboard as the Gingerbread one doesn't work right on the D2.. Also make sure to to redue your build.prop edits as this update comes with a build.prop
Here is an update.zip with all the needed files
Please if you like my work donate as I would like to buy other phones to build other ROMS

Tried it on a few different roms. Camera and video camera, the things I couldnt get working, work Physical keyboard, the one thing I did figure out, does not. Easy fix though. Your awesome Kejar!!
**I updated your update.zip to fix keyboard. It works 100% on the 3 roms ive tested it on. Can I post it or do you want to post it?

Go ahead and post it
Sent from my DROIDX using Tapatalk

Here is kejars update.zip to port DX roms to D2. I tested this on 3 different roms and it works. Enjoy!

is there anyway to get this where it will work on the GB leak ???

Guys, is there something like this for defy, or even any chance?
Sent from Barebones-Defy using tapatalk.

Antszej said:
Guys, is there something like this for defy, or even any chance?
Sent from Barebones-Defy using tapatalk.
Click to expand...
Click to collapse
That would be a tad harder since you'll need more proprietary files. It is so easy for these devices because they have very similar hardware.

Vanilla "de-blurred" GB ROM?

Haven't been able to find one, but I was hoping someone knew if there was a vanilla GB rom for the Droid 4. I want to get a "de-blurred" version on GB on the D4 until we get ICS. Anyone know of one? Thanks in advance!

There's a few roms that still have Motoblur but with less bloatware, but none that match your description. For a true "vanilla" GB experience you'd probably want CM7, but Hashcode pretty much abandoned his work on it for CM9. That was on the Droid 3, I highly doubt there's anything for the Droid 4 at this point.
Sent from my DROID4 using Tapatalk 2

Unfortunately, the biggest hold-back has been getting a deodexed version of the stock ROM. I tried deodexing once so far, and my result didn't boot. At the moment, I'm running one of the Nightlies of AOKP that has proven to be particularly stable, so whether I will go back to trying to deblur the stock ROM, I don't know. Honestly, I haven't seen much interest in it. You can try my Motoblur LT ROM for now and see how it works for you, though. I did replace the launcher with Zeam and added the stock Car Home, but that's about it I'm afraid.

I used this to deblur my phone a few minutes ago and it seems fine so far. btw i DID NOT hard reset my phone.

I'm running Eclipse 1.3.4, and it's de-Blurred enough that I can stand it. Intall a launcher, and you'd hardly know there is any Blur left.
Eclipse is deodexed.
Sent from my DROID4 using Tapatalk 2

Is it possible to build CM7 from source for the DROID 4? Can we use the vendor files the devs are using to build ICS?
Sent from my DROID4 using Tapatalk 2

We could start with the D3 port, and update it and go from there, but after talking with Hashcode, I was reluctant to work on it because I am not 100% familiar with how Safestrap works. Unfortunately, I rely HEAVILY on my phone for my school and work, and if I accidentally brick it, I am in big trouble.

Anyone port the ICS leak's radios and kernel yet?

I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo

The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA

Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA

azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium

flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk

highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.

rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.

GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.

wait, the 206 version keeps you on the upgrade path?

dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium

I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.

dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.

I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.

I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium

Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium

Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2

Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?

podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2

..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)

I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.

[Q] ICS for Droid 3 Recommendations

I've been running Liberty 2.0 on my D3 for quite a while now. Starting to get jealous of everyone who's one or even two builds up on me.
I looked into what ROMs were available for the D3 for ICS, specifically because some of the custom apps I use are not compatible with JB yet. I found HashCode's CM9 build and his AOKP build (which could be the same thing, and I just don't understand.
I also posted once before where someone recommended Gummy for the Droid 3, but I could never nail down which version was the most up-to-date and was working the best. I learned that they stopped working on the Gummy ROM over the summer, but if they had a working build, I would love to try it out.
All I am looking for is the most complete build of ICS on the Droid 3. I use this phone as my primary device, so I would like to be able to use the camera, internet, data, etc.
If anyone has any other suggestions, please feel free to recommend what you use/have used.

joefuf said:
I've been running Liberty 2.0 on my D3 for quite a while now. Starting to get jealous of everyone who's one or even two builds up on me.
I looked into what ROMs were available for the D3 for ICS, specifically because some of the custom apps I use are not compatible with JB yet. I found HashCode's CM9 build and his AOKP build (which could be the same thing, and I just don't understand.
I also posted once before where someone recommended Gummy for the Droid 3, but I could never nail down which version was the most up-to-date and was working the best. I learned that they stopped working on the Gummy ROM over the summer, but if they had a working build, I would love to try it out.
All I am looking for is the most complete build of ICS on the Droid 3. I use this phone as my primary device, so I would like to be able to use the camera, internet, data, etc.
If anyone has any other suggestions, please feel free to recommend what you use/have used.
Click to expand...
Click to collapse
There is no 100% working ICS rom as of now, but with Kexec they have a custom kernel booting and building from there. I would settle into a GB rom for stability/everyday use and have either an ICS or JB rom just to test. You can check the development forum for the current active CM9/CM10/AOKP by Hashcode, the latest CM10 (Jelly Bean) Kexec rom only seems to have a sleep issue and no camera, everything else seems fine so far. Safe Strap 3.05 lets you have up to 5 bootable systems without swapping nandroid backups; Stock + 4 custom rom slots.
http://blog.hash-of-codes.com/how-to-safestrap/ Here is Hash's website about safestrap and to download.
http://forum.xda-developers.com/showthread.php?t=1804665 Here is the thread about Hash's current work on Kexec and available roms. Read up some of the last ~20 pages for current rom and information on it, just make sure to learn the new safestrap before playing around.
As for other roms; The Gummy team split up as I recall, no more Gummy roms...
Personal main usage; I use Maverick ROM 4.0, good battery, good tweaks, looks nice.. version 4.5 has overclock, but a bug in it causes battery drain so stick with 4.0.

Best way to restore a ICS bionic?

So I've pushed the ICS leak onto my Bionic (Build number 6.7.2-223) and after having it on there for a while, i'm looking to restore the phone since it's been slowed down really bad now. My question is, what would be the best thing to do? Should i go to Factory data reset and reset it that way? I'm aware that there's a build number that works that's ahead of mine (-232?). Should I upgrade to that? If so, should I just follow these http://forum.xda-developers.com/showthread.php?t=1771993 steps? Anyway, thanks for the help!
Edit: I do want to keep ICS on there. I'm not looking to restore it completely back to Stock.

dewie68 said:
So I've pushed the ICS leak onto my Bionic (Build number 6.7.2-223) and after having it on there for a while, i'm looking to restore the phone since it's been slowed down really bad now. My question is, what would be the best thing to do? Should i go to Factory data reset and reset it that way? I'm aware that there's a build number that works that's ahead of mine (-232?). Should I upgrade to that? If so, should I just follow these http://forum.xda-developers.com/showthread.php?t=1771993 steps? Anyway, thanks for the help!
Edit: I do want to keep ICS on there. I'm not looking to restore it completely back to Stock.
Click to expand...
Click to collapse
I'm not sure but are you aware that ICS .246 is the current software for the bionic (not a leak but an official build)? My suggestion would be to RSDlite the thing to the stock firmeware of .246. Then install SS 3.11 and make a partition and install a nice rom. As for rooting the motofail root works just fine on the ICS stock build.

neo1738 said:
I'm not sure but are you aware that ICS .246 is the current software for the bionic (not a leak but an official build)? My suggestion would be to RSDlite the thing to the stock firmeware of .246. Then install SS 3.11 and make a partition and install a nice rom. As for rooting the motofail root works just fine on the ICS stock build.
Click to expand...
Click to collapse
Hah yeah, I only found out last night. Okay, that all sounds logical. Only two questions are, what is SS 3.11, and what ROM would you suggest. Thanks for replying!

dewie68 said:
Hah yeah, I only found out last night. Okay, that all sounds logical. Only two questions are, what is SS 3.11, and what ROM would you suggest. Thanks for replying!
Click to expand...
Click to collapse
SS = Safe Strap version 3.11
As for Roms so far the fastest Jelly Bean Rom is Icarus, but it doesn't have all the frills of the newer Cyanogen mods. As for ICS Roms I like Blurry Maxx or Eclipse. Google search should find them. Also there are roms in the Bionic Development section of xda here you can browse and see what some of the features are. Good luck.

neo1738 said:
SS = Safe Strap version 3.11
As for Roms so far the fastest Jelly Bean Rom is Icarus, but it doesn't have all the frills of the newer Cyanogen mods. As for ICS Roms I like Blurry Maxx or Eclipse. Google search should find them. Also there are roms in the Bionic Development section of xda here you can browse and see what some of the features are. Good luck.
Click to expand...
Click to collapse
Personally I would go with Eclipse, they recently released v 1.3 that runs great (way better than stock). I tried BurryMaxx but its pretty overclocked so the battery drain is quite a bit more than eclipse. Honestly I don't think you really need the OC as long as you make sure to use task killer frequently enough. I tried AOKP and CM10 for the JB roms but neither of them were ready to be daily drivers, I had issues with phones not ringing/vibrating, screen of death, etc. (and of course the standard camera issues).

:thumbup: