Related
Hello all-
This is my first post here, so go easy on me
Well, I am Samsung captivate user on AT&T. I am currently running 2.2 rooted. My question: Should I upgrade to AT&T's gingerbread and try to root in there, or should I just pull the trigger and go to Cyanogenmod?
It seems rooting in 2.3 is not the simple SuperOneClick that it was for 2.2, and rooting with odin actually seems MORE complicated that flashing CM7 (And I guess more risky with multiple kernel flashes, yada yada yada). I am just thinking the less steps, the safer it probably is.
I am also liking all of the features of Cyanogenmod, epically the gesture app launching from the unlock screen.
In this How-to, the guy says to download the latest nightly build. Will it work the same if I choose the 7.1 stable release (I'm going for having whatever option I choose to be my daily use (I'm not gonna be flashing ROMs every month or week)):
I'd like to post it as a link, but xda is hating me and thinks I want to spam them D) so it is youtube at watch?v=iBPu-GqM9RE
What do you guys think?
PS I'm pretty sure you can, but using Titanium backup you can just "restore" all your apps just like that, correct?
If you are still on 2.2 you are way behind the curve.
There are some things you need to know. CM7 is a great ROM but is going to be replaced eventually by CM9 as everything is progressing towards Ice Cream Sandwich based ROMs. Gingerbread is an easy upgrade done through kies even with your rooted phone. It will flash the gingerbread bootloaders that are necessary to flash all gingerbread and some Ice Cream Sandwich based ROMs. Also, if you do choose to go to gingerbread, the kernel flashing process to root is very safe and very straight forward.
Lastly, I highly suggest getting away from a stock rom and flashing a custom ROM. It will make your phone feel like a new device compared to a stock ROM of any build. And yes, you can restore with Titanium Backup but remember to only restore the apps not the data.
Ive seen multiple guides for the stock gingerbread on captivate rooting.
Could you please point me towards the right one? I wanna make sure I dont try something outdated, wrong, ect.
Also, even if I choose to go to CM9 in the near future, should I still upgrade to the stock gingerbread right now and root? Will staying on 2.2 rooted make the CM9 flash easier ( I don't have clockworkmod recovery yet, if that matters ) or will having the 2.3 stock on it make the entire process easier?
Thanks!
From 2.2 Stock you can flash directly to CM9 without changing your boot loader to Gingerbread. That will put you straight to ICS 4.0.3. However your first step is to install CWM. But yes definitely get away from stock!
Sent from my SGH-I897 using xda premium
So there is no advantage to going to stock 2.3 in terms of flashing CM9 (start to finish)?
Here is the thread on how to root gingerbread.
http://forum.xda-developers.com/showthread.php?p=21375771
Cm9 as well as most all ice cream sandwich roms are still in beta phases so keep that in mind. If you absolutely have to have 100 percent reliability then a beta ROM is not for you.
Sent from my Captivate running Android 4.0.3 ICS
capocaccia said:
Here is the thread on how to root gingerbread.
http://forum.xda-developers.com/showthread.php?p=21375771
Cm9 as well as most all ice cream sandwich roms are still in beta phases so keep that in mind. If you absolutely have to have 100 percent reliability then a beta ROM is not for you.
Sent from my Captivate running Android 4.0.3 ICS
Click to expand...
Click to collapse
+1 to everything they said in posts above.
The only thing I would add is that while the CM9 build is beta (alpha actually) it is VERY stable. Many folks, myself included, use it a our daily driver with no real issues.
In any event, by all means, get off of stock and onto CM. You'll love it.
Sent from my SGH-I897 using XDA App
Heres another thought, what is the chance that I will brick my phone, honestly, so bad it really stays just a brick?
I am just scared, as I have another 10 months till I could even consider a phone upgrade and I like the fancy android phone I have now!
If you follow the instructions then chances are pretty low. Just make sure to read and read again. Ask before you go too far. The safest way I say is to use kies to upgrade to gingerbread because that flashes the bootloaders for you. Then you can go anywhere you want from there. That is if you want to go the gingerbread route.
Sent from my Captivate running Android 4.0.3 ICS
dellagd said:
Heres another thought, what is the chance that I will brick my phone, honestly, so bad it really stays just a brick?
I am just scared, as I have another 10 months till I could even consider a phone upgrade and I like the fancy android phone I have now!
Click to expand...
Click to collapse
You will only get a true brick if you fail during a bootloader flash. Most other "bricks" aren't really bricks at all, and can be easily recovered if you can get into download or recovery, which is usually the case.
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
Can anyone explain to me why the netflix app doesn't work on this ROM. Nothing ever gets displayed. AOKP on droid 4 latest build.
Sent from my XT894 using xda premium
Are you on one of the ICS leaks, or still have a Gingerbread "unsafe" system?
The Gingerbreak/ICS frankenROMs don't have hardware acceleration working properly (due to mismatched kernel). Thus Netflix, Chrome, Opera and anything else like that won't work.
Yeah I have gingerbread/aokp installed right now. So it sounds like I can't have a non safe system, just the ics leak installed. Is that correct? I still can't deside if I want to flash the ics leak or not. AOKP is nice and all with all its extra features, but for whatever reason, they cannot get data to work. Its pretty ridiculous they still don't have 3g/4g working after several months. Should i just go ahead and flash the ics leak?
It really isn't their fault, it is because the kernel is locked. AOKP-based off of the leak (as opposed to the Frankbuilds based on GB) work much better.
I finally jumped to the leak and atm I'm actually using the stock leak and am pretty happy with it. That being said, if you move to the leak you have to be ok with the fact that you might be off the upgrade path forever. The chance of that happening looks to be pretty small, but nobody can rule it out...
I understand its not AOKP's fault. The stuff they are pulling off is pretty advanced. Its just very frustrating from a users end trying to get data to play nice. I dont want to go to stock ICS because I really love the features AOKP has thrown in. And I dont wont to be off the upgrade path either. So will AOKP ever have solid data or are they going to have to take the stock ICS kernal and build a new AOKP ROM from that?
whiteout7942 said:
I understand its not AOKP's fault. The stuff they are pulling off is pretty advanced. Its just very frustrating from a users end trying to get data to play nice. I dont want to go to stock ICS because I really love the features AOKP has thrown in. And I dont wont to be off the upgrade path either. So will AOKP ever have solid data or are they going to have to take the stock ICS kernal and build a new AOKP ROM from that?
Click to expand...
Click to collapse
Bottom line is: a locked Bootloader prevents developers from providing a proper Kernel to the device. So, you don't get the HW codecs with a Gingerbread based ICS ROM, therefore no Netflix. If you install any of the leaked ICS builds, Netflix runs just fine (I can confirm)
I guess Motorola says that it's to protect us "in the name of security", but nobody seems to realize that the root exploits in themselves, already breaks that so called "security", so why not just let us have an unlocked bootloader!
Hopefully with the Google acquisition, someone can revisit that policy, and clarify to us users what it actually means. Moto probably loses customers over that policy.
bgarlock said:
revisit that policy, and clarify to us users what it actually means. Moto probably loses customers over that policy.
Click to expand...
Click to collapse
This^
You CAN have a safe system with the ICS leaks installed. You just have to use the Safestrap v 2.00 and ICS Leak build of aokp. AFAIK Netflix and HW Acc. codecs work with the new ICS leak builds!
Sent from my DROID4 using xda premium
zPacKRat said:
This^
Click to expand...
Click to collapse
I would say they lose some of the die hard users, who *need* to have an unlocked boot loader. Just reading through other posts, I have seen many get so frustrated at the fact that Moto won't unlock the boot loader, that they say they won't buy moto products because of it.
I'm just thankful that people have found loopholes that allow us work arounds, but it certainly adds a lot of complexity, that wouldn't be necessary if they would just unlock the boot loader (as they said they would do).
I get Moto's stance that they need to provide support, and if people are loading custom overclocked kernels, it could certainly cause HW damage, if the chip is running at a speed out of specs, but why not have the users sign something giving up that warranty, so they can do with their devices as they wish.
I'm just saying I think they should reconsider their policy of locked boot loaders, and open up their phones to hacker enthusiasts. Heck, Jelly Bean has been announced, and most phones still don't have ICS! I would bet an unlocked boot loader would have gotten ICS into the hands of users much faster, and in this instance where there is a ICS ROM, but a GB kernel, it would actually provide for a much better user experience.
moah909 said:
You CAN have a safe system with the ICS leaks installed. You just have to use the Safestrap v 2.00 and ICS Leak build of aokp. AFAIK Netflix and HW Acc. codecs work with the new ICS leak builds!
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
OK now I'm confused. I've been using the aokp builds for a while and they are the ics build 40 then the date. I've been flashing those for a long time but data is just as bad if not worse on some builds. Can someone explain why even though I have the ics leak, data is still screwed up? I was told data was much better on these builds.
whiteout7942 said:
OK now I'm confused. I've been using the aokp builds for a while and they are the ics build 40 then the date. I've been flashing those for a long time but data is just as bad if not worse on some builds. Can someone explain why even though I have the ics leak, data is still screwed up? I was told data was much better on these builds.
Click to expand...
Click to collapse
Nevrmind figured it out
Sent from my XT894 using xda premium
I was reading how Jelly bean was released, how long ago im not sure.
I know the Bionic has a boot loader, and i believe the only way that ICS and ICS roms are only available on the device through a leak.
How hard would it be to put this on the Bionic (since the source was released).?
symbiance said:
I was reading how Jelly bean was released, how long ago im not sure.
I know the Bionic has a boot loader, and i believe the only way that ICS and ICS roms are only available on the device through a leak.
How hard would it be to put this on the Bionic (since the source was released).?
Click to expand...
Click to collapse
There's a dev, known as Hashcode0f who along with a few others is working on a kernel which can bypass the bootloader. Once he gets it working (primarily on the Droid 3), he's going to put it on the Bionic and other newer Droid phones, JB will soon follow. It'll probably be a few weeks at the earliest before we see anything for the Bionic though.