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.
Related
The only determining factor on whether I stick with OEM ROM or flash monster/steeldroid ROM is this: do these custom ROMs have a single bug?
So, users of monster and steeldroid ROMs: are there any bugs?
There are absolutely bugs in both ROMs but there are bugs in OEM too. Both SD and Monster run so much faster than stock. You can still do everything youre used to on the roms. CM7 had the phone broke at one point but even thats fixed now.
Thanks.
I've got one more question if anyone can answer it. Do either of these ROMs I mentioned work on the Verizon Wireless Droid 3 or the GSM Droid 3?
I own the Verizon Wireless one (gotta make sure I don't flash an incompatible ROM by accident).
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
dpwhitty11 said:
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
Click to expand...
Click to collapse
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
poetryrocksalot said:
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
Click to expand...
Click to collapse
Right now they're all equally consistent and reliable. Mine just hasn't been out as long, so less people are running it, but hopefully that'll change soon.
Sent from my DROID3 using XDA App
Lol I meant no disrespect. Although I know they have a decent user base, I have not tried dark droid, narcotics, or the other chinese rom (or whatever it is
Sent from my DROID3 using XDA App
Anyone else have problems with contacts forceclosing?
Sent from my DROID3 using XDA App
Ever since I flashed SteelDroid 3.0, the market app won't let me make purchases. I tried flashing Market 3.2, 3.0.26, and 3.1.something, and I tried the Root Explorer replace Vending and uninstall update method and nothing seems to work.
Not sure if its the ROM or something else, but very frustrating.
I'm having the same market problem with Monster, I brought it up in the Roms thread, hopefully it will be fixed in the next update
sent from my MONSTERDroid3 from the XDA app
i think you just need to wipe data/cache to get your market to work.
Yes wiping data and cache will fix the market purchases
Sent from my DROID3 using Tapatalk
Flashing with bootstrap Droid 3
I went in to the recovery mode of bootstrap and then went to safe mode to install zip from sd card and i got it to install. Although when I reboot in safe mode nothing starts and when i boot in regular mode it seems exactly the same? I was trying to get the monster rom on 1.2 need help am i missing a step>? I followed the instruction and i did not notice that i had done anything different.........
No issues with darkdroid or steeldroid 3 from what i've found with my own slight notification mods for both, not had any market buying issues with either, flush the cash of the app or reinstall the market, failing that reinstall your roms from scratch.
-smc
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.
Hey guys havent been on xda in a while. Got very busy and so on /so forth. Just wondering what major things have been accomplished in the last 6 months or so. You dont have to go crazy with your responses im just curious. Im on 5.6.890 verizon XT862. Runnin the liberty 3 still lol. What roms are new/better. Whats new and improved/ what do you reccommend? Thanks for your responses in advance!
Sent from my droid 3 using Tapatalk
I would update your system to .906
Then eclipse 3.0 for a gingerbased rom
Or
Cm9 for ics
Thank you
Sent from my droid 3 using Tapatalk
Also, can anyone walk me through overclocking? Im struggling pretty badly.
Sent from my DROID3 using Tapatalk
Actually MavRom 4.5 has overclocking and is much more stable than Eclipse IMO. You could try that or even stick with Liberty (which was great for me) and just find the opptimizer flashable zip on Google for the Droid 3 and learn how to use that and use Busybox installer to run a script as root.
As far as what's new, Hash is trying to get kexec (load a second kernel after the first one boots on top of it) to make a ROM that is sweet but it's taking a while.
MrObvious said:
Actually MavRom 4.5 has overclocking and is much more stable than Eclipse IMO. You could try that or even stick with Liberty (which was great for me) and just find the opptimizer flashable zip on Google for the Droid 3 and learn how to use that and use Busybox installer to run a script as root.
As far as what's new, Hash is trying to get kexec (load a second kernel after the first one boots on top of it) to make a ROM that is sweet but it's taking a while.
Click to expand...
Click to collapse
Wow thats impressive. And thank you ill try that. I recently just went to steel droid 4.8 yesterday. the theming doesn't blow my mind but as far as performance, im not disappointed. Plus it had the. 906 update already in it (; so can't complain. Plus im sick of ics otherwise id go to 5.1 lol.
Sent from my DROID3 using Tapatalk
i want to go back to ics. the jelly bean downsides are becoming a pain right now. what exactly would happen if i just reflashed with ics stock? will it brick and will it be recoverable? can anyone explain in depth the issue regarding this? or will i have to put my phone up for sale and obtain a replacement that still has ics?
the jb performance has been cool but i had everything working perfectly on ics. and the jb update is just significantly less than perfect for my setup and app needs. serves me right for rushing for the latest update i guess. but ive got to go back to ics. jb reminds me of windows millenium edition.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Sorry you aren't enjoying the upgrade. I'll throw out the obligatory suggestion of performing a factory reset on your phone if you haven't already done so since the upgrade. This will allow your phone to clear out old ics data and use pure jb. However, for some people, updates truly do kill their experience and that's a personal thing.
With official updates from Motorola, our devices also receive a new kernel in addition to a new version of android. JB uses a newer kernel than ICS, just as ICS used a newer one than Gingerbread. Unfortunately, because our devices have locked bootloaders, you cannot go back to the ICS kernel, meaning you can not downgrade. Trying to fastboot back will result in a brick, most likely permanent.
At this point, you would need to get a replacement still running ICS if you truly want to downgrade. Alternately, considering using custom roms, which at this point are all JB based, but far superior to the Motorola "Blur" version found on stock phones.
Sorry!
Sent from my XT894 using Tapatalk 2
thanks. looks like this d4 is going up for sale. i did the factory resets when i did the update. but some apps i really like dont work on on jb. id designated them lifelong companion apps. so jb being unable to run them means jb has got to go. my d4 completely suited my needs untilt this update. now it's incomplete. and without moto allowing the bootloader to be unlocked means athe d4 was just destroyed by this update imho.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Have you thought of emailing the app developers and asking them to update them to support JB?
Any and every new phone coming will be based on JB so that limits you to buying older, unsupported devices which will make newer apps as they come out unavailable to you.
thanks but i dont NEED anything else. this thing is totally unreliable. its not storing profiles and settings in some apps so i have to readd login details etc every time i launch the program, others forceclose to homescreen after launching without an error.
i thought about the email option.. but thereve been so many ppl clamouring about them since last summer im not putting any hope on that. i think they really screwed up with jb and took a few steps backwards. unfortunate but this d4 has got to go. cant sell it fast enough right now.
im really happy with the d4. dont see any need to upgrade for the next 10 yrs. great phone/multifunction device. ill buy 3 and keep em on ics with backup parts etc for repairs.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
The Magician Type 0 said:
Sorry you aren't enjoying the upgrade. I'll throw out the obligatory suggestion of performing a factory reset on your phone if you haven't already done so since the upgrade. This will allow your phone to clear out old ics data and use pure jb. However, for some people, updates truly do kill their experience and that's a personal thing.
With official updates from Motorola, our devices also receive a new kernel in addition to a new version of android. JB uses a newer kernel than ICS, just as ICS used a newer one than Gingerbread. Unfortunately, because our devices have locked bootloaders, you cannot go back to the ICS kernel, meaning you can not downgrade. Trying to fastboot back will result in a brick, most likely permanent.
At this point, you would need to get a replacement still running ICS if you truly want to downgrade. Alternately, considering using custom roms, which at this point are all JB based, but far superior to the Motorola "Blur" version found on stock phones.
Sorry!
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Or maybe flash one of the ICS kexec ROMs? Not sure if it would work butttt possible. I may just try it myself so I can play order and chaos again.
Sent from my XT894 using xda app-developers app
Have you factory reset your device (Settings/Privacy/Factory data reset) since taking the update to JB?
Apps should be retaining their configurations (logins, etc..) and the phone should be smoother/faster than when it was on JB.
More than likely since the update patched the ICS system files to bring them to JB versions...something is causing issues from the updating. I'd definitely try a factory reset and reconfigure your phone. It may just be needing a proper reset/setup...
Imagine a Windows PC running Windows XP being "upgraded" to Windows 7 vs. another identical PC with a fresh install of Windows 7. The fresh install W7 will run much better compared to the patched/updated XP-W7.
If you haven't factory reset your device in a while....it's gone from GB, patched to ICS then patched to JB....or Windows 95 patched to XP then patched to W7.
yeah i factory reset twice during initial upgrade and setup all from scratch. at first a couple programs cudnt run and found out they dont work with jb and everyones hoping for an upgrade that seems abandoned by the developer. that was.. bearable slightly if i could find alternatives. but im yet to find satisfactory alternatives to any of them. my guitar chord and scales program wont run anymore. its installed but wont show in the app drawer so i cant launch or uninstall it. lbe privacy throws the fone into a bootloop. motoprint was removed in jb and i loved it. i found an alternative called send2print.. it works is all ill say about that. but overall its just a pain in the rear now. i liked how i never had to worry about anything before. everything just worked. so thanks for the input guys but this phone is going. already put it up for sale.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Hi on my work to unbrick the droid i have flash the ics via droid ics utility but it dosend start i think it ist the kernel becouse if you are on JB you don't get ics roms to work but with the kexec kernel it's working so I think if we get the ics kernel working we get ics back
Sent from my DROID4 using xda app-developers app
Looking for the latest version of Hash's CM9 NON KEXEC rom. I had been running this for a year with no trouble. Decided I wanted to play around again and updated to the new safestrap and loaded JB kexec and it's just not stable enough, sleep issues won't work for DD, and gingerbread sucks. Now I can't find my .zip file and don't see it posted anywhere. The non kexec ICS builds were solid, and the camera worked decent. I want to go back. Does anyone have it?
maybe this is useful for you?
http://forum.xda-developers.com/showthread.php?t=1465297
Nope. That is for the xt860. I know someone has hashcodes non kexec ics roms, if they could just send me a dropbox link or something it would be awesome. Right now I'm using steel droid ics but it seems to have more issues than the hashcode cm9 ics rom I ran for a year.
Sent from my XT862 using Tapatalk 2
Actually that would work you would just have to use the 862 data files from Steel Droid probably.
Let's see if this can be helpful.
I was looking for a good ICS, with camera working, so let's give it a try.
I really need the camera, so that's why I didn't even tried the JB.
Thanks for the link, sm4rty!
you're in luck!
had to hook up the old dev box but found this file, enjoy!
https://dl.dropboxusercontent.com/u/20441294/cm9-droid3-20120101-1600.zip
Found this while I was cleaning up my SD card. Not sure if it's KEXEC or not. It wasn't labeled. I have a feeling it isn't.
https://www.dropbox.com/s/08eyaqskj5041zy/cm9-droid3-20120316-0330.zip
EDIT: Installed it to make sure. It is non-KEXEC.