Related
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.
So who here is on an Android 4.0.4 leak? (official ICS leak)
Who is still on stock gingerbread?
Who is running a custom rom?
Answer in the comments and in the poll.
Im interested to see what is being used!
--Sam
I'm on the 208 leak. Lost root cuz I went from 200 to 206 then 208 but its all good. Only bad thing is all the bloat but besides that its running pretty well so far.
Running ICS leak. 206, kept root from GB .219
I was tempted to keep updating with each new leak, but at the expense of losing root I think I'll wait for the official upgrade to be released.
Sent from my DROID4 using Tapatalk 2
Stock rooted/debloated Gingerbread.
ICS shouldn't be that far off....waiting for the official release version. Since leaks are hitting every 12 to 13 days.....and you lose root going from one to the next.....might as well wait it out.
Running Eclipse ROM via SafeStrap. Sounds like the ICS leaks are running really well for most people. I'd just prefer to make sure I keep root and not have to worry about jumping through a bunch of hoops to update when the OTA finally drops, which can't be too far out.
Running stock. I really like AOKP, but the data issues were killing me, so I switched back. I figure once the OTA drops the ICS ROMs will work a lot better. I'm also hoping we get working 3rd party kernels.
I am running a stock ICS Leak
I am also running the stock .206 leak for the Moto Droid 4 and loving it. I haven't tried going to the new .208 leak as of yet.
I'm on .206, rooted. Very happy with it. I don't plan on upgrading again until Dan Rosenberg releases his ICS root method. As nice as ICS is...I'd rather be on GB with root than ICS without it.
wouldn't VooDoo OTA Root keeper work in all of this? I use it to maintain my root for OTA upgrades. But wouldn't it still work with a firmware push?
Just updated to 208 using Fastboot Upgrade and New ICS Root Method then recovered my files from Safe Strap for the data partition. :-D
gdeeble said:
Just updated to 208 using Fastboot Upgrade and New ICS Root Method then recovered my files from Safe Strap for the data partition. :-D
Click to expand...
Click to collapse
Did you take a nandroid, then restore the data only partition of the nandroid after you did the upgrade? THat's a great idea. I might do the same if it is that easy! Otherwise, I'll wait for a newer leak.
buying Droid soon.
I am eagerly awaiting the official ICS rollouts for Verizon, but it may be a while. The goal is not to update myself. Is ICS really all that...and worth waiting for?
rugo32 said:
I am eagerly awaiting the official ICS rollouts for Verizon, but it may be a while. The goal is not to update myself. Is ICS really all that...and worth waiting for?
Click to expand...
Click to collapse
I was a big Motoblur guy (once you debloat it of course) and even preferred it over CM9. I just liked the theme. I think the Motoblur ICS is worth it, it's ICS with a nice familiar feel to it. Is it worth the wait? Maybe. I have faith we can get back on the official path once it comes out so I didn't take much convincing to flash a leak now.
Sent from my DROID4 using Tapatalk 2
droidian1441 said:
So who here is on an Android 4.0.4 leak? (official ICS leak)
Who is still on stock gingerbread?
Who is running a custom rom?
Answer in the comments and in the poll.
Im interested to see what is being used!
--Sam
Click to expand...
Click to collapse
Not me.
Me.
Not me.
It's a corporate-supplied device... I can't mess around with custom ROMs and deal with bugs that I don't have the time to troubleshoot.
Plus no ROM will improve this awful screen or only-slightly-better camera, right?
Sent from my EVO using Tapatalk 2
I'm running .206. I tried .208 but I'm too much of a noob to even fallow noob proof instructions so I'm staying with .206 till I learn more, and till I can get back on the regular path (if its even possible).
So far I like it, the only thing that doesn't work for me is the facebook (my gallery) from the accounts. It crashes my gallery with an error saying that friendfeed has stopped working, so I just don't use that part of my gallery.
I'm satisfied!
Sent from my DROID4 using XDA
danifunker said:
Did you take a nandroid, then restore the data only partition of the nandroid after you did the upgrade? THat's a great idea. I might do the same if it is that easy! Otherwise, I'll wait for a newer leak.
Click to expand...
Click to collapse
Yes I took a Nandroid before I started the crazy Fastboot recovery process, then once rooted and safe strap installed, I did another nandroid(heaven for bid I'd have to start over again) then flashed over data only.
gdeeble said:
Yes I took a Nandroid before I started the crazy Fastboot recovery process, then once rooted and safe strap installed, I did another nandroid(heaven for bid I'd have to start over again) then flashed over data only.
Click to expand...
Click to collapse
Can't you just use recovery for flashing back data (I assume you are using the advanced restore?) or do you need to have safestrap installed?
I am running the .208 and was able to keep root thanks to Voodoo. I know some people have had issues with keeping root when going to .208 from .206 or .200. I went from GB to to .208 maybe thats why i was able to restore root? Anywho, ive been using the leak for over a week now and i am so glad i did.
Just went from .206 to .208 using the new kernel and following the instructions over at DroidForums. Also got root with the new method. Everything works peachy-keen.
Sent from my DROID4 using Tapatalk 2
On the ROMBot page you can find 2 different kind of ICS ROM's for the Droid4, both CM9 and AOKP based (so 4 different ROM's)
The first kind seems to be based on the ICS leaks:
http://rombot.droidhive.com/ROMs/maserati/ics-leak-builds/cm9/
http://rombot.droidhive.com/ROMs/maserati/ics-leak-builds/aokp/
And the other kind seems to be a 'regular' build:
http://rombot.droidhive.com/ROMs/maserati/cm9/
http://rombot.droidhive.com/ROMs/maserati/aokp/
Can anyone indicate what the difference between these is?
Can I flash both on my Droid4?
vyruz1986 said:
On the ROMBot page you can find 2 different kind of ICS ROM's for the Droid4, both CM9 and AOKP based (so 4 different ROM's)
The first kind seems to be based on the ICS leaks:
http://rombot.droidhive.com/ROMs/maserati/ics-leak-builds/cm9/
http://rombot.droidhive.com/ROMs/maserati/ics-leak-builds/aokp/
And the other kind seems to be a 'regular' build:
http://rombot.droidhive.com/ROMs/maserati/cm9/
http://rombot.droidhive.com/ROMs/maserati/aokp/
Can anyone indicate what the difference between these is?
Can I flash both on my Droid4?
Click to expand...
Click to collapse
The "regular" builds are for those still on stock GB. The ICS leak builds are meant for those who have updated their stock system to one of the Moto ICS leaks.
kwyrt said:
The "regular" builds are for those still on stock GB. The ICS leak builds are meant for those who have updated their stock system to one of the Moto ICS leaks.
Click to expand...
Click to collapse
So the regular ones are some kind of ICS overlay on the GB kernel? Or how should I see that?
Do they work better than the ICS-leak based ones? But I think there's no going back from the ICS leaks, right?
vyruz1986 said:
So the regular ones are some kind of ICS overlay on the GB kernel? Or how should I see that?
Do they work better than the ICS-leak based ones? But I think there's no going back from the ICS leaks, right?
Click to expand...
Click to collapse
There is no going back once you flash one of Moto's ICS leaks. You are right about the original builds basically being ICS running on a GB kernel. These were kinda buggy. Data connection in particular was very flaky. The new ICS leak builds are much better because they are ICS running on an ICS kernel. The way it should be. I am back on stock ICS right now but I ran the CM9 ICS leak for 4 - 5 days and never had any issues. Data was solid. It's really coming along nicely.
kwyrt said:
There is no going back once you flash one of Moto's ICS leaks. You are right about the original builds basically being ICS running on a GB kernel. These were kinda buggy. Data connection in particular was very flaky. The new ICS leak builds are much better because they are ICS running on an ICS kernel. The way it should be. I am back on stock ICS right now but I ran the CM9 ICS leak for 4 - 5 days and never had any issues. Data was solid. It's really coming along nicely.
Click to expand...
Click to collapse
I'm on stock ICS leak as well, wanted to go to CM9 but I can't get into 'mobile networks' settings, probably because i'm in Europe on GSM, I got some help in this thread but at the moment it's a stand-still
vyruz1986 said:
I'm on stock ICS leak as well, wanted to go to CM9 but I can't get into 'mobile networks' settings, probably because i'm in Europe on GSM, I got some help in this thread but at the moment it's a stand-still
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27700656#post27700656
By any way is it possible that LG will upgrade it to JB, or is possible for xda developers to upgrade current stock ICS to JB?
Sent from my LG-P990 using xda app-developers app
CM10.x is JB...
LG's junk isn't needed and therefore it isn't even worth asking/waiting for. We finally got all we wanted from them, now enjoy CM10.
I think the best way for us is using CM10 ROM, such as in this post: http://forum.xda-developers.com/showthread.php?t=2058231
Just a tip. When you're upgrading to CM10 you should have installed CM7 at some earlier point. Easy fix for the SD card bug. Took me half a day to find this out.
Plus use new ICS bootloader, it fix slow charge and minimize call bug
Custom40 said:
LG's junk isn't needed and therefore it isn't even worth asking/waiting for. We finally got all we wanted from them, now enjoy CM10.
Click to expand...
Click to collapse
Well if we didn't have "LG's junk" RC wouldn't have been able to build CM10 as it is now
All you need to build a perfectly good JB ROM without any JB update are device-specific ICS source code and an unlocked bootloader. JB and ICS are still very much the same under the hood, much like the case with Froyo and GB. Back in those days you could also build GB ROMs out of Froyo sources I believe (the O2X got CM7 quite some time before its official GB update arrived).
CM10 is as good as JB can get on our device. I believe the only JB-specific feature we don't have is true vsync, aka no Project Butter, but that's not a deal breaker as it's hardly noticeable.
If you look at recent news, no OEM wants to bring JB to a 512 MB RAM device because their stupid skins like Sense/Touchwiz/LG UI eat up so much memory that allocating more for vsync would make performance atrocious. The only exception is the Nexus S simply because it doesn't have that bloat to deal with.
My problem is with CM10 I can not have 3G calls, FM radio, Polaris office etc.
fundoosite said:
My problem is with CM10 I can not have 3G calls, FM radio, Polaris office etc.
Click to expand...
Click to collapse
Use stock ics if you want those features
Sent from my LG-P990 using Tapatalk 2
I believe we will get a stable cm10 later.
better than any stock rom
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